4 ms·
I noticed long ago that none of Twitter's redirects had the proper referrer listed, and it really is annoying. There's no way to parse a log and know how many p
by dendory 15y ago
I noticed long ago that none of Twitter's redirects had the proper referrer listed, and it really is annoying. There's no way to parse a log and know how many people clicked on a link from Twitter unless I use another landing page just for Twitter shares which is a bit silly. I don't see why Twitter is doing that.
- jdkoeck 15y agoRead the article again, they just fixed the very problem you're having! All you have to do now is to count all HTTPs accesses with a referrer from 't.co'.
- deleted 15y ago[deleted]
- dendory 15y agoNope, if someone clicks on one of my links on Twitter the referer field is empty. If I click on Facebook I get a Facebook url. That is a problem for both Twitter and web sites.
- jaredsohn 15y agoReread it again :). Especially look at the charts. Like the author, I personally see t.co in my server logs. It would be pretty hard for Twitter to remove the referrer altogether (and I'm not sure what the point would be; they should want people to see that they got traffic from Twitter). Just did some research on ways to remove the referrer and found this: http://coding-talk.com/f14/how-to-remove-referral-8570/ http://coding-talk.com/f14/how-to-remove-referral-8570/. At comment #8, they suggest making links via Flash, using https, or using a redirect (which is what t.co is). Users could also do it by configuring their browser to not send along the referrer when they make new requests, but Twitter wouldn't have control over that.)
- zeedotme 15y agoWhich referrers did you see before the change? Wasn't it just the twitter client that the visitor used to click the link?
- intranation 15y agoBecause of Twitter's hashbang URL routing, you'd often just see "http://twitter.com/ http://twitter.com/ as the referrer.