"I deployed server-side tracking" and "server-side tracking works correctly" are two different statements. Between them is testing that many people skip — and then wonder why their data is off. Here's a practical routine for verifying the measurement really flows.
1. GTM preview mode
Start in Google Tag Manager's preview mode — for both the web container and the server-side container. Walk the site as a customer and watch:
- Do events fire at the right moment (product view, add to cart, purchase)?
- Does the event reach the server-side container from the web?
- Do events carry the correct values (value, currency, transaction_id)?
2. GA4 DebugView
In GA4, open DebugView and confirm events reached Analytics — with the right parameters. This is where you'll catch missing or mislabeled data layer values. If value is missing or zero, the problem is in the data layer, not in server-side. See the data layer as the foundation of measurement.
3. Meta Events Manager — Test Events
In Meta Events Manager, use the Test Events tab. You'll see whether events come from the Pixel and the Conversions API and — importantly — whether they deduplicate correctly via event_id. Also check Event Match Quality. Details in the Meta CAPI guide.
4. Google Ads diagnostics
- In conversion actions, check the "Recording conversions" status.
- For Enhanced Conversions, verify they're being received and the match rate is rising.
- Watch whether the conversion count makes sense against orders in your store.
5. A test against reality
The most important test is the simplest: make (or simulate) a real order and follow it the whole way — from the site, through the server-side container, all the way to GA4, Meta and Google Ads. One verified end-to-end conversion tells you more than an hour of staring at settings.
What to watch out for
- Doubled conversions — a sign of missing deduplication. See deduplication.
- Zero or text values — a data layer error.
- Conversions arrive but match rate is low — missing first-party identifiers (email, phone).
- Nothing changed after deployment — maybe only client-side is still running; confirm the server-side path is actually active.
Summary
Testing isn't an optional step — it's the difference between measurement you trust and measurement you only think works. Walk through GTM preview, DebugView, Test Events and one real end-to-end conversion. Only then is the deployment done. Continue with the complete guide or the sGTM basics.