Identity & Recognition

Safari ITP

Safari ITP, or Intelligent Tracking Prevention, is Apple's set of browser limits on tracking. The one ecommerce teams meet most often deletes script-writable storage, including JavaScript-set cookies, after 7 days of Safari use without interaction with the site.

October 31, 2026

Safari ITP, or Intelligent Tracking Prevention, is Apple's set of browser limits on tracking. The limit ecommerce teams meet most often deletes script-writable storage, including JavaScript-set cookies, after 7 days of Safari use without interaction with the site.

What does ITP limit?

Situation What Safari does Source
Cookie or storage written by script Deleted after 7 days of browser use without interaction with the site WebKit
Script-set cookie after a click from a known tracker to a URL with query parameters or a fragment 24-hour expiry Klaviyo docs
Cookie set in an HTTP response Not covered by the script rule WebKit
Server-set cookie through a subdomain pointing to a cross-site host Can be capped at 7 days Klaviyo docs, WebKit on CNAME cloaking
Server-set cookie where the server's IP doesn't match the site's first half (Safari 16.4) Can be capped at 7 days Aimerce write-up

The clock is worth reading closely. It counts days of Safari use without interaction with your site, so someone who visits often keeps resetting it. A customer who reorders every six weeks is much more likely to run past it.

Why does ITP matter for Shopify brands on Klaviyo?

Klaviyo's __kla_id cookie is set by JavaScript for 2 years, and browsers can shorten that. In Safari, a returning customer who stayed away long enough can lose the cookie and arrive looking anonymous. If they add to cart, Klaviyo may not know who to email. Why doesn't Klaviyo identify returning visitors? goes through the causes.

Klaviyo's Extended ID and First-Party ID respond to this directly. The server-set First-Party ID (__kle_id) can restore __kla_id for people with an existing profile. Extended ID is on all plans, so turn it on first.

What doesn't ITP explain?

ITP affects whether one Safari browser is recognized over time. It doesn't explain a shopper who starts on a laptop, opens your email on a phone and finds an empty cart. That's cross-device cart abandonment, and it happens in every browser. A server-side cookie that lasts longer still stays on one device. Keep the two problems apart when you diagnose a flow.

How does reOtter deal with browser limits?

reOtter recognizes people who've already given your brand their details, without a third-party network, in a record that doesn't depend on a browser cookie surviving. Strangers aren't identified, and carts are held only with analytics consent from your store's banner.

Key takeaways

  • ITP's best-known rule deletes script-set storage after 7 days of Safari use without interaction with the site.
  • Server-set cookies avoid that rule, with exceptions for cross-site subdomains and for IP mismatches on Safari 16.4.
  • ITP limits recognition on one browser, so it doesn't explain empty carts on a second device.

See how reOtter restores the cart → Abandoned cart recovery

Frequently asked questions

Does Safari delete all cookies after 7 days?
No. The 7-day cap applies to script-writable storage, which includes cookies set by JavaScript. Cookies set in an HTTP response aren't covered by that rule, though other Safari limits can still apply. The clock also counts days of browser use without interaction with the site.
Do server-set cookies avoid Safari ITP completely?
Not completely. Klaviyo's documentation says the 7-day cap applies to its server-set cookie when a subdomain points to a cross-site host. Safari 16.4 can also cap server-set cookies at 7 days when the setting server's IP doesn't match the site's first half.
Does Safari ITP cause empty carts from email clicks?
Usually that's a different problem. A cart left on a laptop is missing from a phone because it's a separate device, and that happens in any browser. ITP's effect is on whether the same Safari browser is still recognized later.
What should a Klaviyo brand do about ITP?
Start with Klaviyo's own options. Extended ID is on all plans, free and paid, and its server-set First-Party ID can restore the script-set cookie. Both work on the browser, so they don't change anything on a second device.

Keep exploring

Cart Recovery

The Safari 7-Day Cookie Limit, Explained for Klaviyo Brands

Safari can delete JavaScript-set cookies after 7 days of browser use without interaction with your site. Here's how that affects Klaviyo's tracking cookie, what Extended ID and First-Party ID change, and the one thing no cookie setting can fix.

Cart Recovery

Server-Side Cookies: What They Do for Returning Customers and Where They Stop

Server-side cookies last longer than script-set ones in most browsers, which is why so many ecommerce tools now use them. They also have exceptions worth knowing. Here's how they work, where they stop, and what to do about recognizing returning customers when browser cookies go away.

Identity & Recognition

Server-Side Cookie

A server-side cookie, also called a server-set cookie, is written by a web server in an HTTP response rather than by JavaScript on the page. It's still stored in the visitor's browser, but it often lasts longer because browser limits such as Safari's 7-day script cap don't cover it.

Identity & Recognition

First-Party Cookie

A first-party cookie is a small piece of data stored in the browser for the domain the visitor is on. Stores use them for carts, logins and recognizing returning visitors. How long one lasts depends on the browser and on whether a script or a server set it.

Identity & Recognition

Returning Customer Recognition

Returning customer recognition means knowing that a visitor is someone who has already given your brand their details, so the site can treat them accordingly. It relies on first-party signs such as logins, email clicks and stored identifiers, and it differs from naming strangers through an identity network.