Three places a resort booking can be claimed, and only one is true
A guest clicks a Meta ad, checks the price on an OTA a day later, then calls the resort directly and books over the phone. Meta claims the booking because its ad was in the path. The OTA's own reporting may still count the visit as an attributed lead. The resort's own books show the true number: one confirmed reservation, taken by phone, paid for once. Add up what the platforms report and it can look like the resort earned three times what it actually did.
The OTA blind spot
OTAs are useful for visibility, but they rarely hand back clean data on why a guest actually booked direct instead. A resort running ads to compete with its own OTA listings, without a way to see which channel a phone or walk-in booking actually came from, ends up guessing at the split between paid, direct, and OTA-influenced revenue, and budget decisions get made on that guess.
A resort can be profitable and still look unprofitable on a Monday report, simply because nobody reconciled what three different systems each claimed credit for.
What proper attribution looks like for a resort
- The booking engine's confirmed-reservation event wired to GA4 and to each ad platform's conversion API, not just a page view or a rate-check click
- Phone and walk-in bookings logged with an asked source, so offline revenue doesn't vanish from the picture entirely
- Consistent UTM tagging across every channel, including the OTA listing where a direct link is possible
- A monthly reconciliation between what each platform claims and what the booking calendar actually shows, so double-counted credit gets caught before it shapes next month's spend
Why this matters more once ad spend scales
At small spend, a resort can absorb a fuzzy attribution picture and still come out fine. Once meaningful budget goes into Meta and Google, an unreconciled gap compounds: money keeps flowing toward whichever platform's dashboard looks best, whether or not it's the platform actually filling rooms.