Insights
Tracking & Attribution

Your Google Ads Numbers Are Not Wrong. Neither Are Your Meta Numbers. Here’s the Problem.

Jamie Frazer 17 May 2026 16 min read
diagram with explanation why conversions apear to gomissing

Open your ad dashboards on any given Monday morning and you will see something that makes no logical sense. Google Ads says you had 94 conversions last month. Meta Ads Manager claims 71. GA4 reports 52. Your CRM shows 63 actual customers.

Same business. Same month. Same campaigns. Four completely different answers.

If you have spent any time trying to figure out which number to believe, you have already done something counterproductive — because the question is wrong. None of these numbers is the correct one. Each is a different and valid answer to a slightly different question. The problem is that nobody tells you what question each platform is answering.

That gap — between what the platforms show and what you think they’re showing — is where budget decisions go wrong, campaigns get cut that should be scaled, and agencies spend client calls defending numbers that were never designed to match.

This guide explains every mechanism that creates the divergence: the attribution windows, the identity resolution differences, the view-through counting rules, and the two significant 2026 Meta attribution changes that have moved numbers across every advertiser’s account. By the end, you will know exactly what each figure means, which one to use for each type of decision, and how to tell the difference between a structural reporting difference and a genuine tracking failure that is costing you campaign performance.

Why conversion data will never perfectly match across platforms

Conversion numbers will never align perfectly across Google Ads, Meta, GA4 and your CRM because each platform uses a different definition of a conversion, a different attribution window, a different method for resolving user identity, and a different approach to handling users who decline tracking. These are structural differences, not errors — and they are not fixable by switching agencies.

A large portion of the gap you’re seeing is not a tracking failure. It is the expected, intended result of four systems measuring the same event from four different angles with four different rulebooks. Chasing a state where all four numbers match is the wrong goal. It is not achievable, and attempting it will lead you to make configuration changes that introduce real problems in exchange for illusory alignment.

Understanding the gap — knowing which parts are structural and which parts indicate a genuine problem — is what lets you make confident decisions even when the dashboards disagree.

The structural sources of divergence fall into four categories:

Attribution windows determine how long after an ad interaction a platform will claim credit for a conversion. Meta defaults to 7-day click, 1-day view. Google Ads defaults to 30-day click for Search and Display campaigns, per Google’s official conversion window documentation. GA4 uses data-driven attribution that distributes credit across all touchpoints in a journey. The same conversion is therefore counted by multiple platforms simultaneously — each correctly applying its own rules.

Identity resolution is how each platform connects an ad click to a later conversion. Google uses GCLIDs and signed-in account identity. Meta uses its own cookie and account identity. GA4 relies on a browser cookie that breaks across devices. When a customer moves across devices between clicking an ad and converting, each platform resolves their identity differently — meaning some see the conversion and some don’t.

View-through attribution is credit claimed for conversions from users who saw an ad but never clicked. Meta and Google both do this for certain campaign types. GA4 does not — it can only track sessions initiated by an actual click. This is the primary reason Meta typically reports more conversions than GA4 for the same period.

Privacy changes have removed data that used to make the numbers closer. Apple’s iOS 14.5 App Tracking Transparency removed the cross-app signal Meta relied on to link impressions to conversions. Cookie consent requirements mean users who decline tracking are invisible to GA4 but may still be partially attributed in ad platforms through other signals.

What changed in 2026 — and why your Meta numbers look different

Meta made two separate attribution changes in 2026 that reduced reported conversions. Both are measurement corrections, not performance declines. January 2026 removed longer view-through attribution windows. March 2026 changed the definition of a click. Check your CRM before making any campaign decisions in response to either.
January 12, 2026 — View attribution windows removed. Meta permanently removed the 7-day view and 28-day view attribution windows from the Ads Insights API. Advertisers running awareness and video campaigns who relied on these windows saw reported conversions drop 15–40% overnight. Only 1-day view remains. The conversions were still happening — Meta stopped counting view-based ones beyond 1 day. If your numbers dropped around January 12, this is the cause.
March 3, 2026 — Click definition changed. As confirmed in Meta’s official announcement, only link clicks that bring a user to your site now count as click-through attributions. Previously, any interaction — likes, reactions, shares, saves — qualified. Non-link interactions moved to a new category called engage-through attribution with a 1-day window. Note: engage-through has a 1-day window versus the former 7-day window for engagement-based clicks. Conversions where a user engaged (but didn’t link-click) and converted on days 2–7 now fall outside any attribution window entirely. They did not simply move to engage-through — they left Meta’s attribution.

In both cases: check your CRM. If actual customer acquisition held steady, do not pause campaigns, cut budgets, or interpret lower Ads Manager numbers as evidence that Meta stopped working. The measurement became more accurate.

What counts as a real tracking problem versus normal variance

