Web Analytics · Google Tag Manager

Conversion Tag Implementation

The same conversion, wired once per platform, counted once per customer.

Each ad platform needs its own conversion tag. We configure those tags in GTM against the approved event, apply the required consent behavior, and check for duplicate firing.

Browser-side conversion tags that fire once under the required consent state, with platform-side evidence of receipt.

Plan conversion tagsAll Google Tag Manager Consulting tasks
A Zeo technician wiring conversion tags to a switchboard of ad platforms

Some of the 500+ brands we've worked with

See all references
  • Mini
  • Enpara
  • A101
  • Atasun Optik
  • Edenred
  • Marble Systems

How we run it

Platform receipt is the go-live evidence

We use the approved conversion event consistently across every platform that needs it. We confirm the conversion list, configure tags, verify platform receipt, and test consent and duplicate scenarios.

How we hold ourselves to it

  • Map conversions to each platform's tag — We take your already-approved conversions and build the matching tag for Google Ads, Meta Pixel, LinkedIn Insight Tag, or whatever platforms you run.
  • Firing tags on the exact conversion moment — We fire each tag on the exact event that represents the conversion. An approximate page load can misfire, so we don't rely on it as a stand-in.
  • Does every platform respect the same consent signal? — We make sure each tag respects the same consent signal, since ad platforms and GA4 can otherwise end up with different rules for the same visitor.
  • Prevent double-counting — Where a value can be sent by more than one tag or platform, we add the checks needed so your reports don't inflate the number.

  1. Confirm the conversion list

    We start from conversions already defined in GA4 or your business systems. This isn't a new definition exercise.

    Conversion list

    AI assist
    Pulls the already-agreed conversions from GA4 or your systems.
    Human gate
    A person confirms no new conversion gets defined here.
    Owners
    GTM Specialist, Media Buyer
    Illustrated figure holding up a signed agreement page

  2. Build the platform tags

    We configure each ad platform's conversion tag in GTM with the correct trigger and value parameters.

    Tag configuration

    AI assist
    Maps each conversion to its matching platform tag fields.
    Human gate
    We configure the actual trigger and value parameters.
    Owners
    GTM Specialist, Ad Platform Admin
    Illustrated figure stacking patterned building blocks

  3. Test with real and simulated conversions

    We run test conversions through each platform's own verification tools to confirm they're received correctly.

    Platform verification log

    AI assist
    Runs a test conversion through each platform's own checker.
    Human gate
    A person confirms the platform's tool shows it received.
    Owners
    GTM Specialist, Ad Platform Admin
    Illustrated figure reading an oversized measurement dial

  4. Check for duplicates and consent gaps

    We confirm no conversion fires twice and that declined consent is respected consistently across platforms.

    Deduplication and consent report

    AI assist
    Flags scenarios where the same value could fire twice.
    Human gate
    We test declined consent on every wired platform tag.
    Owners
    GTM Specialist
    Two illustrated figures carrying an oversized key together

One conversion, wired the same way to every platform that needs it

Automation pulls the agreed conversion list, maps each one onto the matching platform fields, runs a test conversion through every platform's own checker, and flags where the same value could fire twice. People hold the gates: no new conversion gets defined during implementation, and someone reads the platform's receipt rather than trusting GTM Preview.

What you get

A tag matrix backed by platform-side confirmation

Each tag is documented and verified with the destination platform's own diagnostic tools.

  • Configuration record

    Tag matrix

    Every platform, its conversion tag, trigger, and value mapping in one place.

    Accepted when

    Every row names a platform, a trigger, and a value mapping, with no field left as "to be confirmed".

    Cadence: Extended with every new tag

  • QA evidence

    Platform verification evidence

    Screenshots or exports from each platform's own tools confirming the conversion was received.

    Accepted when

    The receipt comes from the destination platform's own tool, not from GTM Preview.

    Cadence: Captured per platform, before go-live

  • Runbook

    Go-live checklist

    What to check the next time a new ad platform or conversion gets added.

    Accepted when

    The checklist can be run by someone who did not build the tags.

    Cadence: Run at every publish

We call it done when: each platform's own diagnostic tool shows the conversion arriving once, and a declined-consent run produces no request.

Fit and readiness

Every ad platform wants its own pixel on your conversion

Already-approved conversions that just need wiring to ad platforms are the clearest sign this is the right task.

A good fit when

  • Your conversions are already defined and agreed, and now need to be connected to Google Ads, Meta, LinkedIn, or another platform's tags.
  • You're adding a new ad platform and need its conversion tracking built to match what you already have.
  • You suspect the same conversion fires more than once on some platforms, while other platforms receive nothing at all.

Better handled as other work when

  • You have not decided what counts as a conversion yet. GA4 Event & Conversion Tracking owns that definition inside GA4.
  • The problem lies in how GA4 measures the conversion rather than in the ad-platform tags. That also belongs to GA4 Event & Conversion Tracking.

If one of these is closer to your situation, start here instead: All Google Tag Manager Consulting tasks

We call it done when: the conversion list is closed and agreed, so implementation wires what already exists instead of inventing new definitions along the way.

People who build your measurement system

Zeo designs measurement systems that connect a business decision to governed collection and reporting you can check. The people shown here work on the part of that system this page covers.

Tools we use

Tools behind this work

  • Google Tag Manager

    where each platform's own conversion tag gets built against one shared, agreed event

  • Google Tag Assistant

    confirms a tag fired, the half of the proof this page's own FAQ says isn't enough on its own

  • Meta Events Manager

    the receipt evidence on Meta's side, checked against what the tag claims fired

  • Google Ads

    the Google Ads-side conversion status, checked independently of what GTM or GA4 shows

Next step

Get your conversions counted right, on every platform

Tell us which platforms you advertise on and which conversions are already approved. We will connect them and verify their operation before go-live.
Plan conversion tags

Before we start

Questions teams ask before booking

Google Ads, Meta, LinkedIn, and most platforms that support a browser-side or GTM-compatible conversion tag. Tell us your ad mix and we'll confirm the specifics.