Conversion tracking: a practical setup guide

The short answer: conversion tracking records the actions that matter, such as a demo request or a closed deal, and passes them to analytics and ad platforms so you can judge campaigns. A reliable setup has one clear definition for each conversion, one tag firing once, consent handled, and a route for later outcomes to come back from the CRM.

What a conversion is, and which ones to track

A conversion is an action you want a visitor to take. Track a small number of them, ranked by how close they sit to revenue.

• Macro conversions: a demo request, a quote request, a purchase or a trial start. These are the actions a campaign is judged on.
• Micro conversions: a pricing page view, a download or a calculator use. They are useful signals, but they should not be what a bidding algorithm optimises for.
• Downstream outcomes: a qualified lead, an opportunity or a closed deal. These happen in the CRM, after the visit, and are the most valuable of all.

Write each definition down in plain words: what exactly counts, where it is recorded and who owns it. Most disagreement between reports starts with two people counting different things under one name.

The tracking stack

• Tag manager. Google Tag Manager holds the tags and the rules for when they fire, so changes do not need a developer each time. See GA4 and Tag Manager setup.
• Analytics. GA4 records events, and you mark the important ones as key events.
• Ad platform tags. Google Ads, Meta, LinkedIn and Microsoft each have their own conversion tag or pixel, plus server-side options such as the Meta Conversions API.
• Consent layer. A banner and consent signals decide which tags may run. See POPIA and marketing tracking.
• Server-side tracking, where justified, to control what leaves your site. See what server-side tracking is.
• The CRM, which records what the lead became.

Setup, step by step

• 1. Write the tracking plan. List each conversion, its trigger, its event name, the platforms that need it, and who checks it.
• 2. Build one event per action. Fire a single event on a true success signal, such as a thank-you page or a confirmed form response, not on a button click.
• 3. Send it to GA4 and mark it as a key event.
• 4. Add the ad platform conversions. Either import from GA4 or fire native tags, but count each action from one primary source only. See GA4 vs Google Ads conversions.
• 5. Pass identifiers through. Save UTM tags and the ad click ID in hidden form fields so the CRM record carries them. See what UTM parameters are.
• 6. Handle consent. Make sure tags wait for consent where the law requires it, and that the banner records the choice.
• 7. Send later stages back. Feed qualified leads and closed deals to the ad platforms. See offline conversion tracking.

How to test it

• Use Tag Manager preview mode to confirm each tag fires once, on the right action, with the right values.
• Use GA4 DebugView to confirm the event arrives with its parameters.
• Use each platform's own test tool, such as Meta's test events, to confirm it receives the event.
• Submit a real test lead and follow it into the CRM, checking that the source, UTM tags and click ID arrived.
• Repeat the test with consent granted and with consent denied, and on mobile as well as desktop.

What usually goes wrong

• The same action is counted by two tags or by a tag and an import.
• The event fires on a button click, so failed or abandoned forms are counted as conversions.
• The thank-you page can be reloaded or reached directly, so one lead is counted many times.
• Single-page forms or embedded forms do not trigger the usual page-view rule.
• Consent settings block tags, and nobody checks the result.
• The click ID is not saved with the form, so nothing can be matched later.
• Event names change over time, so reports quietly break.

Past the form fill: tracking what the lead became

A form fill is the first and weakest signal. The CRM knows whether the lead was qualified and whether it closed. Sending those outcomes back lets the platforms optimise for customers instead of for form submissions, and lets you see which campaigns really paid. This is where tracking becomes attribution: see B2B marketing attribution.

A quick audit checklist

• Every conversion has a written definition and an owner.
• Each action is counted from one primary source.
• The event fires once, on a true success signal.
• UTM tags and click IDs reach the CRM record.
• Consent behaviour has been tested both ways.
• Later CRM stages are sent back to the platforms, or the plan to do so is documented.
• Reports from GA4, ad platforms and the CRM have been compared for the same period, and the gaps explained.

The free PPC audit and the free data audit both check these points against your own accounts.

Questions people ask

Related: check your click ID coverage with the GCLID coverage checker.