Safari ITP affects affiliate tracking in three main ways: it blocks third-party cookies outright, it caps the lifetime of many first-party cookies at seven days (and at 24 hours in some link-decoration cases), and related features such as Link Tracking Protection strip known tracking parameters in certain contexts. The fix is to rely on click IDs stored in server-set first-party cookies or against customer accounts, and to report conversions by server-to-server postback.

Below we break down each restriction, the symptoms you will see in your reports, and the fixes that still work in late 2026.

What Intelligent Tracking Prevention does

Intelligent Tracking Prevention (ITP) is WebKit's set of anti-tracking rules, used by Safari on Mac, iPhone and iPad. Because every browser on iOS has historically been built on WebKit, many iPhone users are affected even outside Safari, though Apple now allows other engines in the EU under the Digital Markets Act. ITP has been strengthened in stages since 2017. The rules that matter most to affiliates are below.

RestrictionWhat it doesAffiliate impact
Third-party cookies blockedCookies set by a domain other than the site being visited are not availableNetwork cookies set on the advertiser's site via third-party pixels do not work
7-day cap on script-set cookiesCookies created with JavaScript (document.cookie) expire after at most seven daysA 30-day cookie window becomes seven days in practice for script-based tracking
24-hour cap after link decorationIf the visitor arrives from a domain ITP classifies as a tracker, with a query string or fragment in the URL, script-set cookies on the landing page are capped at 24 hoursVisitors who arrive via certain redirect chains and buy the next day may be lost
7-day cap on server-set cookies from third-party IPsSince Safari 16.4, cookies set by a server behind a third-party CNAME, or whose IP does not match the main site's, are capped at seven daysSome "first-party" tracking subdomains pointing at a vendor's servers are treated like third parties
Storage deletionScript-writable storage such as localStorage can be deleted after seven days of Safari use without interaction with the siteClick IDs saved in localStorage are not a durable fallback

The WebKit team documents these changes on its blog; for example, its ITP 2.3 post covers the link-decoration and storage rules.

Apple introduced Link Tracking Protection in 2023. It removes known tracking parameters, such as some ad-platform click identifiers, from URLs opened in Mail, Messages and Safari Private Browsing. With Safari 26 in 2025, Apple extended Advanced Fingerprinting Protection to all browsing by default, while Link Tracking Protection in normal browsing remains tied to the stronger protection setting, which users can switch on.

Apple does not publish the full list of stripped parameters. Generic affiliate parameters have not been the main target so far, but you should not assume that holds. Other features to know:

  • iCloud Private Relay hides the user's IP address for subscribers who enable it, which weakens IP-based matching and fraud checks.
  • Hide My Email generates random addresses, which can break email-based matching between sign-up and purchase.
  • In-app browsers in social and messaging apps keep their own storage, so a visitor who clicks inside an app and later buys in Safari looks like a new visitor.

Signs Safari is losing your affiliate commissions

  • Conversion rate for iOS and Safari traffic is markedly lower than for Chrome and Android on the same offer, while the program says Safari customers convert normally.
  • Short-path conversions (same session) track, but sales a week or more after the click do not.
  • Programs using JavaScript tags on the advertiser's site under-report compared with those using S2S postbacks for the same audience.
  • Email and SMS campaigns linking straight to offers under-perform, particularly where links carry ad-platform click IDs.

To confirm, run tests from an iPhone using our pre-launch tracking test, including a conversion several days after the click. Our guide to conversions not tracking covers other causes to rule out.

Technical fixes that still work

For advertisers and programs

  1. Read the click ID on landing and store it server side. Save it in your own database against the session or, better, the customer account at registration.
  2. Set first-party cookies from your own server. An HTTP response cookie from your main domain, served from infrastructure that matches your site's IP, avoids the script-set and third-party-IP caps.
  3. Report conversions by S2S postback to the network, not by browser pixel. See S2S vs pixel tracking.
  4. Attribute at account level so later and cross-device purchases are credited when the customer logs in.
  5. Avoid CNAME set-ups that point to a vendor's servers if you are relying on them for long-lived cookies, or configure server-side tagging so the IP rules are met.

For affiliates and media buyers

  1. Prefer programs that use S2S postbacks and account-level attribution, and ask how they handle Safari.
  2. Keep redirect chains short and avoid hops through domains that may be classified as trackers.
  3. Use your own tracking domain for your tracker so your redirect is less likely to be blocked.
  4. Segment by browser in your tracker and value iOS traffic per program based on what actually tracks.
  5. Encourage same-session conversion with clear calls to action and honest offer information, so fewer sales depend on long cookie windows.

Hypothetical example: a publisher sees Safari conversion rates half those of Chrome on Program X but similar to Chrome on Program Y. Program Y uses server-set cookies and postbacks; Program X uses a JavaScript tag. Moving iOS traffic to Program Y, or asking X to upgrade, recovers the gap without changing the content.

What does not work (or is not worth the risk)

  • Fingerprinting to re-identify Safari users. Apple actively counters it, and UK and EU regulators treat it as subject to consent rules.
  • Bouncing visitors through extra domains to set cookies; ITP's bounce-tracking protections target this.
  • Relying on localStorage as a durable store for click IDs.

Privacy law still applies to every fix. Our guides to whether affiliate cookies need consent and server-side tracking and GDPR explain the position. This is general information, not legal advice.

Frequently asked questions

Does Safari block affiliate links?

No. Links work and visitors reach the offer. What Safari restricts is the tracking that credits you afterwards, especially third-party and script-set cookies and certain known tracking parameters.

Does ITP affect Chrome on iPhone?

Browsers on iOS have traditionally used Apple's WebKit engine, so many ITP-related limits apply to them too. Apple now permits alternative engines in the EU, but WebKit-based browsers remain common, so test on the browsers your audience actually uses.

Will server-side tracking fully solve Safari losses?

It solves most of them, provided the click ID reaches the advertiser and is stored server side. Cross-device journeys without a login and stripped parameters can still cause losses.

Next steps

For the wider picture beyond Safari, read our guide to cookieless affiliate tracking and the explainer on cross-device affiliate tracking. To find a tracker that supports postbacks and custom domains, browse our affiliate tracking platforms directory.