Tracking hotel bookings when the booking engine is on another domain
Freetobook and booking engines like it host the reservation flow on their own domain, so the guest leaves your site partway through and the booking completes somewhere you can't tag freely. The result is the familiar pattern: paid campaigns show clicks and no revenue, and the booking engine appears as your top referrer. What's achievable depends entirely on what the engine allows — cross-domain linking and a confirmation-page tag if it permits them, and the property management system if it doesn't.
Free30 minutesNo obligation
Freetobook · what breaks
The situation, as it usually presents — Freetobook
- 01
Bookings credited to the booking engine as a referral
Not to the campaign.
- 02
Paid campaigns showing traffic and no revenue
The revenue landed elsewhere.
- 03
No visibility into where the booking flow loses people
Because half of it isn't yours.
Freetobook · the fix
What changes — Freetobook
Session continuity across the domain hop
Where the engine allows it.
Bookings attributed to campaigns
Rather than to self-referral.
Cancellations accounted for
Hotel cancellation rates make this material.
Freetobook · architecture
Why this pattern keeps recurring — Freetobook
Hospitality booking engines constrain what's possible in ways that are worth stating before any work is scoped.
- 1
The booking domain isn't yours
Cookies don't cross it, and whether you can tag it at all is the engine's decision, not yours.
- 2
Self-referral swallows the campaign
The engine sees a visitor arriving from your site and credits your site, not the ad.
- 3
Cancellation rates are high in hospitality
Counting bookings without reversing cancellations overstates revenue meaningfully in this vertical.
- 4
OTA and direct bookings are different channels
Mixing them makes direct look worse and paid look unaccountable.
Freetobook · diagnose
How the root cause gets found — Freetobook
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Check what share of revenue is self-referral
The signature symptom.
- 02
Establish what the engine permits
Tags, parameters, webhooks — this scopes everything.
- 03
Walk a real booking and read the URL on arrival
Does anything survive?
- 04
Confirm referral exclusions are set
Often not.
- 05
Check whether the property system exposes reservations
The fallback path.
Freetobook · prove
How the work is proven — Freetobook
Against the client's own records, not a dashboard turning green.
Source of truth
Reservation records in the property management system
- Identifiers confirmed surviving the hop, or the fallback path confirmed working.
- Self-referral revenue reduced to near zero.
- A real booking walked end to end.
- Reservations reconciled against platform conversions for a closed month.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Freetobook · free audit
What we check in the free audit
- Check what share of revenue is self-referral
- Establish what the engine permits
- Walk a real booking and read the URL on arrival
- Confirm referral exclusions are set
- Check whether the property system exposes reservations
Checked against
Reservation records in the property management system
Free30 minutesNo obligation
Freetobook · when not to buy
Why there are no client numbers on this page — Freetobook
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Freetobook · what we deliver
What the work involves — Freetobook
Engine capabilities established first
What can actually be injected or configured.
Cross-domain linking where supported
Both directions.
Referral exclusions set
So the engine stops being a source.
Property system used where the engine allows nothing
Reservation records as the event source.
Written guarantee
95%+ tracking accuracy
Measured against Reservation records in the property management system. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, for advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Freetobook questions, answered
Then the conversion comes from the property system's reservation record, with the click ID captured before the guest left your site. Lower fidelity, but it works.
Because the booking engine saw the guest arrive from your site with no prior session. That's the textbook cross-domain symptom.
In hospitality, yes. Cancellation rates are high enough that ignoring them materially overstates what your campaigns produced.
Not to your campaigns — the OTA owns that journey. Keep them separate so your direct-booking performance stays readable.
Free · 30 min
Attribute your direct bookings properly
WhatsAppFree30 minutesNo obligation
