GA4 for hotels: a plain-English guide to knowing which channels drive bookings

Ask many independent hoteliers where their website bookings come from and the honest answer is a guess. Instagram feels busy, so maybe Instagram. The marketing agency says the ads are working, so maybe the ads. Meanwhile the actual answer sits in a free tool many hotels already have installed and rarely open: Google Analytics 4.

This guide is for hoteliers, not analysts. It skips the jargon where possible, explains it where necessary, and focuses on the one question that matters: which channels drive bookings, and which just drive traffic.

Why bother, in one paragraph

Marketing money follows evidence or it follows feelings. If you know that search brings most of your booking revenue, that email to past guests converts at several times the rate of anything else, and that a particular campaign produced traffic but no stays, your next budget decision is easy. Without that, every channel looks equally deserving and the loudest invoice wins.

The one thing GA4 must be set up to do

GA4 out of the box counts visitors, page views, and sessions. None of that answers the booking question. The setup that matters is conversion tracking: telling GA4 what a completed booking looks like, so it can connect bookings back to the traffic that produced them.

In GA4's language, a booking is an event, and you mark that event as a key event (the term GA4 now uses for what used to be called conversions). Ideally the event carries the booking value, so reports show revenue rather than just counts.

How hard this is depends entirely on your booking engine:

• If the booking engine runs on your own domain, your web team or platform can fire a purchase event on the confirmation page. This is the clean case.
• If the booking engine lives on a different domain, which is common in hotels, you need cross-domain tracking configured so GA4 understands that the person who left your site and the person who confirmed the booking are the same visitor. Skip this and your booking engine shows up in reports as a traffic source itself, with "referral" bookings that are really your own guests mid-checkout.
• If bookings complete somewhere you cannot tag at all, track the strongest signal you can reach, such as clicks into the booking engine with dates selected, and treat it as your proxy for booking intent.

This setup step is where hotel analytics most often fails, quietly. If your GA4 property has no key event for bookings, every report downstream is traffic trivia.

Reading the channel report without fooling yourself

The report you want is Traffic acquisition, in the Acquisition section, filtered to your booking key event. GA4 groups traffic into default channels. For a hotel, the ones that matter:

• Organic search. People who found you via unpaid search results. For many established hotels this is the largest channel, and a large share of it is people searching your hotel's name.
• Direct. People who typed your address, used a bookmark, or came from a source GA4 could not identify. Some of this is genuine loyalty. Some of it is measurement failure, often links from messaging apps. Treat direct as a mix, not a channel you can act on.
• Paid search. Your Google Ads traffic. Link your Google Ads account to GA4 so the cost side and the booking side meet in one place.
• Organic social and paid social. Instagram, Facebook and friends. Social commonly produces inspiration-stage visitors: strong traffic, long time on site, few immediate bookings. That does not make it worthless, but it means judging social on last-click bookings alone will understate it, and judging it on traffic alone will overstate it.
• Email. Usually small in volume and strong in conversion rate, because the audience already knows you. If email shows as nearly nothing, the links in your emails are probably missing tracking tags.
• Referral. Other websites linking to you. Scan this for two things: valuable sources worth cultivating, and your own booking engine appearing here, which is the cross-domain problem above.

One honest caveat: attribution is a model, not a fact. A guest might see your hotel on Instagram in January, read a travel guide in February, and search your name in March. GA4's default reports will give organic search the credit. Channel reports tell you where bookings finished, which is still vastly better than guessing, but keep the whole path in mind before declaring any upper-funnel channel useless.

A monthly routine that takes twenty minutes

Dashboards nobody opens change nothing. A short, repeated routine does. Once a month:

• Bookings and revenue by channel. Traffic acquisition report, booking key event, compare with last month and the same month last year. Hotels are seasonal; year-on-year is the honest comparison.
• Conversion rate by channel. Which sources send visitors who actually book? A small channel with a strong rate is often where the growth is.
• Landing pages. Which pages do booking guests enter on? If a page gets heavy traffic and produces no bookings, it has a content or usability problem worth a look.
• Devices and countries. If most visitors are on mobile and mobile converts far worse than desktop, the website has a mobile problem, and that is a finding worth more than most campaigns.
• One decision. End every review by writing down a single action: shift budget, fix a page, send an email. Analytics that produces no decisions is a hobby.

Common hotel-specific traps

• The booking engine as a referral source. Covered above, and worth repeating because it is one of the most common distortions in hotel GA4 properties.
• Untagged campaign links. Links in emails, bios, and QR codes need UTM parameters, or their results dissolve into direct traffic.
• Internal traffic. You and your staff visit the website constantly. Filter out your own IP addresses, or small hotels end up studying their own behavior.
• Counting sessions instead of stays. Traffic is the easiest number to grow and the least connected to revenue. Keep the booking key event at the center of every report you look at.

Set up properly once, GA4 turns the channel question from a debate into a lookup. That setup, including booking conversion tracking and cross-domain configuration, is exactly the kind of work that gets postponed indefinitely at busy properties, which is why HotelierKit includes GA4, Tag Manager and booking conversion tracking in the platform rather than leaving it as homework. If you would like the measurement layer handled with the website itself, see how tracking works on HotelierKit.