Attribution

Attribution for hotels, resorts and vacation rentals: a map of where it breaks

Hospitality has a harder version of the attribution problem than almost any other industry, and it is not because the marketing is more complicated. It is because a booking has three common routes to your revenue and each one severs the connection to the advertisement in a different place. Most hotel and resort accounts are optimising against whichever route happens to survive.

Answer first

Map your bookings to three routes before you argue about any number. The route that goes through a booking engine on another domain, where the session restarts and the campaign is lost. The route that goes through a person on the phone or an email thread, which the advertising platform never sees. And the route that goes through an online travel agent, where no click ever touched your systems and never will. The first is a configuration problem, the second is a system and a habit, the third is a floor to be stated rather than solved. Fix them in that order, report each share separately, and stop treating one blended number as the truth.

Three routes, three different breaks

Guest sees an ad Your property page campaign still attached Phones or emails the team no page view, no form Goes to an online travel agent never reaches your site Booking engine on another domain A person takes the booking The agent takes the booking Confirmed booking clicks through rings instead books elsewhere the session restarts no click is recorded no click exists at all records the revenue
Three routes to the same booking record, each severing the link to the advertisement at a different point. The marked steps are where the chain of custody breaks in a typical hotel, resort or rental account.

The hand-off. Your website is on one domain and the booking engine is on another. Unless cross-domain measurement is configured on both sides, the guest who clicks through to check availability is treated as a brand new visitor arriving from your own site, and the campaign that paid for them is left behind on the previous page. The booking still happens. The record of what caused it does not survive the boundary.

The conversation. In hospitality, the higher the value of the stay, the more likely somebody wants to speak to a human before committing. Those calls and emails are invisible to the advertising platform, which does not see a slow conversion, it sees no conversion at all. In one luxury vacation rental account, 61 percent of bookings began with a phone or email conversation with staff. Every optimisation decision in that account had been made on the minority.

The floor. In that same account, 27 percent of bookings came through online travel agents. There is no click anywhere in your systems to find, because the guest was never in your systems. This is not a tracking failure and it cannot be fixed by better tagging. It is a share of your business that arrives through somebody else’s shop window.

Those three routes are why hospitality accounts so reliably report a healthy cost per acquisition on a small, unrepresentative slice of the revenue.

What the reconciliation actually showed

In that luxury vacation rental account, Google Ads reported $173,555 of revenue across a two month window. We reconciled it against GA4 and against the property management system, which is where the reservations genuinely live.

Once every booking carried the identifier of the click that produced it, $100,646 could be traced to a confirmed reservation. The remaining $72,909, which is 42 percent, was not fraud and it was not lost money. It was revenue the account could no longer claim credit for.

That is a more useful thing to know than it sounds. The platform had been favouring campaigns on the strength of conversions it could see, and once the provable bookings were the input, the budget moved. There were also 12 search ads landing on the homepage before the restructure, which is its own kind of leak: a guest looking for a specific property, delivered to a general page, in an account that could not tell you whether it mattered.

What to do first, and why the order pays

Repair the hand-off. This is configuration rather than engineering. Both the site and the booking engine have to agree that they are one journey, and the identifier has to survive the jump. It is the cheapest of the three fixes and it makes the next two work better, because a repaired hand-off means the identifier is still present when the enquiry or reservation is created. The mechanics are in why your sales say Direct.

See the conversation. Call tracking with dynamic number insertion so the call carries its campaign, a single field for whoever takes the booking to record the outcome, and only qualified conversations imported back to the platform, with a value. The habit is the hard half, not the technology. The full version is in when customers call instead.

Build the join. Carry the click identifier from the landing page into the enquiry and then into the reservation record in the property management system, then send confirmed bookings back to the platform as offline conversions with their real values. This is the step that changes bidding rather than reporting. It is set out in full in the missing join, and it is the reason we eventually built BookingBridge rather than doing it by hand for every property management system.

State the floor. Report the OTA share separately and stop apologising for it. An account that proves three quarters of its revenue and names the reason for the rest is in a far stronger position than one claiming everything.

Two things that make hospitality harder still

The booking window. Somebody researching a villa in March for a stay in August is outside most default conversion windows and well outside most identifier storage defaults. If your sales cycle is longer than the storage you gave the identifier, the thread is cold before the money arrives. Set that storage deliberately.

Cancellations and modifications. A reservation is not final. It gets amended, shortened, upgraded and cancelled, and none of those corrections reach your analytics. The property management system knows the real value of a stay; the tag that fired on the confirmation page never will. Any number you report should come from the system that holds the money, not from the one that watched the browser.

Where this genuinely cannot reach

A guest who enquires on a phone and books on a laptop has used two browsers, and there is no honest way to connect them without a login. View-through conversions leave no identifier at all. Word of mouth, a returning guest and a repeat booking made by ringing a number saved two years ago are all real revenue with no digital trail whatsoever.

The right response is to name those shares rather than model over them. Every number above belongs to one account in one two month window, and the reason we can publish it is that it was reconciled against the reservation system rather than assembled from a dashboard. Your own mix will be different, and finding out what it is comes before deciding what to do about it.

Where this sits

These three are the three places a chain of custody breaks, seen from a hospitality account specifically. The order is the same everywhere: repair the hand-off, see the conversation, build the join. What changes in hospitality is the size of each break, and the fact that a floor exists which no amount of instrumentation will lift.

That order is the whole of the method. Proof before spend, and a report that says what it cannot see.

Find out what you can’t prove.

Free Attribution Leak Audit. Five working days. No pitch inside.