Two revenue numbers. One much better conversation.

First, name what you are comparing

A dashboard says one thing. A network export says another. Before calling either number wrong, ask each report the same questions: what is counted, over which interval, for which app, in which currency, and from which source?

An event observed by an SDK and revenue reported by a network describe different parts of the system. In TionAds, those perspectives stay separate. That gives a team a place to investigate differences instead of treating a combined figure as an explanation.

Estimated also does not mean finalized. Google says that AdMob’s performance estimates can differ from finalized earnings after adjustments, including invalid-activity deductions. Its finalized amounts appear in the payments and transaction history. That is a specific AdMob distinction; check the equivalent definitions for each other network you use.

Make a small comparison contract

Our suggested workflow starts with a single app and a closed reporting window. Write the comparison settings beside the result so that a teammate can reproduce it without asking which filters were active.

Do not treat a missing import as zero revenue. Give it a missing-data label in your working notes, find the last successful import, and repeat the comparison once the data is available. Zero is a measurement; missing is a state.

• ↗Match the app, ad format and network identifiers.
• ↗Use the same date boundaries and confirm the reporting time zone.
• ↗Record the currency and any conversion method.
• ↗Note the import time and whether each amount is estimated or finalized.

Turn the difference into a next step

Split a broad discrepancy into smaller comparisons. Is it concentrated in one network, one day or one app version? A narrow difference gives the team a concrete place to inspect. Keep a short record of the finding, the owner and the next check.

For illustration, suppose two matched reports show $100 and $96. The absolute difference is $4; relative to the first report it is 4%. Those are example values, not platform performance. Stating the denominator matters: a percentage without a reference point can create a second disagreement.

The goal of reconciliation is a repeatable explanation. Some differences will have a clear cause, some will need more data, and some will remain unresolved. Preserve that uncertainty alongside the number so the next person can continue the investigation.