Apple and Google have gone in opposite directions. Safari now blocks fingerprinting and limits how long any script can remember a visitor. Chrome, used by most of the web, kept third-party cookies and shelved the technology meant to replace them. For anyone measuring a website, the result is that the same visitor is easy to follow in one browser and hard to follow in the other.
Safari vs Chrome tracking protection at a glance
| Safari and iOS (Apple) | Chrome and Android (Google) | |
|---|---|---|
| Third-party cookies | Blocked by default since 2020 | Allowed in normal browsing; blocked in Incognito |
| Cookies and storage set by scripts | Expire after 7 days without a visit (Intelligent Tracking Prevention) | No cap |
| Fingerprinting | Advanced Fingerprinting Protection adds noise for known scripts in all browsing (Safari 26) | No comparable protection; Google's ad policies have allowed it since February 2025 |
| Click IDs in links | Stripped in Mail, Messages and Private Browsing (Link Tracking Protection) | Kept |
| Visitor IP address | Hidden behind iCloud Private Relay for iCloud+ subscribers | Visible |
| Tracking across apps | Apps must ask first (App Tracking Transparency) | Android advertising ID, which users can delete |
As of October 2026. Apple can also change its lists of known trackers without shipping a new Safari version.
How Apple limits tracking
Apple sells hardware and services, not ads, so it can afford to treat tracking scripts as a problem to contain. Each Safari release has removed a little more of what trackers relied on:
- Intelligent Tracking Prevention (2017 onwards). Blocks third-party cookies and, since 2020, deletes cookies and storage written by scripts after 7 days without a visit.
- App Tracking Transparency (iOS 14.5, 2021). Apps must ask before tracking people across other companies' apps and websites. Most people say no, which is why ad attribution on iPhone became so unreliable.
- iCloud Private Relay (2021). Hides the IP address of iCloud+ subscribers in Safari, so many iPhone visitors share Apple's IP addresses.
- Link Tracking Protection (2023). Removes known click IDs from links opened in Mail, Messages and Private Browsing.
- Advanced Fingerprinting Protection (Safari 26, 2025). Previously limited to Private Browsing, now on for all browsing. Known fingerprinting scripts get deliberately noisy canvas, audio and screen values.
- Safari 27 (2026). Reportedly classifies more tags, including some mainstream marketing tags, and restricts what they can read. See what iOS 27 changes for your analytics.
How Google handles tracking in Chrome
Google earns most of its money from advertising, and its plans to limit tracking in Chrome have mostly been reversed:
- Third-party cookies stay. Google announced in 2020 that Chrome would phase them out, dropped that plan in 2024, and in April 2025 said it would not add a separate cookie prompt either. Chrome blocks third-party cookies only in Incognito.
- Privacy Sandbox retired. In October 2025 Google said it was retiring most of the Privacy Sandbox, including the Topics, Protected Audience and Attribution Reporting APIs, after low adoption.
- Fingerprinting allowed for advertisers. Since February 2025, Google's ad platform policies no longer forbid fingerprinting. The UK's data protection regulator, the ICO, called the change irresponsible and said fingerprinting still has to meet data protection law.
What this means for your analytics
Your data is now uneven by browser. Chrome visitors look much as they always did. Safari visitors, which on many sites means most mobile visitors, are harder to recognize on a return visit and arrive with fewer campaign details. The error hides inside your totals:
- Returning visitors look new. An ID set by a script lasts 7 days in Safari, so a visitor who comes back after two weeks is counted twice.
- Attribution gaps. Stripped click IDs and blocked scripts mean conversions from iPhone users get credited to "direct" or lost.
- Fingerprinting is a dead end. On Safari it is blocked or made useless, and in the EU and UK it needs consent anyway. See the consent banner data gap.
What to do about it
- Compare key metrics by browser. If Safari visitors convert less or return less often in your reports, check whether that is real or a measurement gap.
- Collect analytics on your own domain. Data sent through your own site and server is treated as first-party by browsers.
- Send conversions from your server. Sign-ups and purchases recorded on your backend can't be lost to a blocked script.
- Store click IDs at landing. Save them against the visit on the first page view, so later conversions can still be attributed.
- Use analytics that don't depend on tracking. Privacy-first analytics and cookieless analytics are built for the limits Safari already enforces.
How WysLeap handles this
WysLeap sets no cookies and keeps a random ID in local storage. On other browsers, device fingerprinting can link a new ID to the earlier one when the browser and network match. It never runs on Safari or iOS. In the EU, UK and Switzerland, nothing is stored or sent until the site records consent.
Frequently asked questions
Does Chrome still use third-party cookies in 2026?
Yes. Google dropped its plan to remove third-party cookies from Chrome in 2024, and in April 2025 said it would not add a separate prompt either. Chrome still allows third-party cookies in normal browsing and blocks them in Incognito.
What happened to Google's Privacy Sandbox?
In October 2025 Google said it was retiring most Privacy Sandbox technologies, including the Topics, Protected Audience and Attribution Reporting APIs, citing low adoption. They were meant to replace third-party cookies, which Chrome is keeping.
Does Safari block fingerprinting?
Safari 26 turned on Advanced Fingerprinting Protection for all browsing by default. Scripts Apple classifies as fingerprinters get noisy canvas, audio and screen values and lose access to some browser APIs. Safari 27 reportedly adds more scripts to that list and restricts what they can read.
Does iOS block tracking in Safari or only in apps?
Both, through different features. App Tracking Transparency covers apps tracking you across other companies' apps and websites. In Safari, Intelligent Tracking Prevention, Advanced Fingerprinting Protection and Link Tracking Protection limit tracking on the web.
Why do my analytics numbers differ between Safari and Chrome?
Safari limits how long scripts can keep an ID and blocks fingerprinting, so returning Safari visitors are often counted as new and campaign click IDs go missing. Chrome visitors are rarely affected. If your audience is iPhone-heavy, compare your metrics by browser before trusting the totals.



