Attribution & Measurement

Why your numbers never match between platforms

Your ad dashboards and CRM can count different things, even when the tracking works. Here is how to check the definitions, find the gaps, and explain the report.

Founder of MetricMaven. Previously managed Google Tag Manager and Google Analytics across 800+ sites at HCA Healthcare, and built attribution and eCommerce reporting at RYZE Superfoods and Mars.

You have checked the monthly report twice. Then someone opens an ad dashboard in the meeting and asks why its conversion total is different. The campaign discussion stops while you compare the numbers.

A mismatch can mean the tracking is broken. It can also mean the reports count different things. You need to establish which before changing a tag or correcting a spreadsheet.

Why your numbers never match between platforms

Start with the word “conversion.” On one screen, it might mean a submitted form. On another, it might mean a qualified contact. In the sales report, it might mean a deal that finally closed.

A submitted form, a qualified contact, and a closed deal each deserve a place in the report. Calling all three “conversions” makes it harder to see where people drop out between them.

Before comparing totals, agree on what the report counts. Name the event or record, the reporting period, and the source that owns it. For example, “new contacts created this month” is a definition you can check against the CRM.

What makes platform numbers differ?

Choose one record and trace it through the reports. Check the event definition, attribution window, time zone, duplicate handling, and filters. These checks are easier to resolve on a single record than on an unexplained difference between monthly totals.

Three analytical lenses turn one customer journey into different reports, with filters, identity cards, and a calendar.

A person might click an ad, return through search, and fill out a form. Several systems can record that submission. If the person later buys, the sale creates a separate record with its own date.

Each system also decides which interactions can receive credit and which records belong in the report. One may exclude internal traffic. Another may still contain test submissions. A repeated form submission may count as another event without representing another person.

Which platform usually reports more?

For most pairs, one side reading higher is expected, and the direction tells you where to look. A gap that flips direction, or jumps from one week to the next, points to a change in tracking or settings rather than a difference in rules.

ComparisonUsually higherMain reasonGuide
Meta Ads vs GA4Meta AdsMeta can credit views with no click and credits only Meta ads; GA4 cannot see impressionsMeta vs GA4
Google Ads vs GA4Google Ads, for its own campaignsGoogle Ads credits only its own clicks; GA4 shares credit with organic, email and directGoogle Ads vs GA4
LinkedIn Ads vs GA4LinkedIn AdsView-through conversions, and Lead Gen Form leads that never reach your siteLinkedIn vs GA4
Shopify vs GA4 revenueShopifyShopify counts every order in its backend; GA4 counts only purchase events it receivesShopify vs GA4
Email or SMS clicks vs GA4 sessionsPlatform clicksSecurity scanners click links, and a session needs the page and the GA4 tag to loadEmail and SMS vs GA4
CRM customers vs customer-list audiencesCRMAn audience only includes people the ad platform can match to an accountCustomer and audience counts
HubSpot, Salesforce or GoHighLevel vs GA4Neither: they count different thingsGA4 counts events and sessions; the CRM counts contacts, leads and dealsHubSpot vs GA4
Direction only. How large a gap is depends on your settings, consent rates and traffic mix, so compare against your own baseline.

How do attribution windows change the numbers?

Suppose someone clicks an ad and buys ten days later. With a seven-day click window, that click falls outside the window. With a thirty-day window, it falls inside. Check your account settings to see which rule applies.

The window determines which interactions are eligible. The attribution model determines how credit is assigned among them. Changing either can change the story a report tells about the sale.

Check the actual settings before assuming a platform default. Google Ads, for example, distinguishes the lookback window in its attribution reports from the conversion window configured for a conversion action. Its attribution reporting guide explains that distinction.

Put the window and model beside the metric, where the person reading the report can find them. Our guide to attribution models explains how the credit is assigned.

Why do time zones move totals between months?

A purchase at 11:40pm Pacific on the last day of the month falls on the following day in UTC. The event is identical; its reporting date is different.

That is enough to move it out of one monthly total and into the next. If a small gap appears around month-end, check the timestamps before looking for missing purchases.

