How do I track completed bookings across my hotel website and booking engine?
Connect the website visit to a confirmed reservation, then check the booking value and marketing source against your hotel’s records.
To track hotel booking engine conversions, record a confirmed reservation as a GA4 purchase with a unique transaction ID, value and currency. Connect your website and booking engine through cross-domain measurement, where supported, and respect consent choices throughout. Test the complete journey, including payment redirects and confirmation-page reloads, then reconcile purchases, cancellations and refunds with the PMS. A booking-button click measures interest, not a completed reservation.
Define the events and who owns them
Agree what “confirmed” means with the provider before configuring tags. Assign a website developer to the handover, the booking engine provider to confirmation data, and your analytics specialist to validation. You need GA4 editing access and authorised access to the relevant tags or GTM containers on both sides.
| Event | Trigger and owner | Required evidence |
|---|---|---|
| book_now_click | Custom diagnostic event; website developer | Booking button used; record its location without guest details. |
| begin_checkout | Checkout begins; booking engine provider | Selected items, value and currency where available. No confirmed booking yet. |
| purchase | Reservation confirmed; provider and analytics specialist | Unique transaction_id, numeric value, currency and items; tax separately where applicable. |
| refund | Refund issued; agreed finance/integration workflow | Original transaction_id, refunded value and currency; item details for item-level reporting. |
Use purchase for the booking outcome in your reports. GA4’s recommended events require implementation; enabling enhanced measurement does not create ecommerce tracking.
Connect the domains without losing the source
Follow Google’s cross-domain setup: both domains must send to the same GA4 web stream using the same G- measurement ID. Add the relevant domains in that stream’s Google tag settings under “Configure your domains”. The provider must support this on its booking pages.
Test the actual booking button. Check that the destination receives the _gl linker parameter and that the consenting test visitor’s client and session IDs remain continuous. Redirects must preserve the handover. An embedded booking frame needs a provider-supported implementation; measuring only the surrounding website is insufficient.
Use unwanted-referral settings for a payment processor that incorrectly receives source credit. Referral exclusion does not itself join visitor identities. Keep genuine referral partners visible, and avoid adding new UTM campaign tags to internal booking links.
Test consent on both sides
Check acceptance, refusal and withdrawal across the whole journey. Cross-domain linking does not automatically transfer consent. Keep names, email addresses, telephone numbers and guest-identifying URL parameters out of analytics.
Consent mode adjusts Google tags; it is not a consent banner or a compliance guarantee. Basic mode blocks Google tags when consent is denied; advanced mode can send cookieless measurements. Agree which implementation is appropriate before enabling it.
The ICO’s statistical-purposes exception is limited to qualifying aggregate analytics with safeguards and an objection route. Do not assume it covers advertising attribution or individual visitor tracking; non-exempt storage/access requires consent.
Run test bookings with known results
Use an agreed test environment or controlled test reservations. Your developer should inspect GTM Preview, Tag Assistant and GA4 DebugView, then check processed reports. Record the test time, device, consent state, transaction ID, expected amount and actual result.
Illustrative example: a test reservation has three room nights at £200 excluding VAT, with £120 VAT entered in the fixture. Total booking value is £720; the fully prepaid test collects £720. This is a fictional fixture, not a room quote or a tax rule.
| Check | Expected result |
|---|---|
| Transaction | transaction_id: TEST-2601; one purchase for this reservation. |
| Value and items | value: 600; room-night item price: 200; quantity: 3. |
| Tax and currency | tax: 120; currency: GBP. No currency symbol in numeric fields. |
| Deposit variant | If only £180 is collected, booking value remains 600 excluding VAT; cash collected is recorded separately. |
Google’s purchase specification excludes tax and shipping from value. Check how your provider maps its booking total to that definition.
- Complete a desktop and mobile booking from a known campaign source. Check session source/medium after processing.
- Check refused consent against the agreed tag behaviour. An abandoned checkout or failed required prepayment must not trigger a purchase.
- Reload and revisit confirmation. Keep the same transaction ID and prevent duplicate tag firing.
- Run a second booking. It must have a different, non-empty transaction ID.
- Refund the fully prepaid fixture and verify the original ID and correct refunded amount.
Transaction IDs help GA4 deduplicate purchases, but still check for competing native tags and GTM tags. Never generate a new ID on each confirmation-page view.
Reconcile bookings, cancellations and refunds
Compare the same booking-creation period, time zone, currency and tax basis. Filter PMS records to website/booking engine reservations: telephone, email and OTA bookings do not belong in this comparison. Separate booked revenue from cash received and revenue earned during the stay.
A PMS cancellation does not automatically update GA4. For an actual refund, send a refund event through a supported, validated workflow. The fully refunded fixture reverses £600 of purchase value plus £120 tax; it does not erase the original booking event. Track cancellations without refunds separately, including retained charges.
Use a reservation export if no suitable integration exists. Record unmatched bookings and reasons; consent choices, blockers and processing delays can prevent a complete transaction-by-transaction match.
What to verify with RoomRaccoon
RoomRaccoon’s UK hotel booking engine page lists Google Tag Manager integration. Before choosing a configuration, ask which package supports the required events, who controls the container, and how transaction IDs, tax, consent and confirmation redirects are handled.
Its hotel reporting tools include revenue and deposit reporting. Request the exact export fields needed for reconciliation; availability of a report does not establish an automatic GA4 refund connection.
Bring your website and booking URLs, event plan and £720 test scenario. Ask the team to demonstrate what is supported, identify any integration work and agree who will verify the results.
Discuss your booking engine tracking needsFrequently asked questions
Can I use a thank-you page as the conversion?
Only if it reliably represents a confirmed reservation and supplies the transaction data. A page view alone cannot distinguish a new booking from a reload or a repeat visit.
Does a pay-at-property booking count?
Yes, if the engine has confirmed the reservation under your agreed definition. Measure the booked value separately from payment collection; a later balance payment must not create a second booking purchase.
Which conversion-rate denominator should I use?
For session conversion, divide measured booking-engine sessions containing a purchase by all measured booking-engine sessions in the same period. Label the metric clearly; dividing by website sessions measures a different part of the journey.
Why does a direct booking show as paid search?
“Direct booking” describes the reservation channel. Paid search describes how the guest arrived. A paid advert can generate a direct hotel reservation; GA4’s Direct traffic category has a different meaning.
Sources and further reading
Guidance and UK product pages checked on 10 November 2026. Confirm implementation and package access for your property.
- Google Analytics: cross-domain measurement and unwanted referrals.
- Google: event parameters, ecommerce and refunds, and transaction IDs.
- Google: consent mode. ICO: storage and access exceptions.












