Analytics & Attribution

Campaign Reach Looks Healthy. Customer-Level Frequency May Reveal the Same People Saw Everything.

A customer-level reach report reconciling overlapping audiences across campaigns.

Updated: November 12, 2026

Google Ads API v26.2 expands unique reach metrics from campaign reporting to the customer resource and adds ad-format and network segmentation. The customer view can show deduplicated scale that campaign rows cannot provide when people see multiple campaigns. Do not sum campaign-level unique users and label the result customer reach. Query the customer resource for the account-level question.

Campaign totals are not a customer total

Google Ads API v26.2 expands unique reach metrics from campaign reporting to the customer resource and adds ad-format and network segmentation. The customer view can show deduplicated scale that campaign rows cannot provide when people see multiple campaigns.

Do not sum campaign-level unique users and label the result customer reach. Query the customer resource for the account-level question.

Frequency buckets describe cumulative exposure

The unique_users_two_plus through unique_users_ten_plus fields are N-plus thresholds, not mutually exclusive buckets. A person in ten-plus is also represented in every lower threshold.

Create exclusive bands only with clearly documented subtraction logic and only when states and availability make the calculation valid.

Operating control table

Control Evidence Failure prevented
Owner Named reviewer and decision Unclaimed change
Configuration Saved source state Cannot reproduce
Validation End-to-end fixture Partial success accepted
Threshold Success and rollback rule Result reinterpreted
Evidence Public or reporting read-back Configured mistaken for delivered

State metrics change the interpretation

Companion ReachMetricInfo fields indicate conditions such as privacy or quality suppression. A blank, unavailable or suppressed value is not automatically zero.

Carry the state alongside every reported number and block calculations that combine incompatible or nonreportable values.

Segment without manufacturing totals

Ad format, sub-format, network and sub-network segments can explain where frequency accumulates. Segment rows may overlap or obey platform-specific combination rules.

Validate totals against an unsegmented customer query and disclose when segmented rows cannot be reassembled into one deduplicated account total.

Turn exposure into a decision

Use customer-level frequency to identify saturation, uneven network delivery and creative wear, then compare those patterns with incremental outcomes or conversion quality.

Set review thresholds before looking at performance. High frequency is not automatically waste when the audience, purchase cycle and objective justify repeated exposure.

Connect the control to the wider system

Use this process alongside the reach metric suppression-state guide. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.

Pre-launch checklist

  1. Write the decision and owner in plain language.
  2. Capture the source configuration and evidence.
  3. Test one realistic customer or reporting path end to end.
  4. Verify mobile presentation, links and accessibility.
  5. Record the success threshold and rollback trigger.
  6. Schedule the next review before material spend accumulates.

Run a cross-functional release review

Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.

Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.

Set the review cadence before launch

Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.

At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.

Frequently asked questions

Should this be automated?

Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.

What evidence should be preserved?

Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.

When should the team roll back?

Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.

Sources

Published by Marketing That Clicks
Last reviewed November 12, 2026.