How to burn $20 on Twitter with $10 real CPC
Why I try new advertising channels, I typically spend $20 to be fair.
I also run a personal link shorten-er, and decided to use that to track my CTR.
In about 30 minutes 20$ bought me 31 engagements (all clicks in this case) on a promoted tweet.
At ~$0.65 ecpe, this sounds like an awesome deal. Obviously the quality of the traffic won't be as good as search traffic.
However, I made sure my ad was at least geographically targeted.
Reality:
Of the 31 reported engagements, my link shorten-er showed 10 clicks.
2 were from self proclaimed bots (Mozilla/5.0 (compatible; TweetmemeBot/3.0; +http://tweetmeme.com/))
6 others were also from bots, they had these user agents:
Ruby
Kimengi/nineconnections.com
MetaURI API/2.0 +metauri.com
JS-Kit URL Resolver, http://js-kit.com/
(twice) UnwindFetchor/1.0 (+http://www.gnip.com/)
At the end of the day, only two other clicks came from realistic useragent/ips that could be construed as a real person.
Real Cost:
$10 CPC
conclusion:
Totally not worth it. Twitter needs to get their shit straight and resolve their blatant click fraud OR provide the real data behind those engagements (useragents, precise IP based geolocation, referrers.)
17 comments
[ 3.4 ms ] story [ 44.7 ms ] threadFacebook advised Promoted Posts were more effective on smaller pages (eg. <1,000 fans).
Facebook iOS install ads - ridiculously good conversions on installs, and then active users. Better than any other ad platform that I've tested with.
I liked the demographic information they gave me - where the engagements came from geographically, as well as information on gender and interests. We can use that information with regards to Twitter, as well as independent of Twitter.
I know our campaign (probably) hit real people because we got a reply and five re-tweets. Our campaigns totalled to $225.
Are you sure all clicks from all clients would have visited your shortener, as opposed to skipping it using metadata about its final destination?
(It might be worth testing with a unique, 200-returning terminal URL.)
Shoot; the destination is a static site served with a rack app and Google Analytics does not have data yet (too old for real time, too new for normal). I'll have to check back later.