Before you spend another pound on ads, answer one question: do you actually trust your booking numbers? Most tour operators don't realise how much their conversion data understates reality — and the check takes about twenty minutes.
Take the quick self-assessment below. Answer seven questions about your setup and you'll get an instant Tracking Health Score out of 7 — a fast read on how much of your real booking data your ad platforms are actually receiving. Running the check is the easy part; fixing what it reveals is server-side tracking, which we build into every Google Ads and Meta Ads engagement.
The seven checks, explained
Prefer to read it through, or want the detail behind each question? Here's exactly what each check looks for and what a pass and a fail look like.
The seven checks at a glance
| Check | Pass looks like | Fail looks like |
|---|---|---|
| 1. Platform vs GA4 | PASSGA4 within ~10% of your booking platform | FAILGA4 falls well short |
| 2. iPhone Safari booking | PASSthe Safari booking shows everywhere it should | FAILit shows on Chrome but not Safari |
| 3. Double-counting | PASSone action counts each booking once | FAILduplicates inflate your numbers |
| 4. Meta Event Match Quality | PASSEMQ in the Good or Great range | FAILEMQ low and Meta optimising half-blind |
| 5. Cookie declines | PASSConsent Mode v2 keeps recovering data | FAILtags fully blocked when someone declines |
| 6. Cross-domain hops | PASStracking survives every hop | FAILit breaks at checkout |
| 7. Attribution window | PASSwindow at least as long as your lead time | FAILshorter than how far ahead people book |
Check 1 — Does your booking platform match GA4?
This single comparison is the fastest tell. The gap between the two numbers is, almost exactly, the money your bidding algorithms are making decisions without. Pass if GA4 is within roughly 10% of your platform; fail if it falls well short.
Check 2 — Does a booking on iPhone Safari actually track?
Pass if the Safari booking appears everywhere it should; fail if it shows on Chrome but not Safari — the most common and costly tracking failure in travel.
Check 3 — Are you double-counting conversions?
Pass if one action counts each booking once; fail if duplicates are inflating your numbers and flattering weak campaigns.
Check 4 — Is your Meta Event Match Quality healthy?
Pass if EMQ sits in the “Good” or “Great” range; fail if it’s low and Meta is optimising half-blind.
Check 5 — Does declining cookies kill your tracking?
Pass if Consent Mode v2 modelling keeps recovering data; fail if tags are fully blocked the moment someone declines.
Check 6 — How many domains does a booking pass through?
Pass if tracking survives every hop; fail if it breaks at checkout. This is the failure we see most often — covered in depth in our guide to booking attribution.
Check 7 — Does your attribution window match your booking lead time?
Pass if your window is at least as long as your typical lead time; fail if it’s shorter than how far ahead people book.
What your score means
7 / 7 — Rare. Your measurement is genuinely solid; only dig deeper if reported conversions and real revenue still disagree. 4–6 / 7 — You’re optimising on partial data; the leaks are fixable, but every day they run your bidding learns from the wrong signals. 0–3 / 7 — You’re effectively flying blind, and no amount of bid tweaking fixes a measurement problem this size.
What your score means
| Score | What it means |
|---|---|
| 7 / 7 | Rare. Your measurement is genuinely solid — only dig deeper if reported conversions and real revenue still disagree. |
| 4–6 / 7 | You’re optimising on partial data. The leaks are fixable, but every day they run, your bidding learns from the wrong signals. |
| 0–3 / 7 | You’re effectively flying blind — no amount of bid tweaking fixes a measurement problem this size. |
Failed a few? Here’s the fix
If you flagged even two or three checks, the answer isn’t another tag — it’s server-side tracking, which sends booking data from your server (not the browser) straight to the ad platforms with the real value attached. We explain how it works in our booking attribution guide, and build it into every Google Ads and Meta Ads engagement.
Frequently asked questions
How do I know if my tour booking tracking is accurate?
Compare confirmed bookings in your booking platform against purchase events in GA4 over the same 30 days. If GA4 reports meaningfully fewer, your tracking is leaking. Your booking platform processed the payment, so it is the source of truth — any shortfall in GA4 is data your ad platforms never received.
Why do my Google Ads conversions not match my actual bookings?
Usually because the booking completes on a different domain (the booking platform), on iPhone Safari where tracking prevention blocks tags, or after a visitor declines cookies. Browser-based tracking misses all three. Server-side tracking sends the conversion from your server instead, recovering the bookings the browser dropped.
Can I fix tracking myself or do I need an agency?
You can run the diagnosis yourself in about 20 minutes using the checks above. The fix — a server-side container that sends conversions with their booking values to Google and Meta — usually needs someone who has configured it for booking platforms before, because FareHarbor, Bokun and Peek Pro each break in their own way.
How often should I audit my conversion tracking?
Re-run this self-audit quarterly, and immediately after any change to your booking platform, website, cookie banner, or ad account structure. Each of those can silently break tracking overnight, so a change is the most common moment for a previously healthy setup to start losing bookings.
Want us to audit it for you?
Failed a few of these checks? Send us your setup and we’ll run a full tracking audit — quantifying exactly how many bookings you’re missing. Free, no obligation.
Claim your free tracking audit →