Check the scope first
Google distinguishes user-, session- and event-scoped traffic dimensions. The reporting attribution choice affects event-scoped credit; it does not simply rewrite every user- or session-scoped acquisition dimension. A label saying GA4 is therefore insufficient to describe a query.
Write down the actual dimension and metric used in each report. A channel-session table and an event-attribution table may both be correct while answering different questions. Compare like with like before looking for a tracking failure.
Create a short comparison contract
Use the same closed period, timezone and currency. Specify the purchase event, included accounts, exclusions and whether revenue includes tax, shipping, discounts, cancellations and returns. Record the conversion timestamp basis and the relevant attribution windows.
Some systems may still observe different interactions after these choices are aligned. Document the difference rather than forcing agreement. A reconciliation is useful when it explains the numbers, not when it merely makes the totals match.
Investigate before changing the budget
Check tagging, channel mapping, missing events and data freshness. Follow a small set of suitable transactions or source records where permitted. Distinguish a known definitional difference from an unexplained gap.
Keep native platform reporting visible for the decisions it supports, while naming the reference used for cross-channel discussion. Do not add multiple platforms’ assigned revenue and label the total as business revenue.
The same reporting label, different questions
A team sees a low paid-social figure in a session report and a higher value in an ad platform. Its first task is to inspect period, mapping, conversion event and attribution scope. The discrepancy itself is not enough evidence to conclude that the campaign is unprofitable.
Turn the guide into a useful review
- Record dimension, metric and reporting scope.
- Align period, currency and revenue definition.
- Check tagging, freshness and source coverage.
- Label the remaining gap as explained or still under investigation.
Reference material
Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.
Bring the question.
Keep the context.
Map the relevant sources and specialist workflow for your team.
Explore your stack