X link attribution
See which tweet is behind your π-referred traffic and revenue, instead of just an anonymous t.co referral.
The problem this solves
π routes every link posted in a tweet through its own t.co shortener, and only ever sends the bare t.coorigin as the Referer header β never the tweet, never the path. So without this feature, every click from π shows up in your Referrer breakdown as one anonymous βx.comβ row, no matter how many different tweets actually sent it.
How it works
Once enabled, we search π every half hour for tweets that link directly to your domain and record each one we haven't seen before. Separately, for a visitor whose first-ever visit was referred from π, we look for the most recently-posted tweet we found linking to your site in the hours immediately before that visit. If we find one, that visitor's traffic and any revenue they go on to generate is attributed to it on the Acquisition βΊ Tweets tab of your dashboard.
t.coreferral carries no tweet id, so there is no way to know for certain which tweet a click came from β only which tweet was plausibly posted recently enough to be the cause. Traffic that matches no tweet in the window shows up as an explicit βUnattributedβ row rather than being guessed at or dropped.Getting an exact match instead
If you want certainty rather than an estimate, add a ?ref= or utm_source/utm_campaign tag to the specific links you post, then check the Campaign tab β a tagged link is unambiguous no matter how π rewrites the URL around it.
Latency
Right after you enable it, the dashboard shows a βScanning πβ¦βstate. The first pass looks back over roughly the last two days and can take a few hours to surface everything; after that, new tweets show up within about half an hour of being posted. π search itself only covers roughly the last seven days of posts, so a tweet older than that when scanning first runs won't be picked up.