Analytics & Attribution
The Reach Field Says Zero. The Data May Be Suppressed, Not Missing.

Updated: October 31, 2026
Check reach metric field presence and state metadata before interpreting a zero. Google Ads can leave a reach metric unset when privacy, quality or retention rules suppress it; reporting code that converts every unset value to zero can manufacture a false performance signal.
Why v26.1 changes reach reporting QA
Google Ads API v26.1 completed additional N-plus unique-user frequency buckets and added ReachMetricInfo state information for reach metrics. States can indicate complete data, privacy suppression, quality suppression, low quality or a date range beyond retention.
Google’s reporting guidance explains that suppressed or out-of-retention optional metrics can be unset and may evaluate to zero when code fails to check field presence. LOW_QUALITY is different because a numeric value can still be present with a warning state.
Interpret value and state together
| State | Numeric behavior | Reporting treatment |
|---|---|---|
| COMPLETE | Value present | Report normally |
| PRIVACY_SUPPRESSION | May be unset | Label unavailable; do not use zero |
| QUALITY_SUPPRESSION | May be unset | Label unavailable; investigate |
| LOW_QUALITY | Value may be present | Show with caution flag |
| DATE_RANGE_BEYOND_RETENTION | May be unset | Shorten range or mark unavailable |
Update the reporting pipeline
- Select the ReachMetricInfo message for each reach metric.
- Check optional-field presence before reading the number.
- Store the metric state beside the value.
- Map suppression to null, not numeric zero.
- Flag low-quality populated values.
- Test dates inside and outside retention.
- Update dashboards, alerts and historical comparisons.
Protect downstream calculations from invented zeros
A false zero can inflate frequency, trigger unnecessary creative rotation or imply that delivery collapsed. Null and zero are different business facts: zero means a measured absence, while null means the report cannot provide a trustworthy value.
Preserve the original state through the warehouse and BI layer. If the dashboard only receives a number, analysts cannot distinguish privacy suppression from low quality or retention limits.
Reach reporting controls
- Do not flatten null to zero.
- Store state and value together.
- Annotate privacy and quality suppression.
- Test API client serialization.
- Avoid comparing incompatible date ranges.
- Document metric retention limits.
Run a pre-launch decision review
Build one realistic test case from the first row of the framework above, then follow it from the initial marketing signal through the customer action and the reporting record. Ask the channel owner, creative lead, analyst and conversion owner to review the same case independently. Each reviewer should be able to identify what was promised, what evidence supports it, what the customer can control and what event proves the outcome.
Record disagreements before launch. A difference in naming may look minor in a meeting, but it can split reporting, obscure a product limitation or produce a landing experience that answers a different question. Resolve the definitions in the campaign brief and measurement plan, then repeat the test on mobile, where context and controls are easier to lose.
Use a release gate instead of a vague best practice
Approve the work only when the offer facts, interaction state, conversion rule and downstream record reconcile. If any reviewer needs an unstated assumption to explain the result, the system is not ready. Assign an owner and a repair date for every exception, and preserve a small control group or annotated baseline where possible. That turns the launch into a measurable operating decision rather than a one-time interpretation of platform guidance.
Connect the decision to the rest of the system
Apply the frequency framework from MTC’s repeated-reach analysis. The purpose of the link is operational: the upstream promise, measurement rule and downstream experience must describe the same outcome.
Document the learning, not just the result
Version the query, client library, field-presence logic, state mapping and dashboard behavior. Include test cases for every supported state so future refactors do not reintroduce the zero-default bug.
When suppression rates change, investigate date range, audience size, segmentation and privacy thresholds before blaming campaign delivery.
Frequently asked questions
Does an unset reach field mean zero users?
No. It can mean the metric was suppressed or falls outside retention.
Can LOW_QUALITY still have a value?
Yes. The state can flag a populated metric as low quality.
How should a dashboard display suppression?
Use an unavailable or suppressed label with the state reason, not a zero bar or zero KPI.
