Skip to content
Attribution2 min read

Why GA4 and your ad report tell different stories.

Before treating a reporting gap as lost data, align the question: which event, which date, which conversion window, and which channels can receive credit?

TagVolt BlogOctober 4, 2026
Three colored glass paths converge into one clear channel.
In this article
  1. Write down the question
  2. Align the time and credit rules
  3. Separate collection from reporting
  4. Define an explained difference

Write down the question

Two dashboards can use the word conversion while answering different questions. One view may describe activity across the website. Another may describe actions credited to a particular advertising account. Comparing their totals without those definitions can turn a normal reporting difference into an unnecessary tracking incident.

Start the investigation with a plain sentence: we are comparing these completed purchases, for this period, under these reporting settings. Name the exact report and column. A screenshot of a headline number is useful context, but it is a weak specification for reconciliation.

Align the time and credit rules

Google's documentation lists timing, counting, attribution, and setup among the reasons reports can differ. Google Ads offers conversion-time columns that can help when comparing with systems organized around when the conversion happened. Analytics property and Ads account time zones can also differ.

Record the selected attribution model, eligible channels, and relevant windows. Give recent data time to settle before treating it as a final comparison. Avoid changing the configuration merely to make two totals look closer; first understand what each setting means for the business question.

Separate collection from reporting

Next, investigate a small set of known actions. Did the business system record them? Was the intended event generated? Did the correct destination receive it? This creates a concrete evidence trail that a broad percentage difference cannot provide.

If an event is absent from the collection path, work with the implementation owner. If the event arrived with the expected information, examine report definitions and eligibility. Keep these findings separate in the issue log so that a collection fix does not get confused with a change in attribution policy.

  • Choose one event and one stable comparison period.
  • Confirm the value definition and any exclusions.
  • Record time zones, columns, counting rules, and attribution settings.
  • Trace a few known actions before expanding the investigation.

Define an explained difference

The objective is an explained difference with a clear owner for unresolved gaps. Document which portion comes from known definitions and which portion still needs investigation. Review that explanation when the implementation or reporting configuration changes.

For an agency, this note is also useful client communication. It explains what can be compared directly, what needs qualification, and what action the team will take. Trust improves when the comparison is reproducible, even when the dashboards do not display identical numbers.

Further reading

More on attribution