Cookie ITP & 3P Block Checker
Paste a Set-Cookie list — see which cookies survive Safari ITP, which Chrome will cap, and which are flat-out third-party blocked.
Used to decide first- vs third-party.
Healthy
1
ITP-limited
3
3P blocked
1
_ga
ITP-limited (1P JS)_ga=GA1.2.123456789.1700000000; Domain=.example.com; Path=/; Max-Age=63072000; SameSite=Lax
- · First-party but client-side (no HttpOnly) — Safari ITP caps lifetime to 7 days regardless of Max-Age.
- · Lifetime > 400 days — Chrome (since 100) caps to 400 days for first-party cookies set via Set-Cookie.
_fbp
ITP-limited (1P JS)_fbp=fb.1.1700000000.123456789; Domain=.example.com; Path=/; Max-Age=7776000; SameSite=Lax
- · First-party but client-side (no HttpOnly) — Safari ITP caps lifetime to 7 days regardless of Max-Age.
ads_session
Blocked / restrictedads_session=abc123; Domain=.advertiser.com; Path=/; Max-Age=2592000; Secure; SameSite=None
- · Third-party cookie — blocked by Safari ITP and most ad blockers; partially restricted in Chrome.
session
Short-lived 1Psession=opaque; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax
_gcl_au
ITP-limited (1P JS)_gcl_au=1.1.123.987; Domain=.example.com; Path=/; Max-Age=7776000
- · First-party but client-side (no HttpOnly) — Safari ITP caps lifetime to 7 days regardless of Max-Age.
- · No SameSite attribute — defaults to Lax in modern browsers.
Try these next
Related tools you'll probably want
Need to protect your tracking against Safari ITP?
I configure custom first-party tagging domains with server-side GTM to preserve tracking cookies for up to 1 year.
How to use the Apple Safari ITP & Cookie Lifespan Checker
Apple Intelligent Tracking Prevention (ITP) caps client-side JavaScript cookies (document.cookie) to 1 to 7 days, and as little as 24 hours if the user arrived from a link with a query parameter (like gclid or fbclid). This tool simulates how ITP impacts your tracking cookies and attribution windows.
Step by step
- Select the cookie type you want to audit (Google Analytics _ga, Meta _fbp, Google Ads _gcl_au).
- Select whether the cookie was set via client-side JavaScript or server-side HTTP Set-Cookie headers.
- Indicate whether the landing page visit included click identifiers (gclid, fbclid, utm_*).
- Review the calculated cookie lifespan under the latest Safari WebKit ITP policies.
How to read your result
Lifespan: 1 to 7 Days (Truncated)
Client-side cookies set via document.cookie are severely capped. Returning visitors after 7 days will be counted as brand new users in GA4, fragmenting attribution.
Lifespan: Up to 365 Days (Protected)
Cookies set via server-side HTTP response headers on a same-origin or first-party subdomain retain full lifespan under ITP.
Common mistakes
- Believing first-party JavaScript cookies are safe from ITP: WebKit explicitly targets client-side document.cookie.
- Using CNAME cloaking on a third-party IP address, which Safari ITP detects and truncates to 7 days.
- Analyzing multi-week customer sales cycles with client-side tracking, resulting in broken source attribution.
Questions
What is Apple Safari ITP?
Intelligent Tracking Prevention is a privacy feature in Safari and iOS that restricts cookies and storage mechanisms to stop cross-site tracking.
How do you bypass ITP legally and compliantly?
By setting cookies via your own server on a first-party subdomain (e.g., sgtm.yourdomain.com) with true HTTP Set-Cookie headers.
Need to protect your tracking against Safari ITP?
I configure custom first-party tagging domains with server-side GTM to preserve tracking cookies for up to 1 year.