Web Analytics · Google Analytics & GA4

GA4 Event & Conversion Tracking

One agreed name per action, one agreed rule for what counts as a key event.

When teams use different names for the same action, GA4 stops giving them a shared view of performance. We rebuild the event and conversion setup so each number has one agreed meaning.

An event and key-event setup your team can read, test, and keep tidy long after we leave.

Talk through the setupAll Google Analytics & GA4 Consulting tasks
Two Zeo specialists wiring GA4 event tiles through a DebugView lens toward a key-events board

Some of the 500+ brands we've worked with

See all references
  • BMW
  • PepsiCo
  • eOfis
  • Dalin
  • Desa
  • Eureko Sigorta
  • GoTürkiye

How we run it

From disputed definitions to an agreed event model

This work stays inside GA4, while deployment mechanics remain with GTM. Each step resolves a specific decision and produces an artifact your team can review.

How we hold ourselves to it

  • Business actions, turned into one agreed event model — We identify the actions that matter, including signups, checkouts, leads, and key page views, and turn them into a clear GA4 event model. Each event gets one agreed meaning.
  • One naming convention, applied to every parameter and key event — We write the naming convention, the parameters each event carries, and the criteria for marking an event as a key event. No more guessing which of five similar events feeds a report.
  • Where GA4 configuration ends and GTM begins — We review or set up the event and key-event configuration inside GA4 and cross-check where the GTM boundary sits, so nothing is configured twice or left in no man's land.
  • What DebugView confirms and what it cannot see — We replay representative journeys in DebugView and standard reports, record what GA4 cannot observe, and document the exceptions so they are not mistaken for defects later.

  1. Align on actions and definitions

    We agree on the list of business actions, what each one is called, and which ones deserve key-event status. This is where disputes about meaning get settled, before they turn up in a report six months later.

    Agreed action list

    AI assist
    Scans existing GA4 properties to extract active event schemas and unmapped parameters.
    Human gate
    Measurement specialist confirms business event definitions with product and marketing leads.
    Owners
    Measurement Analyst, Business Stakeholder
    Illustrated figure holding up a signed agreement page

  2. Map the implementation

    We compare the agreed model with what GA4 currently collects and map which events should exist, which parameters they should carry, and where GTM takes over.

    Event mapping sheet

    AI assist
    Compares agreed events against what GA4 already collects.
    Human gate
    Analyst confirms the target-state mapping is buildable.
    Owners
    Measurement Analyst, GTM Owner
    Illustrated figure sketching plans at a drafting table

  3. Test the journeys

    We replay the journeys the business relies on, such as signup, purchase, and lead submission, in DebugView and confirm that events and parameters arrive as designed.

    Journey test notes

    AI assist
    Flags events or parameters missing in DebugView.
    Human gate
    Analyst decides whether a flagged gap is a real defect or just noise.
    Owners
    Measurement Analyst, Engineering Contact
    Illustrated figure reading an oversized measurement dial

  4. Reconcile and report

    We compare GA4 numbers against the sources you trust, explain the gaps we can explain, and flag the ones that come from consent, blockers, or platform behaviour.

    Reconciliation summary

    AI assist
    Calculates variance between GA4 and trusted sources.
    Human gate
    Analyst attributes each gap to consent, blockers, or platform.
    Owners
    Measurement Analyst
    Illustrated figure examining a search result row through a large magnifier

  5. Hand over and set recheck triggers

    We review the documentation with your team and agree on the changes that should trigger another check, such as a site relaunch, consent update, or new platform feature.

    Handover session

    AI assist
    Drafts recheck triggers from the events most likely to drift.
    Human gate
    Team agrees which triggers actually warrant a re-check.
    Owners
    Measurement Analyst, GTM Owner
    One illustrated figure passing a relay baton to another

Four parts of GA4 configuration, with deployment kept in GTM.

Automation scans the property for active event schemas and unmapped parameters, compares the agreed events against what GA4 already collects, flags what DebugView cannot see, and calculates the variance against trusted sources. Meaning stays with people: what a business action is, whether a gap is a defect or noise, and what to attribute the remainder to.

What you get

An event dictionary that answers the question before someone has to ask.

Every document here is meant for daily use.

  • Working document

    Event dictionary

    Every event with its agreed name, its meaning, and the business action behind it. The single place to check what anything in GA4 is supposed to be.

    Accepted when

    Every event name in the property appears in the dictionary with the business action behind it.

    Cadence: Extended with every new event

  • Configuration specification

    Parameter and key-event specification

    The parameters each event carries, their expected values, and the exact criteria that make an event a key event in your property.

    Accepted when

    Each key event states the criteria that make it one, not just the checkbox.

    Cadence: Revised when a key event changes

  • QA notes

    Validation notes

    What we tested, what passed, what we could not observe, and why. Includes the DebugView and report evidence from the journey tests.

    Accepted when

    What could not be observed is written down as unobserved, with the reason.

    Cadence: Captured per validation pass

  • Runbook

    Maintenance and handover guide

    How to add a new event without breaking the convention, who owns what, and when the setup needs a fresh look.

    Accepted when

    A new owner can add an event from the guide without breaking the naming convention.

    Cadence: Updated at handover

We call it done when: the journeys replay cleanly in DebugView, the counts reconcile against a trusted source inside an agreed variance, and the negative cases produce nothing.

Fit and readiness

The team needs one definition of what counts as a conversion.

Here is how to tell whether this work fits the problem.

A good fit when

  • Reports show the same action under several event names, or nobody is sure which event counts as a conversion.
  • A new site, app, or consent setup is coming and the current event model will not survive it unchanged.
  • Marketing, product, and analytics use different key-event definitions, so the same business action changes meaning from one report to another.
  • A business owner can say what each action means, but the GA4 event model has never captured those definitions.

Better handled as other work when

  • You need tags, triggers, or containers built or repaired. That is GTM work, and we will direct you to the appropriate task.
  • There is no one available who can confirm what the business actions actually are, so events would be named in a vacuum.

If one of these is closer to your situation, start here instead: All Google Analytics & GA4 Consulting tasks

We call it done when: product and marketing have agreed what each business action means before a single event name is written.

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.

Content we've produced on this topic

Articleby Zafer YıldızConversion Structure & Conversion Creation in Google Analytics 4Articleby Zafer YıldızHow to Track Mouse Hover on Google Analytics 4 with GTM?

Tools we use

Tools behind this work

  • Google Analytics

    DebugView confirms an event arrived with the right parameters, not just that it fired

  • Google Tag Manager

    where every mapped event actually gets deployed, kept apart from the GA4 settings

  • Google Tag Assistant

    walks the test journeys step by step to confirm each tag actually fired

Next step

Resolve the event model before relying on the next report

Share the current event list and the business actions behind it. We will assess whether the issue belongs in GA4 event design or requires a different task.
Talk through the setup

Before we start

Questions teams ask before booking

No. Tags, triggers, and containers belong to our GTM work, and we keep that boundary explicit. Here we own how events and key events behave inside GA4, and we coordinate with whoever handles deployment so nothing is configured twice.