Practical guide

How to Track Conversions Correctly with GA4 and GTM

Installing Google Analytics does not mean that the site's important actions are correctly measured.

A submitted form, a call, a quote request, or an important click must correspond to an identifiable event, triggered at the right time and verified in the tools.

See how a conversion is measured

The first pitfall

A click on "Send" is not necessarily a submitted form

A button can be clicked even when the form contains an error, a request fails, or the user abandons before confirmation.

Measurement must correspond to the genuinely useful action: successfully submitted form, confirmed appointment, triggered call, finalized purchase, or other clearly defined business event.

Poor measurement

clic_bouton_envoyer

The click can occur while the useful action is not yet confirmed.

Closer to the real action

form_submit_success

The event is triggered after actual submission validation.

Illustrative example, not a universal convention.

Terminology

Three levels not to be confused

The same journey can produce an event in GA4, become a key event, then be used as an ad conversion depending on context.

Level 1

Event

A recorded interaction: click, submission, download, video play, form step, or other defined action.

Level 2

Key event

In GA4, an event important for the business can be marked as a key event to be tracked more explicitly in reports.

Level 3

Ad conversion

An action used to measure or optimize the performance of an ad campaign, for example in Google Ads.

Implementation

GTM triggers and transmits; GA4 analyzes

Google Tag Manager manages tags and their triggers: specific click, confirmation page, custom event, or other condition defined in the site.

GA4 then receives the configured events and makes them available for analysis.

Google Tag Manager

GTM

  • triggers
  • tags
  • conditions
  • transmission

Google Analytics 4

GA4

  • received events
  • reports
  • segments
  • key events
  • analysis

Illustration · Example

A single form can generate multiple events

Illustration

Form

The form is validated then successfully submitted.

Request sent

Events emitted

  • form_view
  • form_start
  • form_errornot fired
  • form_submit_success

In summary

submit success present.

If only the button click is measured, the three user journeys can be confused.

Priorities

Start with actions that actually change something

  • 1

    submitted form

  • 2

    confirmed appointment booking

  • 3

    click to a phone number when it has real business value

  • 4

    quote request

  • 5

    significant download

  • 6

    signup

  • 7

    critical funnel step

  • 8

    purchase or booking when relevant

Not everything clickable needs to become a key event.

Control

Tracking problems are often invisible until tested

#1

Duplicate triggering

The same action sends two events and artificially inflates results.

#2

Wrong timing

The event fires on click while the action can still fail.

#3

Missing event

The site works, but no usable data is sent.

#4

Inconsistent naming

Two similar journeys use different events and become hard to compare.

#5

Lost context

The event exists but does not carry the parameters needed to understand where or how it occurred.

Validation

An event must be tested before being used in a report

Step 1

Trigger

Perform the actual action on the site.

Step 2

Observe

Verify the event is sent at the expected time.

Step 3

Check

Verify its name, parameters, and absence of duplicates.

Step 4

Confirm

Verify it appears correctly in the analytics tool and, if necessary, in the relevant ad platform.

DebugView or preview mode references can be useful depending on the tools, but this guide does not provide an exhaustive tutorial.

Before adding ten events

A measurement plan avoids building tracking on an ad-hoc basis

When multiple pages, forms, or campaigns need to be measured, it becomes useful to define in advance the events, their names, parameters, and the conditions that trigger them.

This structure then facilitates implementation, testing, and data reading.

After the form

A web conversion is not always an actionable lead

The site can record a submitted form without knowing if the request becomes an actual lead, appointment, or sale.

To go further, it is sometimes necessary to connect the form, CRM, and acquisition source to track what happens after submission. Connect the site, CRM, and internal tools This also makes it easier to measure where enquiries come from and reduce dependence on referrals.

Technical implementation

You know what to measure, but not how to implement it?

A marketing team may already have defined the necessary events: forms, important clicks, journey steps, ad conversions.

Atomic Design can assist with implementation: events in the site, dataLayer when necessary, GTM configuration, trigger validation, and connection with the relevant tools.

You keep the measurement strategy. Atomic handles what needs to be developed, connected, and tested.

Discuss your tracking

What about server-side tracking?

Some configurations move part of the tag processing to the server side. This is a separate topic, useful in certain contexts but requiring its own architecture and configuration.

Related pages

Pages liées

Quelques pages utiles pour prolonger la lecture selon votre besoin actuel.

What Is Session Replay Used for on a Website?

See how a journey unfolds over time to complement the event-level view.

Open page →

What Is a Heatmap Used for on a Website?

Understand where clicks and scroll concentrate on a page before drilling into events.

Open page →

What Is an A/B Test Used for on a Website?

See how to test a hypothesis after website key events are measured correctly.

Open page →

Practical implementation

Your numbers are there, but you don't know if they're measuring the right thing?

We can verify the events actually sent, identify gaps between the site's journey and the available data, then correct the implementation.

Discuss your site