Conversion Tracking & Analytics (Meta Pixel, GA4, GTM)

Haven lets you add your own marketing and analytics tags to your public booking pages so you can measure traffic and report bookings as conversions to Meta (Facebook) and Google. You add your IDs once and Haven loads them across every site that serves your listing — your custom domain, your *.bookwithhaven subdomain, and the canonical Haven URL — and fires the full booking funnel for you automatically.

This guide covers the Meta Pixel, Google Analytics 4 (GA4), Google Tag Manager (GTM), and the optional server-side conversions (Meta Conversions API and the GA4 Measurement Protocol).

When to use tracking

You're running Meta (Facebook/Instagram) ads and want to optimize for bookings and build retargeting audiences.
You want Google Analytics to understand how visitors find and move through your booking site.
You manage multiple marketing tags (Google Ads, remarketing, extra pixels) and want one place — Google Tag Manager — to control them.
You want booking conversions to report accurately even with ad blockers via server-side conversions.

If you're not running ads or measuring traffic, you can skip this entirely — it's optional.

Where to set it up

Everything lives in one place:

Host Dashboard → Advertising → Tags & Pixels

Your sites are grouped into Single Property Sites and Multi-Unit Sites. Click a site to expand it, paste your IDs into the matching fields, and they autosave — watch the "Saving… / Saved" pill in the top-right corner. A "Tracking on" badge appears on any site that has at least one ID set.

Set it on the right site. Each site row maps to one specific listing or multi-unit site. If you have more than one listing with a similar name, make sure the row you edit is the one whose live URL matches the site you're testing — otherwise the tags load on a different page than the one you're checking.

What Haven tracks automatically

Once an ID is saved, Haven fires the standard booking funnel for you — you don't have to build any of these events:

Funnel step	Google Analytics 4 event	Meta Pixel event
Property/site page view	`view_item`	`ViewContent`
Booking started (hold created)	`begin_checkout`	`InitiateCheckout`
Inquiry / request to book	`generate_lead`	`Lead`
Booking confirmed	`purchase`	`Purchase`

The same events are also pushed to the GTM dataLayer, so they're available to any tags you build in Google Tag Manager.

How to set up the Meta Pixel

You only need the ID, not the code. Meta (and Google) will offer to walk you through pasting a code snippet into your website's <head>. Skip that — Haven installs and fires the tag for you. All you ever copy into Haven is the ID (and, optionally, the server-side token/secret).

Step 1: Find your Pixel (dataset) ID

In Meta Events Manager, open (or create) your dataset. The Pixel ID is the 15–16 digit number shown next to the dataset name.

Step 2: Paste it into Haven

In Advertising → Tags & Pixels, expand your site and paste the ID into the Meta Pixel field. It autosaves, and a "Tracking on" badge appears.

Step 3: (Recommended) Add the Conversions API token

Once a valid Pixel ID is saved, a Server-side conversions section appears in Haven with a Meta Conversions API token field. In Events Manager, go to your dataset's Conversions API setup and Generate access token, then copy it.

Meta Conversions API "Generate an access token" screen

Paste the token into the Meta Conversions API token field in Haven. It's encrypted at rest and never shown again. This sends a server-side Purchase from Haven on every confirmed booking — accurate even when a guest blocks the browser pixel — deduplicated against the browser event.

You don't need Meta's manual "Select events / parameters" CAPI wizard. Haven builds and sends the events (ViewContent, InitiateCheckout, Lead, Purchase) for you using the access token — just generate the token and paste it in.

See Testing your tags below, then Verify your domain in Meta.

How to set up Google Analytics 4

You can run GA4 directly (simplest) or through GTM — but not both with the same Measurement ID, or every event double-counts.

Path A — GA4 directly (recommended for a single site)

In Google Analytics, open the Admin area, click Create, and choose Property (or use an existing property). On the last step, select Web and enter your site's URL to create a Web data stream.
Open your Web stream details and copy the Measurement ID — it looks like G-XXXXXXXXXX. (Ignore the "install the Google tag" code snippet — you only need the ID.)
Paste the Measurement ID into the Google Analytics 4 field in Haven. It autosaves.
(Recommended) Server-side backup: in the same web stream, open Measurement Protocol API secrets → Create, name it, and copy the secret value. Paste it into the GA4 API secret field that appears in Haven. This sends a server-side purchase on confirmed bookings, deduplicated with the browser event.

