Google Tag Manager is the technical middleman, GA4 helps you analyse website behaviour, and Google Ads uses selected conversions to measure and optimise campaigns. If one link in the chain is set up wrong, the numbers quickly start telling different stories.
In short
GTM
Listens for the event and fires the right tags at the right moment.
GA4
Analyses the event together with the user’s journey, channels and behaviour.
Google Ads
Uses the selected conversion as the campaign result and, where needed, for Smart Bidding to learn from.
The simplest analogy: GTM is the plumbing, GA4 is the analysis tool, and Google Ads is one of the systems that uses the measured result to steer advertising. They’re not three competing tools.
One example: someone submits a contact form
01 · Website
The form has to actually succeed
Ideally, a successful submission creates a clear event or dataLayer push.
02 · GTM
The tag fires on the right event
GTM passes the necessary data to GA4 and/or Google Ads.
03 · Destination platform
The data gets the right role
GA4 analyses, Google Ads measures and optimises towards the chosen goal.
I don’t usually start a tracking check from a GA4 report. I start where the event happens and move forward step by step until I see where the data gets lost or changes.
Richard Pikmets
Why don’t Google Ads and GA4 numbers have to match exactly?
The same lead can be attributed differently in different systems. Platforms have different models, identifiers, lookback windows and data processing. So the goal isn’t to force every report onto one number, but to understand why the difference occurs and whether the trend and technical logic are reliable. How Google Ads and GA4 calculate conversion rate is explained in the article conversion rate.
Common mistakes in this chain
- a click on the form’s submit button counts as a conversion even when the submission fails;
- the same event fires through both a plugin and GTM;
- a GA4 event is imported into Google Ads while a separate Google Ads conversion tag runs in parallel;
- the Consent Mode default state is set too late;
- the event exists in GA4, but Google Ads optimises towards a different primary conversion;
- the online store’s purchase event is missing a transaction ID, value or correct currency.
How to test whether the chain works
- Perform a real test action on the website.
- Check in GTM Preview which event was triggered.
- Check which tags fired.
- Check the browser’s network requests and consent state.
- Look at GA4 DebugView or Realtime.
- Check the conversion source diagnostics and status in Google Ads.
Where does server-side GTM fit in?
Server-side tagging adds a server between the browser and the destination platform. It can help with first-party data, server-side integrations and more complex tracking, but it won’t fix poorly defined events. To decide whether you need it, read “Server-side GTM: when it pays off and when it doesn’t”.
Stape as one hosting option
If server-side Google Tag Manager is necessary in your situation, one hosting solution built specifically for sGTM is Stape. It can be convenient if you don’t want to manage the whole server infrastructure yourself.
Affiliate note: the Stape link is an affiliate link. If you sign up through it, I may earn a commission; your price doesn’t change.
If browser-side GTM, consent management and the core conversion logic aren’t in order yet, I’d fix those first. Adding a server just makes broken tracking more complicated.
When do you need all three?
If you use Google Ads and want to analyse overall website behaviour alongside campaign conversions, GTM + GA4 + Google Ads is a very common combination. Still, GTM isn’t mandatory in every technical setup: some platforms can handle integrations correctly on their own.
If the systems tell different stories, see also the Google Tag Manager, GA4 and conversion tracking services. If you also want to see what happened before the visit, read the Search Console guide.
Richard Pikmets