Insights

Server-side tracking for hotels and what it really fixes

Server-side tracking gets more of your booking data to Google and Meta. It does not repair a broken set-up, and it does not replace consent.

Data & Insights
Harry FielderCEO & Co-Founder
20 Oct 2026 · 7 min read

Server-side tracking usually arrives on the agenda as a fix for numbers nobody trusts. It will fix some of them. The rest were broken before the data ever left the browser.

Server-side tracking (Google calls it server-side tagging) puts a tagging server on your own domain between the guest's browser and the platforms you report to. The browser sends one stream of data to your server, and the server passes it on to GA4, Google Ads and Meta. Because that traffic looks first-party, browsers keep its cookies for longer and block less of it. More of the bookings your marketing drove get credited to it.

It matters more now than when we first wrote about it in 2023. Safari's cookie limits and ad blockers have made browser-only tracking leakier, and Meta now recommends sending conversions from a server as well as from its pixel. But a tagging server is a better pipe, not a better set-up.

Fix the set-up first, then fit the pipe.

What actually changes

How most hotel sites send data now

On a typical hotel website, Google Tag Manager loads from Google's servers and runs tags in the guest's browser. Each tag sends its own data straight to GA4, Google Ads, Meta, metasearch or whatever else has been added over the years. Every request goes to a third-party domain, and every cookie those scripts set is at the mercy of the browser.

That works well enough in desktop Chrome with no blockers. It works much less well in Safari on an iPhone. Chrome decided in April 2025 to keep third-party cookies, so the pressure comes mostly from Safari and blockers, not from Chrome.

What a tagging server adds

Server-side tagging keeps your normal tag manager container on the site and adds a second, server container, hosted on a subdomain such as tracking.yourhotel.com. The web container sends events to your server instead of to each vendor. The server container then decides what goes where.

It is additive. Nothing you already track has to be rebuilt, and the website keeps working if the tagging server goes down. It is part of how we approach measurement in the Growth Marketing practice, usually once the existing container is in order.

What it fixes

Four things improve, and they are the reasons to do it.

  • Cookies that last. Safari limits cookies set by scripts in the page to seven days, and to a day in some cases. Cookies set by your own server on your own domain are not capped the same way, so a guest who researches in March and books in April can still be recognised.
  • Requests that arrive. Browsers and blockers are far more likely to stop a request to a known ad domain than one to your own subdomain.
  • Conversions sent server to server. The Meta Conversions API lets the purchase reach Meta from a server rather than relying only on the pixel. Send it from both with the same event ID and Meta counts it once.
  • Control over what leaves. You choose which fields each vendor receives, so IP addresses, email addresses and booking details only go where you have decided they should.

There is a catch that undoes a lot of set-ups. Since Safari 16.4 in 2023, cookies set by a tracking subdomain whose server sits on a very different IP address from your website are capped at seven days too. So the subdomain has to point to infrastructure close to the website's own, or the tracking has to be served from a path on the main domain. Google's tag gateway, generally available since May 2025, does the second for Google tags through a CDN such as Cloudflare, and is a lighter first step for hotels already on one.

The gain is in the time horizon. Hotel booking windows are long, and Meta in particular works at the top of the funnel. A seven-day memory credits very little of that to anyone. Longer-lived first-party cookies also mean larger, more accurate audiences for paid remarketing.

What it does not fix

Hotel teams often expect server-side to replace the tracking they have. It does not. It carries whatever the web container gives it.

Server-side is simply the mechanism by which you're sending the tags.
It will help, and it will get better. But the broken things still need fixing.
Harry Fielder, CEO, Umi

The booking engine is still someone else's

Most hotel bookings complete on a booking engine you do not control, on its own domain or subdomain. If the purchase event there has no value, if the visit arrives as a new session, or if the conversion linker does not fire, a tagging server forwards those gaps. Our guide to what to measure as GA4 key events covers where bookings go missing at that hand-off and how to close it.