A tracking problem is when platforms report significantly fewer conversions than your CRM records. Normal variance is when platforms differ from each other. If Google Ads and Meta don’t agree, that is structural. If either platform reports less than 60–70% of your actual CRM sales, that is a tracking failure requiring investigation.

This distinction matters enormously in practice. The wrong diagnostic is comparing platforms against each other. Google Ads and Meta are not measuring the same thing — they cannot be used to validate each other.

The correct diagnostic is comparing each platform against your backend.

Pull your actual sales or leads from your CRM or backend system for the last 30 days. That is your baseline. Now compare each platform:

Google Ads conversions ÷ actual sales — a healthy ratio sits between 0.7 and 1.1. Google over-attributes slightly due to its long click window, but should be broadly in line with reality. Below 0.6 indicates significant tracking loss.

Meta conversions ÷ actual sales — Meta legitimately over-reports due to view-through attribution. Post-2026, healthy ratios are lower than pre-2026 baselines due to the attribution changes. Establish your current baseline from post-March 2026 data. If Meta is showing below 0.6× your CRM sales, investigate a Pixel or CAPI failure.

Patterns that indicate a genuine tracking problem:

  • GA4 shows significantly more conversions than Google Ads — likely GCLID loss or conversion action misconfiguration
  • Either platform’s conversions doubled suddenly with no traffic increase — duplicate conversion actions
  • Conversions dropped to zero in one platform while the other is stable — Pixel or tag failure
  • ROAS varies wildly week to week with no changes to budget, creative, or seasonality — tracking instability, not performance variation

→ For step-by-step Google Ads tracking diagnosis: Google Ads conversion tracking troubleshooting guide

→ For step-by-step Meta tracking diagnosis: Meta Ads conversion tracking problems guide

Why broken tracking harms campaign performance, not just your reports

Conversion tracking is not a reporting layer — it is the input signal your campaigns are trained on. When 30–40% of conversions are invisible, Smart Bidding and Meta’s delivery algorithm learn from a broken dataset. They optimise toward the wrong audiences, underfund profitable campaigns, and build lookalike audiences from a partial view of your customers.

Google’s Smart Bidding and Meta’s delivery system are machine learning systems. They observe which users, queries, times of day, and audiences produce conversions — and allocate budget accordingly. When a large portion of conversions are missing from the data they learn from, the algorithm builds its model on a fraction of reality.

The specific consequences:

Smart Bidding underfunds your best campaigns. If a campaign generates 100 actual bookings but tracking only sees 60, the algorithm calculates a ROAS that is 40% lower than reality. It treats a profitable campaign as borderline. Bids stay conservative. Budget stays low.

Meta’s lookalike audiences are built from an incomplete customer profile. If iOS opt-outs and blocked Pixels mean Meta has only seen 60% of your actual buyers, its model of who your customer is reflects that partial picture. The audiences it builds — and the users it serves your ads to — are less accurate as a result.

You make the wrong strategic decisions. A campaign that appears to be at 1.2× ROAS is cut. It was actually running at 2.1× ROAS. Three months of budget is redirected to a weaker channel.

We have seen this consistently with new clients. One private scanning clinic came to us three months into a Meta campaign that looked like a consistent loss-maker. Their booking platform — hosted on a separate subdomain — was breaking the fbclid parameter on handoff, meaning Meta’s Pixel was recording ad clicks but never seeing the resulting bookings. Their Event Match Quality score was 4.2. After implementing server-side CAPI and correcting the subdomain tracking gap, reported conversions increased by 38% in the first four weeks. EMQ moved to 8.1. The campaigns had not changed. The patients were always booking.

What a correct tracking infrastructure looks like in 2026

A complete tracking setup in 2026 requires four components: server-side Google Tag Manager (sGTM), Meta Conversions API (CAPI), Consent Mode v2, and first-party data enrichment. Each component addresses a different failure mode in standard browser-based tracking. Missing any one of them leaves a measurable and growing gap.
01

Server-side Google Tag Manager (sGTM)

A cloud-hosted server container that collects conversion events from your website and forwards them to Google Ads via Enhanced Conversions and to GA4 via server-side tags. Your core conversion events become completely server-dependent — the browser is out of the loop for the events that matter most.

02

Meta Conversions API (CAPI)

Transmits server-side purchase and lead events directly to Meta alongside — not instead of — your browser Pixel. The Pixel handles page views and upper-funnel events. CAPI handles conversion events that affect campaign optimisation. Running both requires deduplication via a shared event ID — without it, the same conversion is counted twice. See Meta’s CAPI documentation for setup.

03

Consent Mode v2

Required for UK and EU advertisers. When users decline your cookie banner, standard tags fire in a denied state and contribute nothing. With Consent Mode v2 properly configured through a Google-certified CMP, Google models conversions for declined-consent users based on patterns from consenting users. That modelled data feeds Smart Bidding.

