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.

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.
| Comparison | Usually higher | Main reason | Guide |
|---|---|---|---|
| Meta Ads vs GA4 | Meta Ads | Meta can credit views with no click and credits only Meta ads; GA4 cannot see impressions | Meta vs GA4 |
| Google Ads vs GA4 | Google Ads, for its own campaigns | Google Ads credits only its own clicks; GA4 shares credit with organic, email and direct | Google Ads vs GA4 |
| LinkedIn Ads vs GA4 | LinkedIn Ads | View-through conversions, and Lead Gen Form leads that never reach your site | LinkedIn vs GA4 |
| Shopify vs GA4 revenue | Shopify | Shopify counts every order in its backend; GA4 counts only purchase events it receives | Shopify vs GA4 |
| Email or SMS clicks vs GA4 sessions | Platform clicks | Security scanners click links, and a session needs the page and the GA4 tag to load | Email and SMS vs GA4 |
| CRM customers vs customer-list audiences | CRM | An audience only includes people the ad platform can match to an account | Customer and audience counts |
| HubSpot, Salesforce or GoHighLevel vs GA4 | Neither: they count different things | GA4 counts events and sessions; the CRM counts contacts, leads and deals | HubSpot vs GA4 |
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.

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.
- Name the event or record being counted and the source that owns it.
- State the attribution window and model where they apply.
- Confirm the reporting period and time zone.
- Document duplicate handling and exclusions for tests, spam, and internal traffic.
- Explain expected gaps and flag differences that still need investigation.
- 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
- Why Google Ads and GA4 conversions don’t match
Google Ads and GA4 count conversions on different dates, models, windows, and tags. Here is how to find the gap and reconcile the two before the next review.
- Why Meta Ads and GA4 numbers don’t match
Meta and GA4 disagree on conversions because of view-through credit, attribution windows, cross-device identity, and missing UTMs. Here is how to reconcile them.
- Why LinkedIn Ads and GA4 numbers don’t match
LinkedIn Ads and GA4 count different clicks, views, and people, so their numbers will not match. Here is how to explain the gap before the next report review.
CRM and revenue vs GA4
- Why HubSpot and GA4 numbers don’t match
HubSpot and GA4 disagree because they count different events, people, windows, and lifecycle states. Here is how to reconcile them before the next report review.
- Why Salesforce and GA4 numbers don’t match
Salesforce counts leads, contacts, and opportunities while GA4 counts website events and sessions. Here is why the two disagree and how to report on both without guessing.
- Why GoHighLevel and GA4 numbers don’t match
GoHighLevel counts contacts, pipeline, and won deals while GA4 counts web events and sessions. Here is how to reconcile the gap before the next report review.
- Why Shopify and GA4 revenue doesn’t match
Shopify records every order on the backend while GA4 only sees purchases the browser reports. Here is how to reconcile orders and revenue before the next review.
- Ecommerce metric reconciliation: Shopify vs Meta vs Google Ads vs GA4
Shopify, Meta, Google Ads, and GA4 each count sales on their own dates and credit rules. Here is the system of record for each metric and the weekly ratios that keep them honest.
Other sources
- Why Adobe Analytics and GA4 numbers don’t match
Adobe Analytics and GA4 use different units, visitor identities, timeouts, and attribution rules. Here is how to reconcile them during a migration or parallel run.
- Why email and SMS clicks don’t match GA4 sessions
An email or SMS click and a GA4 session are different records. Scanners, redirects, UTM gaps, in-app browsers, and consent all change the count. Here is how to reconcile them.
- Why web and mobile app analytics numbers don’t match
Web and app analytics disagree because they come from separate streams, identify people differently, and count installs, sessions, and attribution on different rules. Here is how to reconcile them before the next report review.
- Why customer and audience counts don’t match across your CRM and ad platforms
Customer and audience counts differ because each tool counts something different. Stop forcing them equal, name the CRM as the source of truth, and track match rate as a health metric.
- Why ABM platform reports and web analytics don’t match
ABM platforms report accounts, GA4 reports people and events, and the CRM owns pipeline. Here is how to reconcile them before the next report review.
- Dynamic UTM parameters: a generator, plus tracking template vs. Final URL suffix
Build a platform-ready dynamic UTM template, learn how to test supported macros, and see why Maven uses utm_mc_id to audit paid-media attribution coverage.
When the gap is attribution
- Offline conversions: what they are, how to measure them, and what changed in 2026
When a deal closes on a sales call or in your CRM, your ad platforms never see it. This guide explains offline conversion tracking from the ground up: what to capture when a lead arrives, how to send the outcome to Google Ads, Meta, Microsoft, LinkedIn and TikTok, how the credit works, and what changed in 2026.
- GA4 multi-touch attribution without BigQuery: what the built-in reports can and can’t do
GA4’s built-in views cover model comparison, conversion paths, and lookback windows. Here is what they answer well, where they stop, and when the raw export becomes necessary.
- GA4 multi-touch attribution in BigQuery: build a custom attribution model in SQL
Turn the GA4 export into sessions, find each conversion, join the sessions in a lookback window before it and assign credit with window functions. The SQL below builds position-based and time-decay models and a channel rollup. It will not match GA4’s data-driven model, which the export does not include.
- HubSpot multi-touch attribution: native reports vs. a warehouse model
HubSpot’s built-in attribution reports are a useful start. Here is what they measure, where they stop, and how to rebuild the same questions in BigQuery.
- Salesforce multi-touch attribution: Campaign Influence vs. a warehouse model
Campaign Influence credits revenue to campaigns through campaign members and contact roles. Here is where the native models stop, and how to build an auditable model in the warehouse.
- Multi-touch attribution and models explained
Multi-touch attribution (MTA) shares credit for a conversion across the interactions your systems recorded before it, and an attribution model is the rule that decides how.
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.
