GA4 Search Ads 360 Reports: Check the Population and Scope

By Dave TanguayPublished Updated Editorial draft

Quick Answer

Before comparing a GA4 Search Ads 360 report with another report, identify the report, included population, dimension scope and date range. The documented acquisition detail report is session-scoped and limited to attributed SA360 sessions. It is not an interchangeable view of every visit, first acquisition or campaign-performance measure.

Two tables can display the same campaign name while answering different questions. A difference in totals can be a reason to inspect their definitions before treating it as lost data or a broken integration.

Identify the actual report

Google’s Search Ads 360 report guide distinguishes its acquisition detail report from the Search Ads 360 performance report in Advertising. It describes access through a successfully linked advertiser or sub-manager. It also says historical report access can remain after unlinking, so an old table does not prove a current link is active.

Save the exact report title, property, selected dates and any filters. A bookmarked URL or abbreviated dashboard heading may conceal which view someone is using.

Check the included sessions

The acquisition guide says the report includes SA360-attributed sessions, excludes records with an empty or not-set Session SA360 advertiser ID and uses its documented session attribution. Changing the property’s Attribution Settings does not change that report’s attribution model.

Those boundaries matter before comparing its total with a sitewide report. A report limited to one integration should not be expected to include every session from other sources.

Keep scope beside the business question

Google’s traffic-source scope guide distinguishes First user dimensions, Session dimensions and event-scoped source dimensions. They describe initial acquisition, session acquisition and attribution credit for key events respectively.

Question Definition to check
Where were users initially acquired? The actual First user dimension and its eligible user population.
What acquired these sessions? The Session dimension, including any integration-specific restriction.
Which source receives key-event credit? The event-scoped dimension and applicable attribution settings.
How did the campaign perform? The specific performance report, metrics and included campaign data.

The similar names do not make the rows interchangeable. Do not remove the Session or First user prefix from a report label if that makes the evidence ambiguous.

Write a comparison that preserves the difference

In an illustrative review, one analyst supplies an SA360 acquisition table and another supplies a first-user acquisition table. Before comparing totals, record their exact dimensions, population, period and filters. Describe the different questions they answer instead of subtracting one total and labeling the remainder missing visits.

If the business needs a matched comparison, have the authorized analyst select compatible report definitions and document remaining limitations. This example is a proposed review, not an inspection of a linked account or proof that a particular integration works.

Our analytics work-plan guide explains how to turn a defined uncertainty into an investigation. The campaign-link guide addresses a separate manual labeling task. Neither replaces the SA360 report’s actual inclusion rules.

Key Takeaways

  • Identify acquisition detail and performance reports separately.
  • Save population rules and dimension scope with the result.
  • Reconcile definitions before diagnosing a difference as missing data.

Frequently Asked Questions

Does historical SA360 data prove the current link is active?

No. Google documents continued historical report access after unlinking. Verify the actual current integration separately.

Should first-user and session totals always match?

No. They describe different acquisition scopes. Confirm the question, included records and metrics before comparing them.

Archives