Skip to main content
Safari ITP and Affiliate Tracking: What Actually Breaks and What Does Not

Technical · ~5 min read

Safari ITP and Affiliate Tracking: What Actually Breaks and What Does Not

Xark Team

Affiliate Program Management

November 15, 2026

Last updated 2026-11-15

Safari ITP blocks third-party cookies and caps JavaScript-set cookies at 24 hours or 7 days depending on the case. This guide separates what that breaks in affiliate tracking from what it does not, using WebKit's own published rules, and lists what to check and change.

Quick Answer

Which parts of affiliate tracking does Safari ITP break?

Under WebKit's published rules, Safari blocks all third-party cookies, caps cookies created in JavaScript at 24 hours when link decoration is detected, and deletes script-writeable storage after 7 days without user interaction. Server-recorded click and order data and promo codes do not depend on that browser storage.

# Safari ITP and Affiliate Tracking: What Actually Breaks and What Does Not

Safari's Intelligent Tracking Prevention (ITP) blocks all third-party cookies by default and limits how long cookies and other storage written by JavaScript can survive. For an affiliate program, the part that breaks is tracking that depends on a script-set cookie lasting through a long cookie window. Click and order data that your server records, and promo codes redeemed at checkout, do not depend on browser storage. The rules below come from WebKit's own tracking prevention documentation at webkit.org/tracking-prevention, which we read on 15 November 2026. The page was first published in 2020 and WebKit keeps updating it, so recheck before you make changes.

What WebKit says ITP does

These are the rules that matter for affiliate tracking, as described in the WebKit document:

  • ◆Third-party cookies are blocked. ITP blocks all third-party cookies by default, with no exceptions. Access can only be granted through the Storage Access API and a temporary compatibility fix for popups.
  • ◆Link decoration is capped at 24 hours. Some trackers add click IDs to link URLs and read them with JavaScript on the landing page. WebKit says ITP detects this and caps the expiry of cookies created in JavaScript on that landing page to 24 hours.
  • ◆Script-writeable storage is deleted after 7 days. ITP deletes all cookies created in JavaScript, and other script-writeable storage such as IndexedDB, LocalStorage and service worker registrations, after 7 days of no user interaction with the website.
  • ◆CNAME cloaking is capped at 7 days. When a first-party subdomain resolves to a third-party tracker through a CNAME, cookies set in the HTTP response are capped to 7 days. WebKit's table lists no cap when there is no cloaking, or when the cloaking is first-party.
  • ◆Bounce tracking is penalised. Domains classified as having cross-site tracking capabilities can have their website data deleted when there has been no user interaction in the last 30 days, and ones that do bounce tracking may have cookies rewritten to SameSite=strict.
  • ◆Third-party referrers are shortened. By default they are reduced to the origin, so a full URL with a click ID shows up as just the site address.

What this means for each tracking method

This section is Xark's analysis of those rules, not a WebKit statement, and we have not measured how much of any specific program's traffic comes from Safari.

  • ◆Third-party cookie tracking is blocked in Safari, so it should not be relied on there at all.
  • ◆A JavaScript-set first-party cookie with a 30-day window is the exposed case. If the visit used a decorated link, the cookie is capped at 24 hours. Otherwise it is deleted after 7 days without interaction. A shopper who returns on day 10 may no longer have the cookie, and the sale loses its credit.
  • ◆Cookies set by your own server on your own domain, without a third-party CNAME, are not covered by the caps above in WebKit's published rules.
  • ◆A tracking subdomain that CNAMEs to a vendor falls under the 7-day cap, so moving tracking onto a subdomain does not by itself solve the problem.
  • ◆Click IDs stored on your server and matched to the order are not browser storage, so ITP does not delete them. You do still need a reliable way to carry the click ID from landing page to checkout.
  • ◆Promo codes attribute at the point of purchase and do not rely on cookies at all.

What to do about it

  1. Measure Safari first. Compare conversion and commission per click for Safari and non-Safari traffic by network. If the gap is small, the problem is small.
  2. Ask each network how it tracks. Find out whether it relies on a client-side cookie, a first-party cookie, or server-side matching, and what lifetime it expects to survive in Safari.
  3. Capture the click ID on your server at landing and attach it to the session or cart, so it is available at order time.
  4. Give creators and partners their own promo codes as a fallback, so some attribution survives when a cookie does not.
  5. Do not lengthen the cookie window to compensate. A longer window does not outlast a 7-day or 24-hour deletion rule.
  6. Re-audit after browser updates. Check the WebKit page and your own conversion gap a couple of times a year.

For definitions, see our glossary entries on server-side tracking and mobile affiliate tracking.

Frequently Asked Questions

Does Safari block affiliate tracking cookies?

It blocks all third-party cookies by default, with no exceptions. First-party cookies written by JavaScript are limited rather than blocked: WebKit caps them at 24 hours in link-decoration cases and deletes them after 7 days without user interaction.

How long can a JavaScript cookie last in Safari?

Under WebKit's published rules, script-writeable storage is deleted after 7 days of no user interaction with the site, and cookies created in JavaScript on a landing page reached through detected link decoration are capped at 24 hours.

Does server-side tracking avoid ITP?

ITP's caps apply to storage in the browser and to cookies set through third-party CNAME cloaking. Click and order data recorded on your own server is not browser storage, so those rules do not delete it. You still need to carry the click ID through to the order, and a tracking subdomain that CNAMEs to a vendor is still capped at 7 days.

Do coupon codes still attribute sales in Safari?

Yes. A code entered at checkout is matched to the order directly and does not depend on a cookie surviving, which is why it works as a fallback attribution method.

Does Chrome behave the same way?

This article covers Safari only. Chrome and Firefox have their own rules, which we did not verify here, so check each browser's current documentation before applying these conclusions to them.

How does Xark handle tracking gaps in Safari?

Xark starts by measuring the Safari versus non-Safari conversion gap per network, then asks the network how its tracking survives ITP and adds server-side click ID capture and promo-code fallbacks where the gap is material.

Source: WebKit, Tracking Prevention in WebKit (webkit.org/tracking-prevention), read 15 November 2026.

TechnicalGrowthAutomation

Get affiliate insights in your inbox

— Stay Updated —

Get weekly affiliate marketing insights from Xark.

Further Reading

Ask an Expert

Have a question about this topic?

Our affiliate program specialists answer within 1 business day.

Related Reading