Bounce tracking mitigations
Browsers delete the stored data of sites the person only passed through on a redirect.
In one line
Can wipe stored data of sites you only passed through on a redirect
Browsers delete the stored data of sites the person only passed through on a redirect.
Defeats the tracker that bounces a person through its own domain to set a first-party cookie. Chrome checks about hourly and spares sites visited with interaction in the past 45 days. Safari has classified bounce trackers since 2017.
What it can and can't do
What the user does: Nothing. Your browser does it on its own after a redirect
It can
- Delete cookies and storage of a site that only bounced you along
- Run on its own after a short wait
- Stop trackers using quick redirects to set IDs
It cannot
- Delete data of sites you actually used or interacted with
- Stop a tracker that gets you to click or sign in there
- Run in Samsung Internet, and only partly in Firefox
- Be turned on or off by the site
How it differs between platforms: Chrome, Edge and Safari do this. Firefox does it partly. Samsung Internet does not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 116 | 2023-08-15 | Active for users with third-party cookies blocked |
| Edge | Supported | 116 | 2023-08-21 | None |
| Firefox | Partial | 131 | 2024-10-01 | Strict mode, verify default |
| Safari | Supported | 11 | 2017-09-19 | Classification based, 30 day clearing |
| Safari on iPhone | Supported | 11 | 2017-09-19 | None |
| Chrome on Android | Supported | 116 | 2023-08-15 | None |
| Samsung Internet | Not supported | Not available | Not listed | Unverified |
How a site asks for it
| API | Browser background task; no site API (Clear-Site-Data and interaction avoid it) |
| 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 | Chrome deletes after a grace period (about 1 hour) unless the site had interaction in the last 45 days |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: No data exposed
Shape: none
How often: n/a
No individual data fields. The signal is the access itself.
Technical limits
- Sites with user interaction in the past 45 days are exempt (Chrome)
- Deletion runs about hourly
- Only affects sites reached by redirect with no visible interaction
- Chrome and Firefox default behaviour varies by tracking protection mode
The story
What it is
The browser clears stored data from sites that you only passed through on a redirect.
For you
You do not see it. If a link sends you through a tracker's page for a split second, the browser notices you never used that site. It then wipes the tracker's cookies and storage so it cannot follow you.
For makers
Trackers moved to redirects when third party cookies got blocked. Browsers answered by deleting data from sites you did not really visit. Makers of login or payment redirects must make sure that real people interact with their site, or it may be treated as a tracker.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A single sign on service sends you through its domain to sign you in, and needs you to click or type there so it is not seen as a bounce tracker. | Okta, Auth0 |
| ads | An ad tracker bounces you through its domain to set a first party cookie. The browser deletes it within hours. | None named |
| payments | A payment page redirects you through a bank domain. If it never gets a user action, the browser may clear its data. | PayPal, Stripe |
| analytics | A link shortener passes you through its domain to count clicks. Safari and Chrome may erase its cookie. | Bitly |
| games | A game login that bounces you through a different account site must get a click there, or your session data may be cleared. | Epic Games, Steam |
| social | A shared link wrapper on a social site that redirects to the target may lose its cookie if people never interact with it. | Facebook, LinkedIn |
Risks
- Legit redirects can be wrongly cleared
- Does not stop other tracking
What the platform says
- Apple: Tracking prevention. WebKit documents Safari's protections that classify and limit sites that bounce people through redirects to track them.
Good uses and abuse
Legitimate uses
- Privacy protection
Known abuse
- Not applicable
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 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
- 2017-09, Safari 11: ITP 1.0 classifies bounce trackers
- 2023-08, Chrome 116: Bounce tracking mitigations shipped when third-party cookies blocked
- 2024-09, Firefox 131: Bounce tracking protection in Strict mode (verify default)
Related capabilities
Related
- Navigational tracking. Can pass an ID along when you move between sites by link or redirect
- Outbound link decoration. Can add an ID to a link so the next site can recognize your visit
Sources
- Privacy CG bounce tracking mitigations
- Chrome bounce tracking mitigations
- WebKit Tracking Prevention
How well checked: Based on official documentation.