Conversion Tracking Setup Wizard

Most measurement problems are not analysis problems — they are setup problems that nobody sequenced. Tell the wizard what you sell and what you already have in place; it returns a prioritized, dependency-ordered plan to get conversions tracked cleanly, durably, and in line with consent.

Sound conversion tracking is built in order: define the money events first, then a clean data layer, then GA4 and Google Tag Manager, then platform conversion tags, then durability (enhanced conversions and, ideally, server-side), with Consent Mode v2 respected throughout and end-to-end QA last. Skip ahead and later steps inherit earlier mistakes. The wizard generates that sequence for your situation.

The calculator

Business type iSets which money events the plan defines first.

Google Tag Manager already installed? iGTM is the single place all tags and triggers live.

Plan server-side tracking? iServer-side improves match quality and resilience.

Consent Mode v2 in place? iRequired for compliant measurement in many regions.

✓ Setup plan generated

Setup steps generated

6phases

browsercollection mode

Export

Walkthrough

How to use this calculator

Pick your business typeEcommerce, lead generation, and SaaS track different money events, so the wizard defines the right ones first. Getting the event list correct up front is what every later step depends on.
Tell the wizard what you already haveIndicate whether Google Tag Manager is installed. If it is not, the plan adds it as step two — GTM is the single, auditable place every tag and trigger should live.
Decide on server-side and consentChoose whether you are planning server-side collection and whether Consent Mode v2 is already wired. These change the plan: server-side adds container and deduplication steps; consent is enforced throughout either way.
Work the steps in orderThe plan is ordered by dependency — foundation, events, platform conversions, consent, server-side, then QA. Do not skip ahead; later steps assume the earlier ones are clean.
Validate before you trust the numbersThe final step is end-to-end QA with GTM Preview, GA4 DebugView, and the platform tag assistants. Reconcile counts to the back end weekly for the first month before you optimize against them.

From the desk

RGM Expert Says

Real Growth Matters — Measurement engineeringHow we use this tool with clients

Almost every ‘our data is wrong’ conversation traces back to a setup that was assembled out of order. Someone added a Meta Pixel before the data layer existed, so it scraped values off the DOM and broke the first time the page changed. We rebuild tracking in strict dependency order — define events, lay the data layer, then config, then platform tags — because the sequence is the product. This wizard encodes that sequence so a build does not skip a load-bearing step.

The two steps with the best return right now are enhanced conversions and proper consent handling. Enhanced conversions (and Meta’s advanced matching) pass hashed first-party data so conversions survive cookie loss — it is the cheapest durability you can buy. Consent Mode v2 is the other: implemented correctly, it keeps you compliant and recovers a meaningful share of otherwise-lost conversions through modeling. We treat both as default, not optional.

The mistake we warn clients about most on server-side is deduplication. Routing events through a server container is only half the job; if the browser and server both report the same purchase without a shared event ID, the platforms double-count and your ROAS looks better than reality. We will not sign off a server-side build until dedup is verified, and the wizard calls it out explicitly so nobody forgets.

The math

How it works

The wizard sequences a tracking build by dependency rather than by checklist. It begins with the money events specific to your business, then the data layer those events need, then GA4 and GTM, then platform conversion tags, then durability layers (enhanced and server-side conversions), with Consent Mode enforced throughout and validation last. Your inputs add or remove the server-side and consent steps and tailor the event list.

Plan order = Foundation → Events → Platforms → Consent → Server-side → QA

Each step depends on the ones above it being clean

Durability = enhanced conversions + (optional) server-side with event deduplication

Business type — sets which money events the plan defines first.
GTM status — whether the auditable tag foundation already exists.
Server-side — adds container and deduplication steps when planned.
Consent Mode — enforced throughout; flagged for implementation if missing.

Enhanced conversions and Consent Mode v2 reflect current Google guidance on enhanced conversions and Consent Mode. This is an RGM recommended sequence; confirm exact steps in the official docs and have privacy counsel review your consent setup.

