Clients, mobile devices, and web browsers: Another mistake is not paying attention to the source attribute of a status message. There you should see something like, via web*,
If you're here, I assume you've read the first part of this tutorial, Twitter for Traffic Overview. Squeezing Twitter traffic is fallible process! I wouldn't suggest skipping anything.
(previous: Twitter for Traffic Errors Part 1)
4. Clients, mobile devices, and web browsers: Another mistake is not paying attention to the source attribute of a status message. There you should see something like, via web*, via Twitter for iPhone*, via etc. These are application programs called clients for an array of devices used to access twitter. These could also be desktop programs, or remote website applications, which allows a user to access a Twitter account indirectly.
Remember that if you want converting traffic, you should go for via web*. This means that a user was accessing Twitter on the main website, "Twitter.com," and not in some robotic remote client. It means that a user is reading your tweets using a web browser, with scripting enabled, and not from an iPhone.
Error D: Mobile Devices
Another problem that webmasters face is that Twitter could be accessed via mobile devices. Now not all our websites work well with iPhones, much less if it's even compatible to be displayed in the first place. And even if by some cosmic luck, a website loaded seamlessly into a mobile device, it is hardly even possible to serve ad rotators, banners, flash, etc.
After then traffic simply becomes a great waste of bandwidth, rather than good converting traffic.
Error E: Spam Activity
Before considering outsourcing to paid services, you must know that automation is a real screamer to get a user banned by Twitter. Rummage through background information of such sites to be sure if they don't spam your account or show risky behaviors. Like so;
* Following and unfollowing the same person over and over
* Following and unfollowing aggressively
* Tweeting to your account without your consent
* Tweeting too much links to your account
* Sending out duplicate updates
* Spamming the hashtags (#) or mentions (@)
Error F: TwitterOAuth
Recently, the Twitter API team made TwitterOAuth mandatory for all Twitter based applcations or clients. TwitterOAuth gives developers access codes. Then with your permission, they after getting a users permission, they could substitute that code for your account credentials. Meaning, you don't compromise your Twitter username or password.
A few months back, I would have said signing up for application-based websites and giving them your Twitter username and password is out of the question. Now, it's basically pathetic and obvious the way there are still some websites asking you for your username and password—knowing that it no longer works that way.
(next: Twitter Potential)