Google Tag Manager

Load your existing GTM container on funnel pages and get funnel events pushed to the dataLayer. Whatever you already run through GTM — GA4, Google Ads conversions, a marketing tag your agency manages — starts working on the funnel without us building a separate integration for each one.

Analytics & tags

Google Tag Manager

Your container on funnel pages, funnel events in the dataLayer

Runs on the page

Why connect Google Tag Manager

The argument, not the feature list.

One integration, every tag you already run

GTM is the escape hatch. Rather than waiting for us to support each vendor, you point your container at the funnel and manage tags where you already manage them.

Funnel events, not just page views

Checkout starts, registrations and purchases are pushed to the dataLayer with their real values, so a GA4 or Google Ads conversion tag fires on the thing that actually happened.

Your agency keeps working the way it works

No code change on our side to add a tag. Whoever manages your container manages the funnel’s measurement too.

How it works

What moves, and in which direction.

  1. 01Your GTM container loads on funnel pages.
  2. 02Funnel events are pushed to the dataLayer as they happen, carrying value, currency and product identity where relevant.
  3. 03Your existing tags and triggers fire against those dataLayer events.

What gets sent

Google Tag Manager runs on the page rather than receiving a server-side event stream.

What you need

Have these on hand and setup takes a couple of minutes in the dashboard.

  • 01Your GTM container ID (GTM-XXXXXXX)

Getting these from Google Tag Manager. Our own setup steps live in the docs.

Worth knowing

Things that will otherwise surprise you later.

  • GTM runs in the browser, so anything it feeds inherits browser-side reliability. For conversions you buy media against, the server-side Meta and TikTok integrations are the sturdier route.

Connect Google Tag Manager in a couple of minutes

Set it up in the dashboard — no engineering ticket, no deploy.