Clicks and WhatsApp enquiries may indicate interest, but a hotel campaign needs a reliable view of completed paid reservations. When your website sends guests to a separate booking engine domain, conversion tracking can become fragmented.
Set measurement rules before increasing spend. The objective is one trustworthy booking event, the right value and a way to reconcile advertising reports with your reservation system.
The process at a glance
Use this visual workflow to identify which platform, owner or reporting layer comes next.
- 1Ad click with attribution
- 2Hotel site and booking engine
- 3Booking confirmation event
- 4GA4 and Google Ads reporting
Define one authoritative purchase event
A completed reservation should generate a stable transaction ID from the booking system. Fire a purchase event when confirmation is genuinely reached, not on every visit to the booking widget or payment page.
If bookings can fail after payment initiation, ask the engine provider for the proper server-side or confirmation-based event. Avoid counting retries or page refreshes as new bookings.
Practical checklist
- Specify the booking-confirmation trigger.
- Include transaction ID, currency and total booking value.
- Test that the same booking fires only once.
Configure GA4 and Google Ads intentionally
Use Google Tag Manager or the booking engine's supported tracking integration to send the transaction information. In GA4, check DebugView and purchase reports; in Google Ads, verify the purchase conversion action and the attribution source.
Depending on your chosen implementation, conversions may be tracked with a Google Ads tag or imported from GA4. Avoid importing duplicates as separate primary conversions for one reservation.
Practical checklist
- Use a consistent purchase event name.
- Check conversion value and currency.
- Designate primary and secondary goals appropriately.
Handle payment and booking-engine redirects
When a hotel website and booking engine use different registrable domains, configure supported cross-domain measurement where permitted. Maintain source attribution through booking completion and exclude inappropriate payment referral sources.
Test the actual path from an ad-tagged landing URL to a final confirmation. A booking confirmed on another domain may otherwise appear as direct traffic or a new referral.
Practical checklist
- List all booking domains and payment redirects.
- Test GA4 session continuity.
- Inspect Google Ads click attribution where available.
Reconcile measurement with hotel operations
Create a weekly report that compares GA4 purchases, Google Ads conversions and actual reservation exports. Time zones, attribution windows, cancellations and cross-device behavior can cause legitimate differences.
Use the reconciliation to identify broken tags and duplicated revenue, rather than forcing every platform to show exactly the same conversion count.
Practical checklist
- Compare booking IDs where privacy rules permit.
- Track cancellations separately.
- Document discrepancies and the correction owner.
Common mistakes to avoid
- Tracking click-to-booking-button as a completed sale.
- Omitting transaction IDs and purchase values.
- Counting a Google Ads tag and imported GA4 purchase twice.
Frequently asked questions
Should hotels track enquiries as well as bookings?
Yes, but distinguish lead events from completed reservations and avoid treating both as the same purchase.
Why are Ads and GA4 booking counts different?
They can differ because of attribution, consent, time zones, conversion windows and implementation issues. Reconcile against confirmed booking records.
Official Google resources
This guide uses Google's product documentation. Interface labels and eligibility can change; verify them in the connected account.
Continue learning
The complete series links connectivity, campaigns and the commercial direct-booking journey.