Skip to Content
Platform.Ontology

Navigational tracking

Passing IDs through link URLs or redirects when the person moves between sites.

Used to track youTracking across apps and sitesBefore the visitWeb browsersBefore you visitAfter you leave the site

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

Chromeworks
Edgeworks
Firefoxworks
Safariworks
iPhoneworks
Androidworks
Samsungworks
BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11Technique, works in every browser unless mitigated
EdgeSupported1Not listedTechnique, works in every browser unless mitigated
FirefoxSupported12004-11-09Technique, works in every browser unless mitigated
SafariSupported12003-06-23Technique, works in every browser unless mitigated
Safari on iPhoneSupported12007-06-29Technique, works in every browser unless mitigated
Chrome on AndroidSupported1Not listedTechnique, works in every browser unless mitigated
Samsung InternetSupported12013-04-27Technique, works in every browser unless mitigated

How a site asks for it

APIURL query or fragment decoration; HTTP 302 redirect chains; first-party cookies
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsFirst-party cookie lifetime (Safari caps to 24 hours if set by script after tracker link decoration)
How to take it backClear site data, browser privacy settings
Inside an iframeNot 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

TypeExampleApps
adsYou 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
analyticsA site passes your visitor ID from its main site to its shop on another domain, to keep one session.None named
gamesA game site sends you to a partner store with a code, so the partner can credit the referral.Steam, Epic Games
shoppingA coupon site redirects you through a tracker so the store knows which coupon you used.RetailMeNot, Honey
securityA login redirect passes a one time code between domains, which is not tracking but looks the same.Okta
mediaA 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

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

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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

Sources

How well checked: Based on official documentation.

On this page