PMax product reporting across all networks
Google has significantly expanded product-level reporting for Performance Max campaigns. Since June 15, metrics no longer flow into product reports only from the Search network and Standard Shopping campaigns, but from all eligible networks. For advertisers, that means a more complete view of product performance—and at the same time a one-time distortion of the numbers, because impressions, clicks, costs, and conversions can suddenly appear higher without any real change in campaign performance.
Performance Max bundles automation across Search, Display, YouTube, Discover, Gmail, and Shopping. That breadth made previous product reporting incomplete: many relevant placements outside Search were missing from product-specific metrics. Anyone looking only at cost and conversions at the product level mainly saw Search and Shopping shares and underestimated the role of Video, Apps, and Demand Gen. The new measurement closes that gap and provides a more consistent data foundation across Google's inventory.
What changes in reporting in practice
According to the update, product reports now include performance data across all Performance Max networks and, where applicable, across Video campaigns, App campaigns, and Demand Gen campaigns—the latter especially through Google Merchant Center. Previously, metrics such as cost and conversions largely reflected only products served on Search networks or in Standard Shopping campaigns. The expanded scope therefore affects not only presentation, but the measurement framework itself.
For many accounts, this leads to a one-time jump in key metrics. Impressions and clicks can rise because previously invisible network shares are now counted. Cost and conversion values can also shift once product-level attribution includes additional inventory surfaces. Anyone reading month-over-month comparisons without context risks false conclusions: an apparent performance gain may simply be the result of broader reporting.
- All Performance Max networks now feed into product metrics.
- Video, App, and Demand Gen data can become visible as well.
- Earlier reports mainly covered Search and Standard Shopping.
- Historical comparisons before and after the cutover date are only partly comparable.
Why the change matters for marketers
Online marketing teams steer budgets, bids, and product feeds in an increasingly data-driven way. When reporting boundaries shift, not only the dashboard optics change, but also the decision basis. A sudden rise in impressions or conversions can push stakeholders into premature budget increases. Conversely, teams that recognize the rise as an artifact can communicate calmly and avoid misinvestment.
The expansion addresses a long-standing limitation: product performance across Google's inventory was hard to assess holistically. At the same time, analysis becomes more complex. Time series, benchmarks, and automations that rely on stable definitions must be recalibrated. Especially critical are alerts that trigger budget rules on deviations, and client reports that present absolute monthly values without noting measurement changes.
Practical steps for evaluation
Google Ads specialist Bia Camargo highlighted Google's notice and warned advertisers not to confuse reporting jumps with real performance gains. In practice, a clear analysis process helps: first mark the June 15 cutover in all dashboards and comments. Then use network filters to separate where activity comes from. The Network (with search partners) filter helps distinguish Search shares from other surfaces and explain the new data breadth.
In addition, month-over-month and year-over-year comparisons should include a footnote. Anyone tracking product ROAS, cost per conversion, or impression share at product level should reset baselines after the update. For agencies, a short client note is worthwhile: metrics look stronger because more inventory is measured—not necessarily because the campaign converts better.
| Aspect | Before the update | After the update |
|---|---|---|
| Product metrics | Mostly Search and Standard Shopping | All eligible PMax networks and additional campaign types |
| Visibility | Incomplete product performance | Broader view across Google inventory |
| Metric jumps | Limited comparability with non-Search | One-time increase possible despite stable performance |
| Analysis focus | Restricted network view | Network filters and context in reports required |
Measurement, attribution, and stakeholder communication
Expanded product measurement improves transparency but does not replace incremental success checks. Anyone steering Performance Max strategically should combine product reports with network breakdowns, conversion paths, and Merchant Center data. That shows whether a product truly scales across additional surfaces or whether previously invisible impressions have simply become visible. This distinction is especially critical for feed optimization, negative lists, and creative tests.
Collaboration between SEA, analytics, and e-commerce also benefits from clear definitions. Teams should document which metrics are comparable before and after the cutover and which must be recalibrated. In Looker Studio dashboards and BI exports, segmenting by reporting period helps prevent automations from storing false trends. Anyone who tied KPI targets to absolute impressions or costs should adjust target ranges in the short term.
- Mark the cutover date and measurement change in all stakeholder reports.
- Use network filters to separate Search and non-Search shares.
- Reset baselines for product ROAS and conversions after the update.
- Prepare clients and internal teams early for apparent performance jumps.
- Reconcile product reports with Merchant Center and attribution data.
Bottom line: expanded Performance Max product reporting provides a more complete overview of product performance in the Google Ads ecosystem. The benefit only materializes when marketers interpret the numbers as a measurement change rather than automatic campaign progress. Teams that consistently use filters, context, and new baselines can make better product decisions—and avoid putting budget behind apparent jumps that come solely from broader reporting.