Why it matters

Why setup order is the whole game

Conversion tracking fails quietly. A mis-sequenced build still reports numbers — they are just wrong, and you do not find out until you have optimized a quarter of spend against them. The fix is to treat setup as a dependency chain: you cannot fire a reliable purchase event without a data layer, you cannot trust a platform conversion tag without GA4 measuring the same event, and you cannot interpret any of it without consent handled correctly. Order is not a preference here; it is the difference between data you can act on and data that flatters you.

The ground is also shifting under browser-based tracking. Third-party cookies, Safari’s ITP, and ad blockers all erode the old client-side model, which is why enhanced conversions and server-side collection have moved from nice-to-have to default. Passing hashed first-party data and routing events server-side recovers conversions that browser tags now miss — but only if you also deduplicate, or you trade one error for another.

Finally, measurement now lives inside consent. Consent Mode v2 is not a bolt-on; it governs whether your tags may fire and store data at all, and done right it recovers a share of lost conversions through modeling while keeping you compliant. The wizard threads consent through every step rather than tacking it on at the end, because that is how regulators — and honest reporting — expect it to work.

Benchmarks

The setup sequence at a glance

The dependency order the wizard generates. Each phase assumes the one above it is clean.

RGM recommended sequence, aligned to Google enhanced conversions guidance. See the GA4 hub, GTM hub, and conversions API hub.
Phase	Goal	Key outputs
Foundation	Events + GTM + GA4	Defined money events, data layer plan
Events	Reliable event capture	GA4 event tags, marked key events
Platforms	Optimizable conversions	Google/Meta tags with value
Consent	Compliant measurement	Consent Mode v2 wired
Server-side	Durable collection	Server container + dedup
QA	Trustworthy numbers	Preview, DebugView, reconciliation

Voices worth trusting

What practitioners say about tracking setup

Tracking that was built out of order does not error — it lies. The sequence is the safeguard.

RGM measurement desk

Field note

Server-side without deduplication is just double-counting with extra steps. Verify the shared event ID before you celebrate.

RGM measurement desk

Field note

Go deeper

Go deeper on measurement

Web Analytics 2.0Avinash KaushikThe foundational mindset for trustworthy digital measurement.Data-Driven MarketingMark JefferyWhy clean measurement is the precondition for every optimization that follows.

Related on RGM

Keep learning

Glossary

Learn & train

Services

FAQ

Common questions

What order should I set up conversion tracking in?

Build by dependency: define the money events, lay a clean data layer, install GTM and GA4, add platform conversion tags, layer durability (enhanced and server-side conversions), enforce Consent Mode throughout, and QA end to end last. The wizard generates that sequence for your situation.

Do I need GTM and GA4 both?

In most modern stacks, yes. GA4 is the measurement backbone the ad platforms borrow from, and Google Tag Manager is the single, auditable place to manage every tag and trigger. The wizard installs GTM first if you do not already have it.

What are enhanced conversions and why do they matter?

Enhanced conversions (and Meta’s advanced matching) hash and pass first-party data like email or phone so conversions survive third-party cookie loss. They are the highest-return durability step in a modern setup, so the plan treats them as default.

Should I use server-side tracking?

Increasingly, yes. Server-side GTM plus conversion APIs improves match quality and resilience to browser restrictions. The catch is deduplication: send a shared event ID on browser and server hits, or platforms will double-count your conversions.

What is Consent Mode v2 and do I need it?

Consent Mode v2 lets your tags adjust to a user’s consent choices and can recover some lost conversions through modeling. It is required for compliant measurement in many regions; implement it with defaults denied and have privacy counsel review your setup.

How do I know my tracking is working?

Validate end to end before trusting any number: use GTM Preview, GA4 DebugView, and the platform tag assistants to confirm each event fires once with the right value and respects consent, then reconcile counts to your back end weekly for the first month.

Related tools