Give it time in standard reports. Realtime and DebugView show events immediately, but GA4's standard reports can take up to 24–48 hours to populate — a new property showing no data there at first is normal.

Path B — through GTM

If you'd rather manage GA4 inside Google Tag Manager, leave the GA4 field empty in Haven and configure GA4 inside your container (see below).

How to set up Google Tag Manager

Use GTM when you want a single place to manage many tags (Google Ads, remarketing, extra pixels) without changing settings in Haven.

In Google Tag Manager, create a Web container and copy the container ID — GTM-XXXXXXX.
Paste it into the Google Tag Manager field in Haven. It autosaves.
In the GTM console, add the tags you want — for GA4, add a Google Tag with your G- Measurement ID triggered on All Pages.
To track bookings, add GA4 event tags triggered on Haven's dataLayer events (view_item, begin_checkout, purchase), reading the ecommerce object Haven pushes.
Publish the container — changes don't go live until you submit/publish.

Avoid double-counting GA4. If you configure GA4 inside GTM, do not also paste the G- Measurement ID into Haven's GA4 field. Pick one path.

Server-side conversions

Server-side conversions are the durable, ad-blocker-proof, cross-domain half of conversion tracking. On every confirmed booking, Haven sends a Purchase / purchase directly from its servers:

Meta Conversions API — fired when a Meta Pixel ID and a Conversions API token are both set.
GA4 Measurement Protocol — fired when a GA4 Measurement ID and a GA4 API secret are both set.

Both use the booking's true amount from Stripe (never a reconstructed figure) and share the same event ID as the browser event, so Meta and Google deduplicate the two into one conversion. Tokens and secrets are encrypted and never displayed again after saving; use Remove token / Remove secret to clear them.

Testing your tags

Two things trip people up, so check these first:

Use a normal browser. Haven suppresses tracking for traffic it detects as automated (bots/crawlers). Some embedded or in-app browsers can be caught by this, so always test in a standard desktop or mobile browser.
Interact with the page. Tags load after the first interaction (scroll, click, or tap) or a few seconds of idle time — so they stay off the critical loading path. If you check the instant the page paints, you'll see nothing yet; scroll once and wait a moment.

Meta Pixel

Install the Meta Pixel Helper Chrome extension, open your live site, interact, then click the extension — you should see your Pixel ID Active with a PageView.
For full validation, open Events Manager → Test Events, browse your site, and complete a test booking. You should see InitiateCheckout and then Purchase — the Purchase arriving from both Browser and Server, marked Deduplicated. That confirms the Conversions API token works end-to-end.

Google Analytics 4

Realtime: open your site in a normal browser, interact, then check GA4 → Reports → Realtime — you should appear as an active user.
DebugView (best): install the Google Analytics Debugger extension, toggle it on, browse your site, then watch GA4 → Admin → DebugView. You'll see page_view, view_item, begin_checkout, and (on a test booking) purchase stream in live.
Network check: in your browser's DevTools Network tab, filter for collect — you should see requests to google-analytics.com/g/collect with en=page_view, en=view_item, etc.

Meta domain verification & Aggregated Event Measurement

To get accurate attribution (especially on iOS) once your Pixel is live:

Verify your domain in Meta Business Settings → Brand Safety → Domains (DNS TXT record or meta-tag method).
Configure Aggregated Event Measurement in Events Manager and rank your 8 events with Purchase as #1.

A brand-new dataset may show a "low data quality" notice until real traffic and the browser + server Purchase pair start flowing — it clears on its own.

Troubleshooting

"No pixel found" / no events in a normal browser — confirm the ID is saved on the correct site (the one whose live URL you're testing), then hard-refresh in an incognito window and interact with the page.
Tags show in the dashboard but not on the live site — make sure the site you edited is the one actually serving your live domain. If you have duplicate listings, the domain may be attached to a different one.
Events double-counting in GA4 — you've configured GA4 both directly in Haven and inside GTM with the same Measurement ID. Remove one.
No server-side Purchase — server conversions only fire on a confirmed booking, and require the token/secret to be saved. Meta also needs at least one identifier (the guest email or Meta cookies) to attribute the event.
Admin preview shows nothing — Haven suppresses tracking when analytics are disabled for previewing; test as a normal visitor.