For hotels & travel
The booking converts. The stay is what pays.
Your conversion fires when someone books. Your revenue exists when they arrive. Between those two moments sits a cancellation rate that differs by channel, lands outside every attribution window, and never reaches the algorithm that spent the money. Your own accounting already knows this — a deposit is a liability, not revenue. The ad platform is the only system in your business that books it as a win.
The cancellation arrives about 79 days after the click.
Across 90 million bookings in 180 countries, the average booking window runs 40 days and the average cancellation lands 39 days before arrival [Cloudbeds, Mar 2026].Add them together and the outcome that decides whether the campaign made money shows up long after every attribution window has closed. The bidding algorithm is not ignoring it. It structurally cannot see it.
- Booking confirmed, revenue attributed on the day of click
- ROAS calculated and reported
- Budget scaled toward the campaign that produced it
The number never gets corrected. A canceled booking stays in the report permanently.
- Cancellation is a channel property, not noise. OTA bookings cancel at 21.8%; direct bookings at 10.6% [Cloudbeds, 2026].
- Two campaigns with identical reported ROAS can differ by more than 20 points of survival to arrival.
- The highest-ROAS campaigns are often the least incremental — branded search and retargeting intercept demand you already owned.
Same reported return. Completely different businesses underneath.
On stayed nights rather than booked nights, it moves from first to third.
Metasearch falls from first to third on stayed nights.
The one mechanism that priced this risk was removed.
Google discontinued commission-per-stay bidding for hotels on 20 February 2025 [Hospitality Net, Apr 2025].Under that model the platform carried the cancellation risk — you paid on stays, not bookings. Removing it handed the risk back to advertisers wholesale, and nothing in the ad tooling replaced it.
One account reported $139,500 in revenue at 6.98× ROAS. Underneath: fourteen canceled bookings worth $21,000 stayed in the reports permanently, while forty-three real bookings were never tracked at all — total coverage of 68.4% [Stape, Jun 2026].The reported figure was wrong in both directions at once, which is why it looked plausible.
Dashboards aggregate by click date. You decide by arrival date.
"Last 30 days ROAS" answers a question no revenue manager asks. The same campaign is simultaneously right and wrong depending on which night the booking is for: on a compression night the spend is pure waste, because those rooms were selling anyway. On a need period thirty to sixty days out, it is the highest-value action in the account.
It is called the pace report, and revenue management reads it every morning — pickup measured at 30, 14 and 7 days out, against same time last year. There is simply no equivalent artifact for ad spend.
A closed period keeps changing as cancellations land. Any figure you reported at month-end was provisional and nobody said so.
Paying to reacquire guests who were already coming to you is the most reliably profitable-looking spend in the account, and the hardest to justify on incrementality.
Notice that a quarter is barely longer than one cycle of this. At 79 days from click to cancellation, a decision deferred to next quarter is a decision made on bookings whose outcome is still in flight — and in the meantime budget keeps flowing toward the channel cancelling at 21.8% rather than the one at 10.6%, because on reported ROAS they are indistinguishable. Since February 2025 that risk sits with you, not the platform. Waiting is not holding the position. It is funding the wrong channel for one more booking window.
The outcome arrives 79 days after the click.
A quarter is barely longer than one cycle of this, so a decision deferred to next quarter is a decision made on a number that has not finished happening yet.
- 79 daysfrom click to the cancellation that undoes it
- 2×the cancellation rate of your direct bookings
- 3rdwhere metasearch lands on stayed nights, not first
The honest line, since this vertical deserves one.
Stayed revenue lives in your PMS or CRS — Opera, Mews, Cloudbeds. Adgent does not read those today, so it cannot compute a stayed-revenue ROAS or split cancellation rate by campaign. Property-system reading is the roadmap item that would close this, and we would rather name it than imply it is finished.
It reads every account daily, not monthly
In a business where the reported number silently restates itself for months, the value of catching a drift in week one rather than at month-end is not marginal.
It reconciles against GA4 and Search Console
On-site behavior after the click, and the relationship between paid and organic — including the case where paid search is buying clicks that organic was already winning.
It refuses targets your history says are unreachable
The Trust Gate pushes back before budget moves, with the account's own numbers as the reason. In a seasonal business with compressed booking windows, a wrong target discovered in week four has already cost the season.
The general mechanism behind the travel-specific problem.
Every vertical on this site has its own version of the same gap: the platform optimizes toward what its pixel can see, and the number that decides the business is somewhere else.
The same read on every client you run — including the ones nobody opened this week. A revenue manager who hears the compression-night argument from your team, not from their own P&L, is a client who stays.
How this works across a book of accountsSee which channels book, and which ones cancel.
We will read your accounts against the pattern this industry lives with: reported returns that never retract, and brand spend defending demand you already owned.
- Daily read, not a month-end figure that restates itself
- Paid and organic seen together, so cannibalisation shows
- Property-system reading is the roadmap item that closes this
Where your paid spend is intercepting demand rather than creating it — and what your reported returns look like once that is separated out.
Thanks — we’ve got it.
We’ll be in touch within a couple of working days.