Tracking & Analytics
The Bookings Are Real. The Numbers Should Be Too.
On a hotel website, conversions go missing in places that have nothing to do with your marketing: a cookie refused, an anonymizer, a browser that blocks trackers by default, an antivirus that decides your pixel is one. Every one of those is a booking that happened and a platform that never saw it — so the campaign that earned it gets credited to nothing. This is the stack that closes those gaps, one at a time.
Not a Conversion. A Booking, in Full.
Most integrations report that something was bought and how much it cost. Simple Booking's purchase event carries the booking itself — which is the difference between knowing a campaign returned four times its spend and knowing it sold suites on half board in February.
Everything on the reservation, visible
Dates, room, rate, what's included, what the cancellation terms actually say. Not in an attachment.
Guest details they can correct themselves
Names, contacts, whatever was typed wrong at eleven at night — updated without asking anyone.
A new payment card when the old one won't do
Cards expire, get replaced, get lost. The guest swaps it on the booking instead of reading it out over the phone.
Requests and notes, added to the booking
A late arrival, a cot, an anniversary — attached where the front office will actually see it, not buried in a thread.
Services and add-ons, before they arrive
The window between booking and arrival is when a guest is most willing to spend on their own stay, and it's open the whole time.
A room upgrade, when one is available
If your rules allow it and the inventory is there, the upgrade is waiting on their booking with the price difference already worked out.
Carried in every purchase
Order total
Currency
Booking number
Rooms
Rate plan
Services
The platforms named here are the ones this page is about. Marketing, user-engagement and tracking tools are one category of a much longer list, alongside chatbots and AI assistants.
No Tag Manager in the Checkout. On Purpose.
Google Tag Manager isn't supported inside Simple Booking, and it isn't an oversight — it's the one place we won't put a container that can inject any script anybody adds to it, later, without review. Your booking flow is also your payment flow, on PCI DSS certified infrastructure. It is not the place to run code nobody has read.
Which means the question isn't whether you get a tag manager. It's what you get instead.
Your IDs, not ours
GA4 and Meta, in your name.
You or your agency hand over the GA4 and Meta IDs. That's the whole handover — nobody needs access to the booking engine's code, and nothing is configured in a place you can't see.
Your accounts, your data
It lands where it belongs.
Conversions, events and revenue go into the hotel's own analytics and ad accounts. Not into ours, with a report sent to you afterwards. If you change agency, the data history doesn't move.
Every script, read first
Configured and validated by us.
The Simple Booking team sets up the tracking and validates it before it goes live, which is also why it works: a tag that fires at the wrong moment in a booking flow is a measurement problem long before it's a security one.
On the hotel's own website there's usually one script to include — the same one that renders your search box — and it carries the tracking parameters with it. It's handed over ready to paste.

Server-Side
The Cookie Is Refused. The Booking Is Not.
Client-side tracking loses more conversions every year, and the trend only goes one way: cookies declined, anonymizers, Safari's tracking prevention, antivirus software that blocks trackers as a category. The booking still happens — the browser just doesn't tell anyone. So we send it a second way, server to server, from our infrastructure straight to the platform.
No booking goes uncounted
Every reservation is delivered as a purchase event, whether or not the browser cooperated.
First-session attribution stays above 90%
The model matters, so we name it: first session. It's the number an agency can act on, and it's the one we can stand behind.
The count survives. The person doesn't
When a guest denies consent, the event still fires — cookieless, with no identifiers attached. That's precisely what Consent Mode v2 prescribes for the denied state, and it's why this isn't a way around consent: you keep the number, you don't keep the visitor.
Consent you can configure, in the flow
The consent banner is built into the booking engine and fully configurable, so what each guest agreed to is what actually happens.
It's the purchase event, to two platforms
Server-side delivery covers the reservation itself, to Meta and to Google Analytics via the Measurement Protocol. We'd rather tell you the perimeter than let you find it.
Tagged Traffic Stays Tagged.
Attribution doesn't usually break at the click or at the booking. It breaks somewhere in between, quietly, and the first you hear of it is a report where half your paid traffic has turned into direct. What closes that gap isn't a tracking script you have to add: it's the same script that puts the search box on your website, doing a second job on the way past.
One script, two jobs
It renders your search box. It carries the parameters.
Dates, guests and rooms, responsive, on your own pages — and the same include handles the cross-domain and tracking parameters. There's no second tag to add, and nothing to keep in sync with it.
The click arrives tagged
By the circuits, or by you.
Traffic tagged by the circuits comes in ready to attribute. So does traffic carrying your own custom tags or standard UTM parameters.
The booking is attributed
To the source that earned it.
Cross-domain handoff and UTM parameters carried through the flow, automatically and transparently. The same campaign, the same medium — on the conversion, not on direct.
Not Direct. Not Nothing. Metasearch.
A booking that starts on a metasearch comparison usually arrives with no attribution at all. It lands in direct, where it quietly inflates a channel that didn't earn it, or it doesn't show up anywhere. Conversions from Google Hotel Ads, Tripadvisor and trivago are tracked and injected into Google Analytics alongside everything else — so the spend that produced them is measurable against the spend that didn't.



