5 min read
How to Reconcile Conversion Numbers Across Ad Platforms With Payment Revenue
Reconciliation does not mean forcing every dashboard to show the same number. It means defining one financial truth, preserving each platform's attribution view, and explaining the difference with consistent windows and identifiers.
· Grometrics Team
Google, Meta, Apple, and other advertising platforms can all claim conversions from the same customer. Adding their reported totals together can produce more conversions than your payment provider recorded.
Reconciliation does not mean forcing every dashboard to show the same number. It means defining one financial truth, preserving each platform's attribution view, and explaining the difference with consistent windows and identifiers.
Choose the financial source of truth
Use the payment provider or subscription system for collected revenue, refunds, renewals, and disputes. Advertising platforms are not the accounting ledger.
Normalize transaction currency and status before comparing campaigns. Decide whether the report uses gross revenue, net revenue, or both. Do not mix authorized payments with settled payments without labeling the difference.
- Verified transaction identifier.
- Customer identifier.
- Payment time and currency.
- Gross amount.
- Refunded or disputed amount.
- Net amount.
Inventory every conversion sender
Before comparing dashboards, list every client, server, integration, and provider that can send a conversion. A browser pixel, server endpoint, mobile SDK, subscription platform, and automation tool may all report the same purchase through different paths.
For each sender, record the event meaning, destination, identifier, value source, and duplicate rule. Disable an unnecessary path or coordinate deduplication when two paths intentionally remain. This inventory often explains inflated totals before any attribution model is examined.
- Browser analytics and pixels.
- Server side conversion endpoints.
- Mobile advertising SDKs.
- Payment and subscription integrations.
- Automation or customer data tools.
- Manual conversion uploads.
Preserve every platform view
Keep each platform's reported conversions, value, attribution window, and model in separate columns. Those values describe how the platform credits itself under its own rules.
Do not overwrite payment attribution with the platform number. Also do not discard platform data. It remains useful for bidding diagnostics and for understanding why its dashboard differs from your revenue view.
- Platform reported conversions.
- Platform reported value.
- Spend.
- Attribution window and model.
- Payment backed customers and revenue.
Normalize time before comparing
Platforms can report by click date, impression date, conversion date, or account timezone. Payment systems record event timestamps and settlement events. A day boundary can move the same customer into different reporting periods.
Select one business timezone and one financial date definition. Preserve original timestamps for audit, then derive the comparison period consistently.
- Account timezone for each platform.
- Click or impression date basis.
- Conversion date basis.
- Payment event date.
- Reporting period and late event policy.
Deduplicate customers without inventing precision
Use permitted click identifiers, first party attribution identifiers, and customer references to connect known journeys. One customer can legitimately appear in several platform attribution reports.
Your own model should apply one documented rule for budget decisions, such as first known source or a clearly defined multi touch method. Keep an unattributed group for payments that lack enough evidence.
- Stable customer or visitor identity.
- Original acquisition context.
- Recent source context when needed.
- Payment reference.
- Attribution confidence and missing reason.
Build the reconciliation table
Create one row per platform, campaign, and reporting period. Show spend, platform conversions, platform value, payment backed customers, gross revenue, refunds, net revenue, and unattributed share.
Add diagnostic differences rather than one unexplained variance. Common classes include overlapping platform credit, time window mismatch, duplicate event delivery, modeled conversions, failed identity joins, and refunds.
- Overlapping provider attribution.
- Different reporting windows.
- Duplicate browser and server events.
- Modeled or aggregated results.
- Missing click or customer identity.
- Refunds and delayed renewals.
Agreement is not the goal: A useful reconciliation explains why the numbers differ and identifies which number answers each business question.
Set the decision rule before reading the winner
Choose how the business report assigns known revenue before ranking campaigns. First known source is easy to explain. A documented multi touch model can support longer journeys. Provider attributed value can remain a separate optimization view.
Apply the rule consistently across every platform. Do not choose first touch for one network and provider reported value for another because the result looks better. Record the confidence and the share of revenue that the rule could not assign.
- One attribution rule across platforms.
- One net revenue definition.
- One reporting timezone.
- One customer acquisition denominator.
- Visible unattributed revenue and confidence.
Use net revenue for budget decisions
Spend decisions should use a stable attribution rule and payment backed net revenue. Provider reports can still guide optimization inside each network, but they should not be added together as if each claimed a unique customer.
Grometrics platform comparison explains the reporting choices, while Grometrics campaign reporting combines spend with real attributed revenue for a consistent decision view.
Sources
READY TO SEE YOUR REAL NUMBERS?
Connect your payment provider and see which channels actually drive revenue.
Start tracking for free →See the full page:
Platform comparisonRELATED POSTS