Tracking14 min read2 views

Safari's 7-day cookie limit: how to keep ad attribution

Safari deletes ad click cookies that scripts set after 7 days of Safari use without an interaction on your site. When server cookies last longer, and the fix.

The short answer

Safari deletes cookies a page script sets, including the ad click cookies Meta and Google tags store, after 7 days of Safari use without an interaction on your site. A buyer who clicks your ad and books 10 days later can lose that click. Server-set cookies last longer, depending on where the server lives.

  • Script-set cookies and storage are deleted after 7 days of Safari use without a click, tap or keystroke on your site.
  • After a click from a site Safari counts as a tracker, script cookies on the landing page last 24 hours.
  • Server-set cookies escape that rule, unless the tracking subdomain points to a different provider than your site.
  • Google Ads counts conversions up to 30 days after a click by default. Meta counts 1 or 7 days.
  • Checked against WebKit's documentation and Crisper's live tracking setup on 5 November 2026.

Ask an assistant

ChatGPTClaudePerplexity

FREE AUDIT

NO LOGIN

Check what Meta and Google can count on your site

  1. Your site
  2. Crisper
  3. Meta and Google count it

Enter your website to see how good its tracking is, and whether Meta is likely restricting it.

Run a free audit

What does Safari's 7-day limit delete?

Safari deletes every cookie a script on your page created, and everything else a script stored, after 7 days of Safari use without an interaction on your site. That is the rule in WebKit's tracking prevention documentationwebkit.org, and WebKit is the engine Safari runs on. An interaction is a click, tap or keystroke; scrolling doesn't count, so a visitor who comes back and only reads doesn't reset the clock.

The cookies that matter for ads are the ones your tags read back later. _fbc holds the Meta click ID from the fbclid in your ad's link, and the Meta pixel saves it as soon as the click ID is availabledevelopers.facebook.com. _gcl_aw holds Google's ad click information, which the conversion linker stores in first-party cookiessupport.google.com. Both are written by a script in the visitor's browser, so both fall under the 7-day rule.

This is not an ad blocker, and it is not Safari's block on third-party cookies. These are first-party cookies on your own domain. Safari lets your tags create them, then removes them when the visitor stays away. It counts days the browser is used, not calendar dayssimoahava.com, so for someone on their phone every day it is about one week.

A script on your page (document.cookie)

Still there after a week away
No
What Safari does
Deletes it after 7 days of Safari use without an interaction on your site.

A script on a landing page reached from a tracker's link

Still there after a week away
No
What Safari does
Caps it at 24 hours, when Safari counts the site the click came from as a tracker.

Your own web server, on your site's network

Still there after a week away
Yes
What Safari does
Keeps the expiry the server gave it.

A tracking subdomain pointed at a different provider than your site

Still there after a week away
No
What Safari does
Caps it at 7 days when it is set.

LocalStorage and other script storage

Still there after a week away
No
What Safari does
Deletes it on the same 7-day rule as script cookies.
How long each kind of cookie lasts in Safari, from WebKit's ruleswebkit.org. "A week away" means 7 days of Safari use without an interaction (a click, tap or keystroke) on your site.

