Navigational tracking
Passing IDs through link URLs or redirects when the person moves between sites.
In one line
Can pass an ID along when you move between sites by link or redirect
Passing IDs through link URLs or redirects when the person moves between sites.
Works even with third-party cookies blocked: site A appends an ID to the outbound link, site B reads it and sets a first-party cookie, or a tracker redirect sets its own first-party cookie for a moment. The main workaround to ITP and TCP.
What it can and can't do
What the user does: You click a link or get redirected to another site
It can
- Add an ID to the link's address
- Pass the ID through a chain of redirects
- Let the next site recognize you as the same visitor
It cannot
- Follow you if you type the address or use a bookmark
- Work if the browser strips known IDs from links
- See what you did on the first site beyond what is in the link
- Last if you clear cookies and the ID is not stored
How it differs between platforms: Firefox, Safari and Brave remove some IDs from links. Chrome does not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | Technique, works in every browser unless mitigated |
| Edge | Supported | 1 | Not listed | Technique, works in every browser unless mitigated |
| Firefox | Supported | 1 | 2004-11-09 | Technique, works in every browser unless mitigated |
| Safari | Supported | 1 | 2003-06-23 | Technique, works in every browser unless mitigated |
| Safari on iPhone | Supported | 1 | 2007-06-29 | Technique, works in every browser unless mitigated |
| Chrome on Android | Supported | 1 | Not listed | Technique, works in every browser unless mitigated |
| Samsung Internet | Supported | 1 | 2013-04-27 | Technique, works in every browser unless mitigated |
How a site asks for it
| API | URL query or fragment decoration; HTTP 302 redirect chains; first-party cookies |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | First-party cookie lifetime (Safari caps to 24 hours if set by script after tracker link decoration) |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: ID in URL
Shape: string
How often: per navigation
No individual data fields. The signal is the access itself.
Technical limits
- Safari caps script-set cookies to 24 hours when the landing URL carries decoration from a tracker classified origin
- Chrome bounce tracking mitigation deletes state of redirect-only sites
- Cannot read the previous site's cookies
The story
What it is
Passing IDs in links or quick redirects as you move from one site to another.
For you
You click a link and land on another site. You may not notice an ID in the web address or a flash redirect. The new site saves it in its own cookie, so third party blocking does not help.
For makers
It is the main workaround for browsers that block third party cookies. IDs in links or redirects join your visit across companies. Browsers answer with caps on cookie life and stripping of known IDs.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | You click an ad and the ad network adds an ID to the link. The store saves it and ties your sale to the ad. | Google Ads, Meta Ads |
| analytics | A site passes your visitor ID from its main site to its shop on another domain, to keep one session. | None named |
| games | A game site sends you to a partner store with a code, so the partner can credit the referral. | Steam, Epic Games |
| shopping | A coupon site redirects you through a tracker so the store knows which coupon you used. | RetailMeNot, Honey |
| security | A login redirect passes a one time code between domains, which is not tracking but looks the same. | Okta |
| media | A newsletter link wrapper counts your click and then sends you to the story. | Mailchimp, Substack |
Risks
- Works with cookies blocked
- Hard to see in the address bar
What the platform says
- Apple: Tracking prevention. WebKit documents how Safari fights tracking that uses link decoration and redirects.
Good uses and abuse
Legitimate uses
- Cross-domain analytics (Google _gl linker)
- Affiliate attribution
Known abuse
- Cross-site ID passing after third-party cookies are blocked
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2019-02, Safari 12.1: ITP 2.1 capped script cookies to 7 days; ITP 2.2 capped to 24 hours when decoration present
- 2023-08, Chrome 116: Bounce tracking mitigation shipped for users with third-party cookies blocked
Related capabilities
Related
- Bounce tracking mitigations. Can wipe stored data of sites you only passed through on a redirect
- Outbound link decoration. Can add an ID to a link so the next site can recognize your visit
Sources
How well checked: Based on official documentation.