Google Analytics 4 for Tour Operators: The Six Numbers That Decide Next Season

Most operator analytics accounts were set up once, by whoever built the website, and have not been opened since. The version running now is called GA4, it works completely differently from past versions, and Goals no longer exist. Google Analytics 4 for tour operators deserves about an hour at the end of a season, because six numbers in it explain how guests decide, where the checkout loses them, and which channel pays for itself.

The six numbers, and the three settings they depend on

1. Booking window: How many days pass between a guest’s first visit and the booking.
2. Direct share: How much of your revenue happens on your own website at all.
3. The phone gap: How differently a phone visitor converts from a desktop visitor.
4. Checkout drop-off: Which step of the booking flow loses the most people.
5. Cost per booking by channel: What each source of traffic costs against what it returns.
6. Revenue by language: Which market is buying, and which translation earns the next hour of work.

Three settings decide whether any of those numbers can be trusted. All three sit in the Admin area, and each takes a couple of minutes:

• Data retention: a standard property keeps event-level data for either 2 months or 14 months, and the setting only affects explorations and funnel reports rather than the standard aggregated ones¹. On 2 months, comparing this September with last September is not possible, so 14 months is the setting a seasonal business wants.
• Cross-domain measurement: where the ticket shop or checkout sits on a different root domain from the marketing site, a guest who crosses between them counts as two users in two sessions unless the domains are listed together². The booking then appears to come from your own website as a referral, and the channel that earned it gets no credit.
• Consent mode: for visitors in the European Economic Area, consent mode is what passes the answer from your cookie banner through to the tag. When a visitor declines, the tag sends a cookieless ping instead of setting cookies, and Google fills the gap with behavioural and conversion modelling³.

Number 1: how long guests take to decide

The report is Advertising › Key events › Key event attribution paths, and the metric is Days to key events⁴. It counts from the first visit rather than from the moment the guest opened the booking calendar, so it describes the whole research window.

Regiondo’s own Statistics Overview already reports an average booking lead time from your booking data. The two numbers answer different questions: lead time is the gap between booking and departure, while Days to key events is the gap between interest and purchase.

That second gap is what a booking cut-off has to respect. In Phocuswright and Arival’s 2026 European sample, same-day bookings run at 17% of travellers aged 18 to 34, 21% of 35 to 54 and 30% of the over-55s⁵. Where a large share of your guests decide on the day, a 48-hour cut-off closes the shop while they are still buying.

Number 2: what Google Analytics 4 for tour operators cannot see

Google Analytics records what happens on your own website. A booking made on an OTA, or taken at your desk through POS, never touches it, so the revenue figure in your reports is your direct online business rather than your season.

Regiondo’s Statistics Overview draws the same line from the other side: turnover there is the gross price with no taxes or provisions deducted, and the conversion rate counts ticket shop and booking widget orders against visitors, excluding POS⁶.

Holding the two side by side gives you the one figure neither report shows on its own, which is the share of your season that your website is responsible for. That share is also smaller than most operators assume across the industry: 33% of experiences worldwide were booked online in 2025, against 64% of the travel market as a whole⁷.

Number 3: the gap between phone and desktop

In Reports › Tech, the Tech details view splits every metric by device category. The number worth reading is the Session key event rate for phones against the rate for desktops.

A gap of a point or two is normal. A gap of several points usually says something about the booking flow on a small screen rather than about the people using it, especially when the guest is standing in the destination with the experience in front of them.

Number 4: where the checkout loses people

Regiondo’s booking widgets already send the standard e-commerce events to whatever tag sits on the parent page, including view_item, add_to_cart, begin_checkout and purchase⁸. A Funnel exploration built on those four events shows the drop between each step without any development work.

The step where the number falls is the one worth acting on. A fall between view_item and add_to_cart points at the price list or the availability on offer, while a fall between begin_checkout and purchase points at the checkout itself, where payment methods, required fields and currency all live.

This is also the report that quietly disappears on the 2-month retention setting, since explorations are exactly what that setting governs.

