{# DE + SK hreflang odebráno 2026-05-24 — viz core/settings.py LANGUAGES. cross_lang_alternates is set False by views whose CS/EN versions live on DIFFERENT paths (KB articles/categories, blog posts) — there the naive same-path alternate would point at a non-existent URL, so we emit only the self-canonical instead of a wrong reciprocal. #} Skip to content

Why GA4 and Google Ads conversions don't match (and when that's fine)

GA4 shows a different conversion count than Google Ads and you don't know which to trust. The most common causes of the gap — and which ones server-side fixes.

D
DataNostro Team 7. 6. 2026 · 9 min · Intermediate

A classic situation: GA4 reports 100 conversions, Google Ads 130, and your store has 110. Which number is right? Short answer: none and all of them — each just measures something slightly different. Here's why the numbers differ and when the gap is a problem.

Why the counts differ fundamentally

  • Different attribution windows. Google Ads by default credits a conversion to a click up to 30 days back. GA4 counts by its own logic. The same purchase can land on a different day or channel.
  • Different attribution model. Google Ads and GA4 may use different models, so they split credit differently.
  • Different counting methods. Google Ads can count "every" conversion (including repeats), while GA4 typically handles per-user/per-session differently. For a single purchase it doesn't matter, for repeats it does.
  • Time shift. Google Ads credits the conversion to the day of the click, not the day of purchase. That alone creates differences in daily reports.

These are expected differences, not errors. The goal isn't identical numbers, but understanding why they differ.

When the gap is a real problem

  • Far fewer conversions in ads than orders in the store. That means data loss — typically to ad-blockers and ITP. This is exactly what server-side fixes.
  • Dramatically more conversions. Deduplication is probably missing and conversions are counted twice. See GA4 and Meta CAPI deduplication.
  • Numbers jump day to day for no reason. A sign of unstable measurement or a data layer error.

How to reconcile in practice

  • Always have a third, "ground truth" source — the order count in your store. Relate both measurements to it.
  • Compare the same periods and the same conversion definitions.
  • After deploying server-side, watch how ad conversions move closer to the actual order count — that's the main sign of success.

How server-side helps

Server-side tracking won't align attribution windows or models — those are platform properties. What it does is close the losses: it recovers conversions that slipped past client-side, so the ad numbers move closer to your store's reality. The differences from different windows remain, but the "missing" conversions disappear.

Summary

GA4 and Google Ads will never match exactly on conversions — and that's fine. What matters is recognizing when the gap is natural and when it signals data loss. Server-side tracking addresses the second, problematic part. More in server-side vs. client-side or GA4 via DataNostro.

Share

A new article once a month

In-depth server-side tracking guides + case studies from the CZ market. No spam, just 1 email a month. Unsubscribe anytime.

Back to Tracking