Click Tracking
Every time someone clicks an Attri shortlink, a click event is recorded with metadata about the visitor. This happens at the edge before the redirect, so there’s no added latency for the visitor.
What is captured
Section titled “What is captured”Each click event includes:
| Field | Description |
|---|---|
| Timestamp | When the click happened (UTC) |
| Link ID | Which shortlink was clicked |
| Referrer | The page the visitor came from |
| Country | Visitor’s country (from IP geolocation) |
| City | Visitor’s city |
| Device type | Desktop, mobile, or tablet |
| Browser | Browser name and version |
| OS | Operating system |
| User agent | Full user agent string |
No cookies. No client-side JavaScript. Everything happens server-side at the redirect, which is exactly the kind of tracking we think should be the default.
How it works
Section titled “How it works”- Visitor clicks your shortlink (e.g.,
attri.link/spring) - The request hits Attri’s Cloudflare Worker at the edge
- The Worker looks up the link configuration in KV
- A click event is sent to Tinybird for analytics
- The visitor is redirected to the destination URL (with parameters appended)
The entire process completes in under 50ms at the edge. We’ve spent a lot of time optimizing this path, and it shows in the numbers.
Bot filtering
Section titled “Bot filtering”Attri filters out known bots and crawlers from your click data so your analytics reflect real human traffic. Nobody wants inflated numbers from Googlebot.
- Click data is retained according to your plan’s retention period
- For tracking activity on your website after the redirect, see the Tracking Script