Tag Manager and the platforms behind it were built with retail in mind, where the shop and the checkout are one site. A hotel guest can hop between three or four systems before paying. Server-side narrows the loss across that journey. It cannot make it one site.

Consent still applies

A tagging server is not a way round the cookie banner. If a guest declines, their data should not reach the ad platforms in a form those platforms can use, whichever route it travels.

Google's tags in the server container read the consent state the website passes to them and adjust what they send. Google's guide to consent mode with server-side tagging covers Google's tags only. Meta, metasearch and affiliate tags in the server container need consent rules built for them, or they will fire for everyone. The wider rules are in our guide to the cookieless web for hotels.

Click IDs that never arrive

Safari strips ad click identifiers such as gclid and fbclid from links opened in Private Browsing, Mail and Messages. A guest who taps your Google ad in a private tab arrives without the ID that ties the visit to the click. No server can recover what the browser never handed over.

Server-side tagging makes good data last longer. It does not turn missing data into good data.

What it costs

Hosting

The server container itself is free in Google Tag Manager. The server it runs on is not. Google's infrastructure planning guide puts Cloud Run hosting at about USD 50 per instance per month and advises running enough minimum instances to absorb normal swings in traffic. Two or three instances is typical in production, so roughly USD 100 to 150 a month.

Managed server-side hosting services are cheaper for most single hotels, from under USD 20 a month at low volumes to the low hundreds for a busy group. The tag gateway route costs little or nothing beyond the CDN you already pay for.

Set-up and upkeep

For a hotel with a sensible container, setting up a server container on a first-party subdomain takes weeks, not months, including the Meta Conversions API and consent rules. It is not a rebuild of anything.

The larger cost is ownership. A tagging server is another system that someone has to monitor, update and check whenever the booking engine, the consent platform or a vendor's API changes. If nobody owns it, it drifts like everything else.

Where to start

  1. Fix the container. Remove duplicate and paused tags, check consent settings and make sure the booking engine sends a purchase with value, currency and transaction ID. Our hotelier's guide to Google Tag Manager covers the clean-up.
  2. Choose the route. Use the tag gateway if you are on a supported CDN and mostly need Google's tags. Use a full server container if Meta matters to your budget or you want control over what each vendor receives.
  3. Host it properly. Use infrastructure close to the website's, or a path on the main domain, so Safari treats its cookies as first-party.
  4. Add the server-to-server conversions. Send the booking to Meta through the Conversions API alongside the pixel, with a shared event ID, and set consent rules for every non-Google tag.
  5. Measure the difference. Record GA4 and Meta bookings against the booking engine's own count for a month before the switch and a month after.

Then go back to the booking engine. The best tagging server is still reporting on a checkout you rent. The hotels that get closest to complete measurement bring more of the booking journey onto their own domain, where every step is first-party by default.

Server-side tagging is the right next step for most hotels that spend on paid media. It is not the last one.

Questions hotels ask

It adds a tagging server on your own domain between the guest's browser and platforms such as GA4, Google Ads and Meta. The browser sends data to your server, which forwards it on. Because the traffic is first-party, browsers keep its cookies for longer and block less of it.

Yes. Server-side tracking changes how data travels, not whether the guest has agreed to it. Google's tags in the server container follow the consent state passed from the website, but other vendors' tags need consent rules set up for them.

The Google Tag Manager server container is free, but it needs hosting. Google estimates about USD 50 per Cloud Run instance per month, and production set-ups usually run two or three. Managed hosting services are often cheaper for a single hotel, and set-up is typically a few weeks of work.

It will usually narrow the gap, but not close it. If the booking engine sends purchases without values, or visits break at the hand-off between the website and the booking engine, a tagging server forwards those problems. Fix the set-up first, then add the server.

Free 30 Minute Consultation

Get more of your bookings counted

We audit hotel tag manager and booking engine set-ups, fix what is broken, then move tracking onto your own domain so the data lasts.

Keep reading

More in Data & Insights