Apple quietly broke your Google Ads tracking in 2021. Here's what server-side fixes

If you advertise an accommodation business and your Google Ads conversions look lower than the bookings you actually take, Apple's 2021 Safari change — which caps certain browser-stored cookies at roughly 7 days — is the most likely culprit. When a guest clicks your ad, browses, and then books two or three weeks later, the cookie that links that booking back to the ad has often already expired. The conversion fires, but Google can't match it to the click, so it goes uncounted.

This isn't vendor scaremongering. It's a documented, industry-wide measurement problem that hit every business with a long consideration window — and accommodation, where people deliberate for weeks before booking a getaway, got hit harder than most.

Here's the plain-English version of what happened, why it matters specifically for operators with min-stay and fixed-arrival rules, and what server-side tracking actually does to fix it.

What Apple actually changed

Apple's Intelligent Tracking Prevention (ITP) is a set of privacy features built into Safari. In a 2021 update, Apple extended an existing limit: cookies set through certain scripts on a website — the kind ad platforms use to remember "this visitor came from a Google ad" — would be automatically deleted after about 7 days.

Before this, that cookie could survive for months. A guest could click your ad in early March, sit on the decision, and book in April, and the cookie would still be there to tell Google "this booking came from that ad." After the change, the cookie is gone within a week.

Two things make this bite hard:

Safari is the default browser on every iPhone and iPad, so a large share of Australian leisure travellers are browsing in exactly the environment Apple restricted.

The change is client-side — it happens inside the visitor's browser, on their device, where you have no control.

So the data loss is silent. Nothing breaks. No error appears. Your campaigns keep running. The numbers just quietly go missing.

Why accommodation gets hit harder than most

The damage from a 7-day cookie cap is proportional to how long your customers take to buy. A $40 t-shirt gets bought the same day — well inside 7 days, so the cookie is still alive when the conversion fires. A $1,800 three-night Margaret River villa stay does not get bought the same day.

Accommodation booking windows are long by nature. People compare regions, check dates against school holidays, wait for a partner to confirm leave, and watch for a better price. Research consistently shows leisure-travel consideration windows running well past two weeks — comfortably longer than Apple's ~7-day cap.

Now add the wrinkle that's specific to operators with restricted stays. If you run a houseboat, a cabin block, or a Saturday-to-Saturday villa with min-stay or fixed-arrival rules, your guest's path is even slower. They search a date that doesn't fit your rule, get knocked back, go away, think about it, and come back later with workable dates. Every one of those extra days is another day for the cookie to expire before the booking lands.

The result: the booking happens, you take the money, but Google and Meta under-report the campaign that drove it. Your reports show fewer conversions than your bank account shows bookings, and you genuinely cannot tell which campaigns, keywords, or audiences are pulling their weight.

What under-reporting does to your decisions

Under-counting isn't a cosmetic problem. It actively steers you wrong, because the campaigns with the longest consideration windows are usually the ones that get under-credited the most — and those are often your highest-value bookings.

Picture an operator spending $3,000/mo on Google Ads. Their dashboard shows a return that looks marginal, so they trim the campaign that targets people researching a "long weekend on the Murray." But that campaign actually drives the slow-deliberating, high-value bookings — the ones most likely to fire after the cookie dies. The dashboard never gave them credit, so the operator cuts their best-performing campaign based on numbers that were broken from the start.

This is the trap. You're not making a bad call. You're making a sensible call on data Apple silently corrupted. Multiply that across a year of "optimisation" and you've quietly defunded what was working.

What server-side tracking actually does

Server-side conversion tracking moves the moment of recording off the visitor's browser and onto your own server.

Here's the conceptual difference:

Client-side (the old way): the visitor's browser holds a cookie and, when a booking completes, the browser reports the conversion. If Apple has deleted that cookie, the browser has nothing to report. The conversion is lost.

Server-side (the fix): your booking system records the conversion on the server when the booking actually completes, then sends that event to Google or Meta directly — server to server, not browser to browser. Because the record lives on your infrastructure rather than in a cookie Apple controls, the ~7-day cap doesn't erase it.

In other words, server-side tracking doesn't try to out-clever Apple's privacy rules. It simply stops depending on a browser cookie that Apple has decided to delete, and uses a durable server-side record instead. Done properly and within privacy law, this is the standard, above-board way the industry has responded to ITP — not a loophole.

For accommodation, this is the difference between guessing which campaigns drive bookings and seeing it. When the conversion is recorded server-side at the point of booking, the long consideration window stops being a measurement problem. A booking that lands 18 days after the click still gets attributed to the click.

How Accommador handles it

On Accommador, server-side ad attribution is included — it's simply part of the platform, not a feature you upgrade into. Because your branded booking engine and your ad tracking live in the same system, the conversion is recorded on the server the instant a booking completes, and that event is sent to your ad platforms without relying on a browser cookie that may already be gone.

• That means:
• Long booking windows stop costing you data. A guest who clicks today and books three weeks later still gets attributed correctly.
• You can finally compare campaigns on real numbers, not browser-truncated ones — which is the whole point of conversion tracking in the first place.
• The data turns into decisions, because attribution you can trust is what lets you scale the campaigns that work and cut the ones that don't.

It's worth being honest about scope: this is a real, structural fix to a real, structural problem, but it's not magic. No tracking method recovers 100% of conversions in a privacy-first world, and anyone who promises that is overselling. What server-side attribution does is stop the systematic, consideration-window-driven under-counting that makes accommodation spend so hard to read — which is the part that's actually costing you money. It's most valuable wherever consideration windows are long, which describes most independent accommodation regardless of size, so independent operators get the same measurement integrity larger players have been using.

And to be clear, this doesn't replace Google Ads or Meta. Server-side attribution doesn't change where you advertise; it changes how accurately your bookings are reported back to those platforms, so you can judge each campaign on real numbers.

The reason server-side attribution is built into Accommador is that your booking engine, channel manager, payments and CRM already live in one place — so the conversion can be recorded at the exact moment a booking completes, on your own infrastructure, instead of in a cookie Apple has already deleted. From $500 AUD/mo per location, everything included. Monthly billing, cancel anytime. Start free.