Google Ads, Meta Ads, and GA4 can report different conversion totals without any system being broken. This guide provides a repeatable PPC attribution reconciliation workflow: define the conversion being measured, align date and attribution settings, compare click-through and view-through rules, calculate the gap, and document which metric should guide budget and bid decisions.
Overview
Paid media attribution differences usually come from measurement design rather than arithmetic. Each platform may answer a different question. An advertising platform might report conversions it attributes to an ad interaction within its selected window. GA4 may report sessions, key events, or attributed conversions using its own reporting identity and attribution model. Your internal system may count completed orders, approved leads, or deduplicated customers after additional validation.
Before comparing totals, write down the conversion definition. “Purchase,” “lead,” and “signup” should refer to the same business event in every report. Also distinguish between:
- Event count: how many times a tracked event occurred.
- Unique conversions: how many people, orders, or leads were counted after deduplication.
- Attributed conversions: conversions assigned to a channel, campaign, ad, or interaction.
- Value: the revenue or estimated value attached to those conversions.
A platform total is therefore not automatically the “true” total. The useful question is whether each number is internally consistent, clearly defined, and appropriate for the decision being made. Use platform reporting for platform-level campaign optimization, a consistent analytics view for cross-channel comparisons, and validated business outcomes for financial decisions.
For a broader monthly reporting structure, pair this reconciliation process with a cross-channel paid media reporting template. Attribution notes belong beside the performance figures, not in a separate document that stakeholders cannot connect to the data.
How to estimate
Use a simple reconciliation worksheet for each reporting period. The goal is not to force every source to match. It is to identify the reason for each material difference and decide which consistently defined number belongs in each decision.
1. Establish the comparison scope
Select one date range, one conversion event, one currency, and one reporting level. For example, compare completed purchases for a calendar month at the campaign level. Do not compare a platform’s campaign conversions with GA4’s total paid traffic unless the scope is intentionally different.
2. Record the measurement settings
Capture the settings that can change the result before exporting data. These include attribution model, click-through window, view-through window, reporting time zone, conversion counting method, conversion status, modeled or observed measurement, and whether the report uses event date or conversion date. Take a screenshot or save the export configuration when possible.
3. Calculate the gap
For two sources, use:
Absolute gap = Source A conversions − Source B conversions
Gap percentage = Absolute gap ÷ Source B conversions × 100
Choose one source as the comparison baseline and keep that choice consistent. If the baseline is zero, report the absolute difference instead of a percentage. For value reconciliation, repeat the calculation with attributed revenue, while noting whether revenue is gross, net, estimated, or imported from another system.
4. Classify the explanation
Assign each discrepancy to a category: definition, scope, attribution window, time zone, duplicate handling, tracking loss, modeled measurement, reporting delay, or data-quality issue. This turns “the numbers do not match” into a documented finding that can be reviewed next month.
| Comparison field | Google Ads | Meta Ads | GA4 |
|---|---|---|---|
| Primary question | Which eligible ad interactions received credit? | Which eligible paid social interactions received credit? | How were tracked events attributed within the analytics property? |
| Click-through window | Use the selected conversion action setting | Use the selected attribution setting | Use the configured attribution and reporting settings |
| View-through window | May be reported separately or included according to conversion settings | May include eligible ad impressions according to selected settings | Often depends on available identifiers and observed journeys |
| Time zone | Account or report configuration | Ad account or report configuration | Property and report configuration |
| Modeled measurement | May affect some reported results | May affect some reported results | May affect modeled or estimated attribution outputs |
| Common comparison risk | Comparing ad-attributed conversions with all analytics conversions | Treating view-through and click-through credit as equivalent | Comparing sessions or key events with platform conversion actions |
The table is a reconciliation framework, not a list of universal defaults. Platform interfaces and measurement models change, so verify the active settings in each account before using the comparison. Record the exact labels shown in the export rather than relying on memory.
Inputs and assumptions
A useful worksheet should contain enough context for another person to reproduce the comparison. Include these fields:
- Reporting period: start date, end date, and whether dates represent interaction date or conversion date.
- Conversion definition: event name, business meaning, counting method, and validation rule.
- Source and scope: account, property, campaign grouping, country, device, and channel filters.
- Attribution rules: model, click-through window, view-through window, and engaged-view treatment where relevant.
- Time zone: the time zone applied by every report.
- Data status: whether results are final, still processing, modeled, imported, or subject to later adjustment.
- Identifiers and deduplication: transaction ID, order ID, lead ID, or another method used to prevent double counting.
- Cost and value inputs: spend, conversion value, refunds, margin assumptions, and currency conversion rules if used for ROAS optimization.
Keep the assumptions separate from the results. For example, “Meta Ads includes view-through credit” is an assumption until confirmed in the selected report. “GA4 shows 84 key events” is an observation. Mixing the two makes later audits difficult.
Privacy-related measurement limitations can reduce the ability to connect an ad interaction with a later conversion. Missing consent signals, browser restrictions, blocked tags, incomplete user identifiers, and offline conversion delays may all affect observability. Treat an unobserved journey as a measurement limitation, not proof that no marketing influence occurred. At the same time, do not use modeled or platform-attributed results as a substitute for validated business outcomes without stating that limitation.
Tracking hygiene matters before attribution analysis. Review campaign naming and parameters with a UTM tracking and attribution audit guide, then check whether landing-page tags, redirects, forms, and transaction IDs preserve the necessary information.
Worked examples
Example 1: Different totals caused by attribution scope
Suppose a monthly export shows 120 Google Ads conversions, 95 Meta Ads conversions, and 178 GA4 key events for the same general period. These figures should not be added together. First, confirm whether all three represent the same event. Next, separate the channel totals from the analytics total. GA4 may assign a single event to one channel under its model, while each advertising platform may claim eligible conversions under its own rules. The platform totals can therefore overlap even when GA4 presents a deduplicated journey.
If Google Ads is the baseline for a search campaign review, the comparison to GA4 is:
Absolute gap = 120 − 178 = −58 conversions
Gap percentage = −58 ÷ 178 × 100, or approximately −32.6%
The calculation describes the size of the difference, not its cause. The worksheet should then record whether the difference came from conversion definitions, windows, time zones, missing tags, imported conversions, or deduplication.
Example 2: Choosing a metric for a bid decision
Assume a campaign has reliable spend data and a verified purchase event, but the platform reports more attributed purchases than the analytics property. For bid strategy review, use the platform’s conversion metric only if the conversion action is correctly configured, the counting method matches the business objective, and the attribution setting is stable across the comparison period. For cross-channel budget allocation, use one consistently defined analytics or finance-validated metric across all channels. Report both where useful, but label them clearly rather than blending them into a single total.
This approach prevents a common error: changing bids because one platform total moved, when the underlying difference actually came from a revised reporting window or a tracking problem. Before changing target CPA or target ROAS, check the reconciliation notes and the conversion tracking status.
When to recalculate
Run the workflow monthly, at quarter-end, and before major budget or bid changes. Recalculate sooner when a platform changes its attribution terminology, conversion settings, reporting interface, modeled measurement approach, or default report configuration. Also repeat it after a tag deployment, consent implementation, checkout change, CRM import, domain migration, or campaign restructuring.
Use this action checklist:
- Export the same conversion event and date range from Google Ads, Meta Ads, GA4, and the internal source used for financial validation.
- Save the report settings, including time zone, attribution model, windows, filters, and counting method.
- Match campaign names, UTMs, transaction IDs, and conversion definitions before comparing totals.
- Calculate absolute and percentage gaps, then classify each material discrepancy.
- Mark each explanation as confirmed, likely, or unresolved.
- Choose the metric for each decision: platform optimization, cross-channel allocation, or finance reporting.
- Assign an owner and due date for unresolved tracking or data-quality issues.
Keep the completed worksheet with the monthly PPC budget pacing review and update it whenever inputs or measurement settings change. A consistent reconciliation record makes attribution differences easier to explain, reduces reactive campaign optimization, and gives stakeholders a defensible basis for deciding where the next dollar of paid media budget should go.