Your booking engine is on another domain, and that is where your marketing data disappears

What actually happens

A guest clicks an ad, lands on your website, browses two room pages and clicks "Book now". At that moment they leave your domain for the engine's: a subdomain of the vendor rather than of your hotel. Unless three things survive that jump, the booking is invisible to your marketing: the analytics linker that carries the session identifier, the click identifiers from the ad platforms, and the tag container itself. When they do not survive, the booking is recorded as direct traffic or as a referral from your own website, and the campaign that produced it appears to have produced nothing.

Browser policy makes it worse. A cookie set after arriving via a decorated link can live as little as twenty-four hours on some browsers, and a normal script-set cookie about seven days, against a hotel research cycle that commonly runs to two or three months. The guest who saw your advertisement in March and booked in May is not connected to it by any mechanism you have.

Why it matters more now than it did

Advertising platforms have moved to automated bidding that consumes your conversion data. Commission-based bidding on hotel advertising was withdrawn in 2024, and what replaced it depends on the property's own conversion signal. Every property now needs its own working conversion signal in order to bid at all, at exactly the moment that signal is least reliable. Properties in this position typically under-invest in the channels that work and over-invest in the channels that happen to get credited.

The fix, in payback order

1. One measurement setup across both domains. The same analytics property configured on the website and the engine, with cross-domain linking so the session survives the jump. Often a configuration change on both sides and nothing more.
2. Click identifiers passed through. Campaign parameters and click IDs carried into the engine URL and, where the vendor allows it, written into the reservation record so a booking can be matched to a click later.
3. A first-party domain. The engine on a subdomain of your own site, or at minimum the tag server, which restores a usable cookie lifetime rather than a day.
4. Server-side conversions. The reservation itself sent to your analytics and ad platforms with hashed guest details, so revenue is reported even when the browser has lost the trail. This is also what makes offline and phone bookings measurable.
5. Consent carried across. Consent state passed with the guest, so measurement and law agree.

Almost no small or mid-size property has all five. Most have one.

The setup that cannot be fixed

A booking engine served inside an un-bridged third-party iframe cannot be measured properly, whatever is done around it. That is a vendor decision rather than a configuration one, and it is worth knowing before another year of media is bought against it. We show the evidence; changing vendor is the owner's call, and it is not the first move.

How to check yours in ten minutes

Open your site in a private window, arrive through a link with campaign parameters, click through to the booking engine and look at the address bar. If the parameters and the linker fragment did not survive, they are not reaching your reservations either. Then compare last month's bookings in your property management system against what your analytics reports as direct: if analytics claims materially more direct traffic than your reservation source data supports, the gap is the measurement, not the guest.