The second row needs a condition: WebKit applies it only when a site classified as a tracker sent the visitor, and the landing URL has a query string or a fragmentwebkit.org (the part after #). Apple doesn't publish which sites are classified, so treat ad clicks as possibly in that row. The fourth row also has conditions, covered in section 03.

How does it cost you ad attribution?

Your tags read these cookies to tie a sale or a booking back to the ad click that started it. When the cookie is gone, the conversion still happens, but it can arrive without the click that led to it. That can reduce what your ad platforms credit to the ad.

How often that bites depends on how long your buyers take. Google Ads counts conversions up to 30 days after a click by defaultsupport.google.com, and Meta counts conversions 1 or 7 days after a link clickfacebook.com. A Safari visitor who comes back after a week is outside the cookie's life but still inside Google's window. For Meta, the window and the cookie end close together, unless the 24-hour rule cuts the cookie to a day.

Fig. 1Example: a Safari visitor who books on day 10
  1. Day 1: they click your ad

    Your landing page saves the click ID in a cookie, with a script.

  2. Days 2 to 7: they stay away

    They use Safari every day but don't click, tap or type on your site.

  3. Day 8: Safari deletes the cookie

    Seven days of use without an interaction, so the click ID is gone.

  4. Day 10: they book

    Your tags send the booking without the click ID, so the ad may not get the credit.

The booking is real. The click that would credit the ad is gone.

Illustrated example, assuming Safari is used every day. Rules from WebKitwebkit.org.

A lost click cookie isn't the only way a platform matches a conversion. Google's enhanced conversionssupport.google.com, for example, match a hashed email to signed-in Google accounts. But the click ID is the most direct link between an ad and a sale, and when a conversion arrives without an email, or with one that doesn't match a signed-in account, it may be the only one.

The same thing shows up in your reports as a gap between the sales your CRM records and the conversions your ad platforms claim. If you're already chasing that gap, why Meta Ads Manager conversions don't match your CRM covers the other causes to rule out first.

Do cookies set by a server fix it?

Usually, with one condition. A cookie your server sends in its response is not written by a script, so the 7-day script rule doesn't apply. That is why Meta recommends setting _fbc as an HTTP cookie with a 90-day expirydevelopers.facebook.com.

The condition is how your tracking subdomain's DNS relates to your main site. Safari caps cookies from that subdomain at 7 days in two cases. The first is a CNAME record to another company's domainwebkit.org, unless your main site points to that same domain. The second is a subdomain with no CNAME whose IP address differs from your main site's in its first halfgithub.com. Both are common in hosted setups, so cookies set by servers behind them are limited to 7 days toosimoahava.com.

Crisper's tracking subdomain is set up the first way, and so are most hosted server-side setups. So moving to server-side tagging is often only half the fix in Safari. The other half is getting the cookie back after Safari trims it, which is what the next section compares.

What keeps ad click cookies working in Safari?

Four setups are common. One keeps the click cookie past a week away in Safari, one brings it back with conditions, and each has a cost.

Tags in the browser only

Click cookie after a week away
Nodeleted with the other script cookies
What it takes
Nothing new
Best for
Sites that don't run ads

Cookies from your own web server

Click cookie after a week away
Yeswith the full expiry
What it takes
A developer adds each cookie to your site's server responses and keeps it current
Best for
Sites with their own backend and a developer on hand

Hosted server-side tagging on a tracking subdomain

Click cookie after a week away
Nowhen the subdomain points to a different provider than your site, which is the usual setup
What it takes
DNS records and a tracking install
Best for
Resisting ad blockers and sending server events, not Safari cookie life

Hosted server-side tagging that can restore some cookies on return

Click cookie after a week away
Partialsome cookies can be restored when the visitor returns on the same network and browser
What it takes
DNS records and a tracking install
Best for
Owners who run ads and have no developer time for their own server
How we compared: one test, whether the click cookie is still there after a week away in Safari, judged against WebKit's published ruleswebkit.org on 5 November 2026. We make Crisper, the last row.

Pick the second row if a developer already runs your site's server and can own those cookies. If your site runs on a hosted builder, ask whether it lets you set cookies in its server responses before you choose that row. Pick the last row if you want the click cookies handled without that work. The third row on its own looks like the fix, and in the usual setup Safari still trims its cookies at 7 days.

A tracking subdomain also helps with ad blockers, which is a separate problem with its own limits: do ad blockers stop Google Tag Manager and analytics?

What does Crisper set up for this?

Crisper runs your tracking on your own subdomain, ctx. followed by your domain, and sets cookies from there. Meta's _fbc and _fbp are set by the server as 90-day cookies, matching what Meta recommends for _fbcdevelopers.facebook.com. The Google Analytics visitor ID, FPIDsimoahava.com, is set by the server too, and so is Google's click cookie FPGCLAWsimoahava.com when Google Ads is connected and the visit came from a Google ad click. Crisper also keeps its own copy of each ad click ID, such as _raw_gclid and _raw_fbclid, as a 90-day server cookie. The browser's own _gcl_aw and _ga stay script cookies.

That subdomain points by a CNAME record to the servers that run Crisper's tracking, so Safari caps those cookies at 7 days like other hosted setups. So on Safari 16.4 and later, ad click cookies that the browser cleared can come back when the visitor returns on the same network and browser. They come back with the values they had before. In our test on 17 Nov 2026, that brought back Meta's _fbc and _fbp and the Google Analytics ID FPID. The browser's own _ga came back as a new ID. How Crisper works lists it with the rest of the setup.

When a click ID was captured, it also travels with the events Crisper sends from the server, so a conversion sent that way can carry it to Meta and Google. Your free audit report lists this fix under the work Crisper does with you on the call.

For your developer: how do you check it?

Three checks, in order. Each needs Safari on a Mac with its developer tools on: choose Safari, Settings, Advanced, then Show features for web developerssupport.apple.com. Check 1 shows who sets each cookie, check 2 shows whether Safari caps it, and check 3 tests a restore.

1. Find out who sets each click cookie

  1. Start clean: choose Safari, Settings, Privacy, Manage Website Datasupport.apple.com, select your site and click Remove.
  2. Open a new tab, choose Develop, Show Web Inspector and select the Network tab before you load anything, so the first page load is recorded.
  3. Load a page on your site with a Meta test click ID in the address: ?fbclid=test123. Check 3 needs the _fbc this creates.
  4. If your site shows a cookie banner, accept advertising cookies, then wait until the page stops loading so every tracking request is recorded.
  5. In that first load, search the responses for Set-Cookie lines naming _fbc, _fbp or FPID, and FPGCLAW if you also add a real Google ad click's gclid. Note which host sent each one and the Max-Age or Expires it asked for.
  6. Open the Storage tab, then Cookies. A click cookie that exists with no Set-Cookie line in that first load was written by a script.

Done when you know, for each click cookie, whether a script or a server response created it, which host sent it, and the expiry it asked for. Look at the first load only: a server usually sets these cookies once, so a later reload with no Set-Cookie line proves nothing.

2. Check whether Safari caps the server cookies

  1. Compare the expiry each Set-Cookie line asked for with the expiry the Storage tab shows. If the server asked for 90 days and Safari stored about 7, Safari capped it.
  2. To see why, run dig +short CNAME on the host that sent it, for example dig +short CNAME ctx.example.com.
  3. If it returns a domain outside yours that your main site doesn't also point to, that is the CNAME casewebkit.org.
  4. If there is no CNAME, run dig +short A and dig +short AAAA on the tracking host and on your site. Safari compares addresses only when there is no CNAME, and caps the cookie when the first half differsgithub.com: the first two numbers of an IPv4 address, or the first four groups of an IPv6 one.

A script on the page

What the first load shows
No Set-Cookie line for _fbc
Stored expiry
Don't trust the date shown: Safari deletes it after 7 days without an interaction

Your own web server, same network as the site

What the first load shows
Set-Cookie from your main host, such as www.example.com, asking for 90 days
Stored expiry
About 90 days out

A tracking subdomain on a different provider

What the first load shows
Set-Cookie from a host such as ctx.example.com, asking for 90 days
Stored expiry
About 7 days out
What checks 1 and 2 should show for _fbc after a clean first load in Safari, from WebKit's ruleswebkit.org and the 90-day expiry Meta recommends.

Done when you know, for each server cookie, whether Safari kept the expiry it asked for. A cookie that keeps it is past the 7-day limit, and you can stop here. One that Safari capped needs check 3.

3. Test a restore

This check is for setups that restore cookies, such as Crisper's. Use Safari 16.4 or later, run it straight after check 1 in the same window, and keep advertising consent accepted.

  1. After check 1, open the same page again without the test click ID in the address.
  2. In the Storage tab, confirm _fbc exists and note its value (it ends in test123), then right-click it and delete it.
  3. Reload the page twice.
  4. Check that _fbc is back with the value you noted.

Done when _fbc returns with the same value. If it doesn't come back in this test, check the Safari version, that the page loads the tracking code from your tracking subdomain, and that consent allows advertising cookies, then run it again.

Three fixes that look right and aren't:

  • Copying click IDs into localStorage. Safari deletes script storage on the same 7-day rule.
  • Writing a longer expires in document.cookie. Safari still deletes the cookie after 7 days without an interaction.
  • Assuming a server-side tag manager fixes it. Run check 2 on its cookies.

One more Safari change for your developer to know: since Safari 26, known fingerprinting scripts can't set long-lived cookies or read query parameterswebkit.org. A tag on that list may never see the click ID, while a server reading the same request still does.

What can't a cookie fix?

  • A click ID that never arrived. In Private Browsing, Safari removes known tracking parameters from linkssupport.apple.com, so there is nothing to save.
  • A buyer on another device or network. Restoring a cookie works only when the return visit comes from the same network and browser. A click on a phone followed by a booking on a laptop has no cookie to restore; only other details, such as a hashed email, can connect them.
  • A tracking install that sends nothing. If events aren't arriving at all, fix that first: how to verify Meta conversion tracking walks through the checks.

Should you fix this now?

If you don't run paid ads, Safari's limit mostly changes your returning-visitor counts. If you run ads and your buyers often take more than a week to book or buy, it can cost you credit for real sales, and your campaigns learn from fewer of them.

We recommend Crisper if your report flags script-set cookies and you'd rather not build cookie handling into your own server: it sets the click cookies from your tracking subdomain and can restore some of them on Safari return visits. You still need the DNS records and the tracking install, and the restore covers Safari 16.4 and later on the same network and browser.

Sources

16 sources
  1. 1WebKit's tracking prevention documentation↩
  2. 2as soon as the click ID is available↩
  3. 3conversion linker stores in first-party cookies↩
  4. 4not calendar days↩
  5. 5a site classified as a tracker sent the visitor, and the landing URL has a query string or a fragment↩
  6. 630 days after a click by default↩
  7. 71 or 7 days after a link click↩
  8. 8enhanced conversions↩
  9. 9CNAME record to another company's domain↩
  10. 10IP address differs from your main site's in its first half↩
  11. 11FPID↩
  12. 12FPGCLAW↩
  13. 13Show features for web developers↩
  14. 14Manage Website Data↩
  15. 15known fingerprinting scripts can't set long-lived cookies or read query parameters↩
  16. 16known tracking parameters from links↩