Google changed how its advertising systems count reach when several people watch YouTube together on a connected TV. From 2 June 2026, the Google Ads API uses a “Total Co-view” definition aligned with the Google Ads interface and Editor.
No API version migration or code change is required. The risk is analytical: a dashboard can show a shift even when campaign delivery and implementation remain unchanged.
What Total Co-view means
Traditional device-based counting can treat a television screen as one viewer. Total Co-view includes the individuals estimated to be watching an ad together on that connected-TV device.
Google says the update aligns its reach reporting with offline media and third-party measurement standards. It changes the population represented by reach metrics; it does not mean that Google received a separate click or conversion from every co-viewer.
Which Google Ads API metrics are affected
Google's developer announcement identifies six campaign-level fields:
| API metric | Reporting meaning |
|---|---|
metrics.unique_users |
Estimated people reached. |
metrics.average_impression_frequency_per_user |
Average impressions per estimated person. |
metrics.unique_users_two_plus |
People reached at least twice. |
metrics.unique_users_three_plus |
People reached at least three times. |
metrics.unique_users_four_plus |
People reached at least four times. |
metrics.unique_users_five_plus and metrics.unique_users_ten_plus |
Higher-frequency reach thresholds. |
The field names and API calls remain the same. Their values can move because the measurement definition changed for dates from the launch onward.
Why period comparisons can become misleading
Suppose a report compares June with May and shows higher unique reach or a different average frequency. Part of that movement may come from the Total Co-view definition rather than a budget, targeting or creative change.
This is a classic measurement-boundary problem. A calculation can be technically correct while the interpretation is wrong because the periods do not use a fully comparable definition.
Reporting changes to make
Update the measurement layer even though no campaign or API code needs to change:
- Add a visible annotation for 2 June 2026 in dashboards and recurring reports.
- Document the definition beside reach and frequency metrics.
- Avoid presenting a May-to-June movement as pure campaign growth without qualification.
- Segment connected-TV delivery when investigating unexpected changes.
- Keep conversion, cost and business outcomes beside reach metrics.
- Tell clients or stakeholders when a KPI trend crosses the methodology date.
For automated reporting, add the annotation in the semantic or presentation layer rather than altering source values. Our conversion tracking guidance covers the broader measurement framework, and the Google Ads resource connects reporting to campaign management.
What advertisers should not infer
More reported people reached does not automatically mean more customers, stronger attention or better campaign efficiency. Total Co-view estimates audience size in a shared-screen context. It should be read with completed views, site activity, qualified conversions and cost.
Frequency also needs care. A lower average after the change may reflect a larger estimated audience denominator. It does not prove that ad repetition dropped for every household or viewer.
The bottom line
Total Co-view makes connected-TV reach reporting more people-oriented, but it introduces a break in trend interpretation. The implementation response is simple: preserve the source data, annotate the methodology change, review connected-TV mix and avoid attributing every movement after 2 June to campaign performance.