Okay, so I spent the last 2 days going back and forth with Aweber technical support regarding publishing my blog announcement on my Twitter account.
The thing is, I manage multiple blogs and I’d like for each blog announcement to be posted on their own Twitter account.
In case you haven’t noticed, this feature is available when you set up your blog announcement:
Now, the same Twitter Update option is available if you switch to another list and manage your blog announcement.
So I did exactly that - switched to another list and set up the Twitter Update, but I noticed that my previous Twitter account login is pre-filled to what I had put in when I was setting up my first list.
I didn’t think much of it and updated the Twitter login to another account that I want posted to. But when I switch back to my first list, that Twitter account login has been updated to the latest Twitter account I had put in!
It seems like whatever you put in your Twitter login, that login is used in all of your lists!
I quickly submitted a support ticket and letting them know of this “bug.” Then I got the run-arounds… first reply telling me that all I have to do is update the Twitter account for each list (no sh*t, did you even read my ticket???), then another reply asks for specific lists that I’m working with (why even bother, just test it on your end!), then last reply apologizing that this “feature” is not available.
SOoo… intuitively, one would think that you can post to one Twitter account from one list, and a different Twitter account from another list - I mean, why even bother having that Twitter Update setting on every list!
Alright, so do me a BIG favor and suggest “using multiple Twitter IDs” as a new feature. Else I’m going to be stuck with publishing all my blog announcements to my one Twitter account.
Login to your Aweber account, click on “Help” link in the top right corner, and submit a suggestion to add this feature:
If you are looking for Aweber alternative, I suggest GetResponse - Here is a comparison between Aweber & GetResponse.
Thanks for listening!