Analytics for your booking pages

What we support

Google Analytics 4, Google Tag Manager, GoHighLevel and the Meta Pixel for Facebook and Instagram ads. All four are optional and independent — use one, several or none. Universal Analytics is retired and isn't supported.

Today, page views fire automatically on your public booking pages. Nothing fires on your staff pages, so your team's own work never pollutes your conversion data.

Find your GA4 Measurement ID

1. Open Google Analytics and click Admin (bottom left).
2. Choose Data streams, then your website stream.
3. Copy the Measurement ID in the top right — it looks like G-XXXXXXXXXX.
4. Paste it into Operations → Settings → Analytics & tracking and save.

Find your GTM Container ID

1. Open Google Tag Manager and select your container.
2. The ID sits beside the container name at the top — it looks like GTM-XXXXXXX.
3. Paste it into Operations → Settings → Analytics & tracking and save.

Because booking pages are rendered in the browser, Tag Manager's no-JavaScript fallback isn't included — visitors without JavaScript can't complete a booking anyway.

GoHighLevel

You can also connect a GoHighLevel Location, so visits to your booking pages show up in the same place you already manage your marketing.

Find your Location ID

1. Log into your GoHighLevel account.
2. Go to Settings → Business Profile.
3. Look for "Location ID" in the account details.
4. Copy the letters-and-numbers string.
5. Paste it into Operations → Settings → Analytics & tracking and save.

In Sub-Account view the same ID appears in the address bar as location/XXXXXXXXX.

What GoHighLevel captures on booking pages

Beyond page views, GoHighLevel's script may automatically capture form submissions from your booking flow, including guest names and email addresses. Those become contacts in your GoHighLevel account — usually what you want for post-booking follow-up. Card details are entered in a secure payment field GoHighLevel cannot see. If you want to control which forms are captured, change your form capture settings in GoHighLevel.

Chat widget

If the chat widget is switched on for that Location in GoHighLevel, it may appear on your booking pages while tracking is active. Change chat visibility in your GoHighLevel settings if you'd rather it didn't.

No cross-domain setup needed

Unlike Google Analytics, GoHighLevel needs no separate cross-domain configuration — visits are tied to your Location whichever domain they happen on. Page views are what fire today, matching what we send to Google.

Meta Pixel (Facebook & Instagram)

Add your Meta Pixel and your booking pages report conversions back to Facebook and Instagram, so your ads can be optimised against real bookings and revenue.

Find your Pixel ID

1. Open Meta Events Manager.
2. Click Data sources in the left menu.
3. Select your pixel — the ID appears under its name, a number like 123456789012345.
4. Paste it into Operations → Settings → Analytics & tracking and save.

The booking steps we report

• Page view — every public booking page.
• View content — someone opens a sailing and sees the cabins.
• Add to cart — a cabin is chosen and the reservation starts.
• Initiate checkout — the guest details step is reached.
• Add payment info — the payment step is reached.
• Purchase — the booking is paid, with the amount charged in US dollars.
• Refund — money returned, so your reported revenue stays honest.

What we never send

No guest names, email addresses, phone numbers or card details reach Meta. Completed bookings carry the booking reference so a page refresh can't count the same sale twice.

Check it's working

In Events Manager, open your pixel and choose Test events, then visit one of your booking pages. Events appear within seconds. No cross-domain setup is needed.

Cross-domain measurement

Your marketing site and your booking pages sit on two different domains. To see one continuous journey instead of two separate visits, add athelm360.com to your Google Analytics data stream:

1. Google Analytics → Admin → Data streams → your website stream.
2. Configure tag settings → Configure your domains.
3. Add athelm360.com and save.

Once that's in place and the same Measurement ID is set on both sides, Google links the two visits automatically — nothing else to configure.

Your booking widget

The embeddable widget runs on your own website, so your existing analytics already sees people viewing and clicking it. We deliberately don't add tracking inside the widget — that would count the same person twice. When they click through, your tracking picks up again on the booking page.

Consent and privacy

Turning tracking on sets cookies and identifiers in your visitors' browsers. Depending on where your visitors are and which laws apply — GDPR in the EU, CCPA in California and others — you may need to obtain consent before any tracking happens.

AtHelm does not currently show a cookie consent banner on booking pages. Ensuring your booking pages comply with applicable privacy law is your responsibility. If you're unsure whether you need a consent banner, speak to your legal advisor before enabling tracking.

Coming later

Richer ecommerce events — cabin views, checkout steps and completed bookings with values — are on the roadmap. For now, page views give you traffic, sources and landing pages.

Need a hand?

Reply to any AtHelm email and we'll help you check that your tracking is firing.