Number 5: what a booking costs you by channel

The Traffic acquisition report groups sessions by channel and shows revenue against each one. Cost is the half that Analytics cannot supply on its own: Google Ads spend appears once you link the two accounts, and every other channel has to come in by hand.

Set against that, each OTA charges a Provision Fee per booking, which makes the honest comparison a per-booking one rather than a per-channel-type one. A commissioned booking on a seat that would otherwise travel empty is worth more than the principle of selling direct. Where availability for those channels comes from the same calendar as your own shop, as it does through Regiondo’s channel manager, the comparison stays clean because the same seat cannot sell twice.

Number 6: which language your revenue speaks

Language and country are dimensions in the same reports as everything else, and applied to revenue they answer a question European operators face every year: which market to translate for next.

Regiondo’s shop and interface run in a dozen languages, but the operator translates offer descriptions, so the work is real and worth pointing at the market that is already spending. A country that converts poorly against strong traffic is usually a translation gap rather than a demand problem.

The one-hour review, once a season

• Set Data retention to 14 months.
• List every domain a guest crosses between, and confirm Consent mode is passing the banner’s answer through.
• Read Days to key events, and compare it against your booking cut-offs.
• Compare Analytics revenue against Statistics Overview turnover to get your direct share.
• Read the Session key event rate for phones against desktops.
• Build the funnel on view_item, add_to_cart, begin_checkout and purchase, and note the biggest drop.
• Put channel revenue next to what each channel costs, including Provision Fees.
• Note which language and country earned the revenue, and pick the next translation.

Sources

1. Google, Data retention, Analytics Help.
2. Google, Set up cross-domain measurement, Analytics Help.
3. Google, Consent mode, Analytics Help.
4. Google, Key events attribution paths report, Analytics Help.
5. Phocuswright and Arival, Travel Experiences 2026: Market Sizing, Operator and Consumer Behavior Highlights, July 2026. European sample of 1,750 travellers in the UK, France, Germany and Spain, fielded Q4 2025.
6. Regiondo, Which kinds of statistics are available?, Regiondo Help Center.
7. Arival, 4 Findings for the Experiences Market in 2026, citing Phocuswright and Arival, Travel Experiences 2026. Global figure.
8. Regiondo, How to set up tracking and analytics: Google Tag Manager, Google Analytics, Regiondo Help Center.

FAQ: Why did my Goals and my old Google Analytics reports disappear?

ANS: Universal Analytics stopped processing data in July 2023 and was replaced by Google Analytics 4, which is built on events rather than sessions and pageviews. Goals no longer exist as an object: the equivalent is an event you mark as a key event, which is Google’s term for the actions that matter most to a business. Historical Universal Analytics data does not carry across, so the comparison year most operators want has to start from whenever GA4 began collecting.

FAQ: Is Google Analytics 4 free for a small tour or activity business?

ANS: Yes. The standard version is free at the volumes a tour, activity or attraction operator generates, and the paid tier is aimed at enterprises with far larger data needs. The cost is the hour of setup rather than a licence.

FAQ: Does the Regiondo booking widget need its own tracking code?

ANS: No. The React widgets send their events to the tracking already present on the page they sit in, so the tag or Google Tag Manager container belongs on your website rather than inside the widget. The Regiondo Help Center lists the events that arrive this way, which is what the funnel in Number 4 uses.

FAQ: Do I need Google Tag Manager, or is the Google tag enough?

ANS: The Google tag on its own is enough to collect visits and the widget’s e-commerce events. Tag Manager becomes worth the extra layer once several tags are involved, for example Analytics alongside Meta or Google Ads, or when a consent banner has to control all of them together.

FAQ: How much traffic does a small operator need before these numbers mean anything?

ANS: Enough bookings for a percentage to move for a reason rather than by chance, which for most small operators means reading a quarter rather than a week. Under a few hundred bookings a season, the shape of the funnel and the direction of the gaps are reliable, while the exact decimal places are not.