Apply the same reporting time zone when comparing periods, and document any source that cannot be aligned. Do not assume the difference will cancel out next month.

De-duplicate once, at the source

Adding platform conversion totals is another common mistake. Google and Meta can both claim credit for the same sale. Their combined total does not tell you how many sales took place.

Start by deciding what should be unique. A contact, an order, and a closed deal need different identifiers and different rules. Match records only where a reliable identifier supports the connection.

Leave unmatched records visible. If an identifier is missing or ambiguous, record that limitation rather than guessing which contact or order it belongs to.

How do you reconcile numbers across platforms?

A spreadsheet can handle these checks at first. The person building the report knows which export to use, which records to exclude, and why the CRM total is lower.

Three streams of marketing records pass through alignment, filtering, and identity matching to become one reconciled ledger.

When that person is away, someone else has to work out the rules again. This is a good reason to move the recurring checks out of someone’s head and into a documented reporting process.

A reconciliation layer applies those rules to the source records each time the report runs. It records the definitions, exclusions, and matching logic behind each metric so another person can inspect them.

Keep website submissions, qualified contacts, and closed deals separate. Name an owner for each metric and explain how the records connect. You should be able to answer a question about a total without rebuilding the report. If no one in-house can own those definitions, see how fractional analytics leadership works.

A checklist before you send

Before sharing the report, check that someone else could reproduce its totals from the definitions you have written down.

  1. Name the event or record being counted and the source that owns it.
  2. State the attribution window and model where they apply.
  3. Confirm the reporting period and time zone.
  4. Document duplicate handling and exclusions for tests, spam, and internal traffic.
  5. Explain expected gaps and flag differences that still need investigation.
  6. Compare periods using the same definitions, or explain what changed.

If a dashboard still disagrees, include the reason beside the number. If you do not know why, flag it as unresolved. That is more useful to the reader than a total you cannot explain.

Platform-by-platform guides

For a closer look at ad reporting, start with Google Ads and GA4, Meta and GA4, or LinkedIn Ads and GA4.

If the disputed number comes from sales, the HubSpot, Salesforce, and GoHighLevel guides follow the gap between web activity and CRM records.

For ecommerce, compare Shopify revenue with GA4 or work through Shopify, Meta, and Google Ads reconciliation.

Other journeys have their own boundaries. We cover Adobe Analytics and GA4, email and SMS clicks, and web and app measurement separately.

For differences in who gets counted, see the guides to customer and audience counts and ABM and web analytics.

To make the checks repeatable, use the monthly reporting workflow. If you would like help with a disputed report, start a 14-day trial to see how Maven’s tracking audit and daily health checks cover the tracking side of the gap. Want it done for you? MetricMaven can start with the number your team needs to explain.

Every guide in this series

Ad platforms vs GA4

CRM and revenue vs GA4

Other sources

When the gap is attribution

Frequently asked questions

Why do campaign performance numbers never match between platforms?

Campaign performance numbers diverge because platforms use different event definitions, attribution windows, time zones, filters, and deduplication rules.

Should I force every platform to match?

No. The goal is to reconcile differences, name the source of truth for each metric, and publish one accurate number the team reports.

What is the fastest way to reduce reconciliation hell?

Start by documenting attribution windows, date ranges, time zones, exclusions, and the owner for every KPI before the report is shared.

When should a team build a reporting layer?

Build a reporting layer when recurring reviews are spent reconciling the numbers instead of deciding what changed and why.

Sources and references

Jamie Isabel

Founder of MetricMaven. Previously managed Google Tag Manager and Google Analytics across 800+ sites at HCA Healthcare, and built attribution and eCommerce reporting at RYZE Superfoods and Mars.

Updated October 29, 2026

Start your 14-day trial

Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.

  • Free for 14 days, no credit card
  • Your first client workspace and portal
  • Every report template, ready to clone
Start a 14-day trial

Nothing is charged unless you subscribe.

Prefer a walkthrough? Book a demo on one of your own clients.