The same conversions are also in the product's own reporting, next to the rest of your booking data.
Run It Yourself. Or Hand It Over.
Everything on this page is yours to use, whoever is holding the keyboard. Some hotels run their own campaigns, most work with an agency they already trust, and some would rather one team owned the whole thing. All three are real answers, and the tracking stack is identical in each.
You, or the agency you already have
Every tool, available.
Your GA4 and Meta IDs, your accounts, your data, your campaigns. Nothing on this page is reserved for hotels who buy the service — the stack is the product, and it's there either way.
Or our agency team
Metasearch, Google, Meta, Microsoft.
QNT runs campaigns for hotels as an agency, specialized in one thing: maximizing direct-channel revenue — metasearch, Google Ads, Meta and Microsoft. And it works on an advantage no third-party agency can claim: it optimizes on the server-side data it built, with the cart inside the event, instead of on whatever the browser managed to report.
FAQs
No, and you can't use it inside the booking engine — that's a deliberate choice, not a gap. A tag container can inject any script anyone adds to it, and the booking flow is also the payment flow. Instead, you hand over your GA4 and Meta IDs, and the Simple Booking team configures and validates the tracking. On your own website you're free to run whatever you like; the checkout is the part we keep closed.
That's the only way it works. The agency supplies the GA4 or Meta ID and the data goes into the hotel's accounts — not ours. Nobody needs access to the booking engine's code, and if you change agency later, the measurement history stays where it is.
Nothing on the booking engine. On the hotel's own website a code update is usually needed, so the tracking stack and the correct parameters are in place — and the script is handed over ready to paste, not described in a document.
The count survives; the person doesn't. The
purchaseevent still reaches Meta and Google Analytics, cookieless and with no identifiers attached — which is exactly what Consent Mode v2 defines for a denied state. You keep the number of bookings. You don't keep the visitor. The consent banner itself is built in and fully configurable.It means first-session attribution, and we name the model because it's the honest way to state the number: an agency reading first session knows precisely what's promised. Server-side delivery of the
purchaseevent is what keeps it there, when the browser side alone would not.Yes. Conversions from Google Hotel Ads, Tripadvisor and trivago are tracked and injected into Google Analytics, as well as being available in the product's own reporting. Without that, a metasearch booking normally arrives with no attribution at all.
Yes. A single hotel's booking engine can carry more than one GA4 tag, and the multi-property front end — the one where a guest chooses between the properties of a group, a chain or a destination — takes a separate tag of its own.
Book Your Demo Now.
Simple Booking Is the CRS You've Been Looking For.
Book a DemoThe Data Comes From Somewhere.
Measurement is only worth what it measures. These are the pages on either side of it.
Metasearch
Make your website visible and competitive on top metasearch engines.
Booking Engine
The strategic software that sells your rooms directly, fast and efficiently.