04

First-party data enrichment

Sending additional customer identifiers — hashed email, phone number, first and last name — alongside conversion events improves Google’s Enhanced Conversion match rates and Meta’s Event Match Quality. The more accurately each platform can connect your server events to real, signed-in users, the better the algorithmic learning and the more accurate the attribution.

→ For a full implementation guide covering sGTM, CAPI, and what the setup actually involves: why your conversion tracking is wrong and how server-side tracking fixes it

How to benchmark your tracking gap in 15 minutes

Compare your last 30 days of CRM sales against each platform’s reported conversions. Google Ads should sit at 70–110% of CRM sales. Meta’s healthy ratio has shifted lower post-2026 — establish a current baseline rather than comparing against pre-2026 data. Below 60% of CRM in either platform means a tracking problem, not normal variance.

You do not need a technical audit to run this check. Pull these figures right now:

  1. 1Last 30 days actual sales or leads from your CRM, Shopify backend, or booking system. This is your ground truth.
  2. 2Google Ads conversions for the same period — Campaigns > Columns > Conversions. Calculate ratio against CRM baseline.
  3. 3Meta Events Manager → your Pixel → Overview → Event Match Quality. Below 6.0 is actionable immediately. Target is 8.0+.
  4. 4Meta Ads Manager conversions for the same period — use click-through + engage-through combined. Calculate ratio against CRM.
  5. 5GA4 → Reports → Events or Monetisation. Compare against both platform figures and CRM.

If either ad platform sits below 60% of your CRM sales, tracking infrastructure should be your first investment — ahead of new campaigns, new creative, or budget increases.

How to use the data correctly when the numbers will never match

Use your CRM as the headline metric for budget decisions. Use GA4 for relative cross-channel attribution. Use ad platform numbers as directional signals within each platform’s own ecosystem. Never add Google Ads and Meta conversions together — the total substantially exceeds actual customers because both platforms attribute the same conversions.

Establish a consistent comparison ratio for each platform and track it over time. If Meta consistently reports 1.2× your CRM sales, that 1.2 multiplier is your baseline. A drop below 0.8× signals a tracking problem. A spike to 2.5× signals attribution degradation or duplicate counting. The ratio matters more than the absolute number.

Never use ad platform conversion totals as your primary figure in stakeholder reporting. Report actual customers from your backend. Explain that platform figures reflect attribution claims, not unique customer counts. This is not a limitation — it is the correct way to present performance data.

Frequently asked questions

Why does Meta always report more conversions than GA4?

Meta uses view-through attribution and a 7-day click window, crediting conversions from users who saw your ad without clicking and from users who clicked up to seven days before converting. GA4 only attributes conversions to sessions it directly tracked via link clicks. Meta will structurally report higher numbers than GA4 — this is expected. The gap has narrowed since March 2026 as Meta’s click definition now aligns with GA4’s.

My Meta numbers dropped in 2026 — what happened?

Two separate changes. January 12, 2026: Meta removed 7-day and 28-day view attribution windows — advertisers running awareness or video campaigns saw 15–40% drops overnight. March 3, 2026: Meta changed its click definition — non-link interactions moved to engage-through attribution with a 1-day window. In both cases, check your CRM. If actual customer acquisition held steady, these are reporting corrections, not performance problems.

Why does Google Ads show more conversions than GA4?

Google Ads uses a 30-day click window and can model conversions from Consent Mode v2 estimates. GA4 uses data-driven attribution distributing credit across multiple channels — GA4 partially credits organic, email, and direct for conversions where they were also involved, whereas Google Ads claims full credit for any conversion following a Google click. Both are correct by their own rules.

What is the right conversion number to use for budget decisions?

Your CRM or backend sales data. It is the only figure that confirms actual customers rather than attribution claims. Use ad platform conversions as directional signals for in-platform optimisation — they matter for Smart Bidding quality — but not as the primary business metric.

How do I know if my tracking is broken or the numbers are just structurally different?

Compare each platform against your CRM, not against each other. Google Ads below 70% of CRM sales indicates tracking loss. Meta below 60% of CRM sales indicates a Pixel or CAPI failure. A sudden drop in your established platform-to-CRM ratio is the primary signal — if Meta was consistently running at 1.3× CRM and has dropped to 0.7× with no corresponding CRM decline, investigate immediately.

If your GA4, Google Ads, and Meta numbers are telling different stories — and you’re not sure which one to trust — we’ll audit your tracking setup and show you what you’re actually missing.

Get a free tracking audit →

Jamie Frazer is co-founder of Bons & Frazer, a performance marketing agency based in Norwich specialising in Google Ads, Meta Ads, and tracking infrastructure for service businesses, clinics and e-commerce brands across the UK and internationally.

Related guides