SEM Reporting Software Needs a June 15 Product Baseline

Google's April 30, 2026 product-reporting update will make Performance Max product totals more complete on June 15. If your reporting stack does not split pre-change and post-change baselines, trend charts can mislead budget and search-term decisions.

What This Means: The Practical Takeaway

Google's April 30 developer update is good news for product-level reporting, but it also creates a charting trap. On June 15, 2026, Performance Max product reporting becomes more complete because all networks will begin appearing in `shopping_performance_view`, and more campaign types will expose cost and conversion metrics through `shopping_product`. If your SEM reporting stack compares pre-June 15 and post-June 15 rows as if nothing changed, it can turn a reporting expansion into a fake performance win.

The risky version of this story is ordinary.

A dashboard shows a product-level lift, a team assumes Performance Max got better, and budget shifts start before anyone checks whether the reporting surface changed first.

Google's June 15 Change Creates A Comparison Problem

Google said that starting June 15, product reporting in the Google Ads API will expand in three ways: more campaign types will get cost and conversion metrics, `shopping_performance_view` will return results consistently across Merchant Center-backed campaign types, and all Performance Max networks will begin appearing in product reporting.

That is useful data.

It is not automatically comparable data.

Google also says historical requests for dates before June 15 will not contain the expanded fields. That means a clean month-over-month chart can quietly compare two different reporting definitions without telling the operator.

Why Performance Max Product Totals Can Jump Without A Real Performance Shift

Teams often treat product reports as stable operating dashboards.

They compare week over week, month over month, and product line against product line. That works only when the underlying report means the same thing across both periods. After June 15, some product-level totals will widen because the report is seeing more of Performance Max, not necessarily because the campaign became more efficient.

The first mistake will be calling the jump optimization progress.

The second mistake will be letting that narrative move budget faster than the evidence deserves.

Good [SEM reporting software](/articles/sem-reporting-software) Should Force A Baseline Split

The better reporting standard is not only `show me more data`.

It is `show me when the data changed shape`.

A serious reporting tool should annotate June 15, split pre-change and post-change product trends, and make it hard to blend those periods inside one clean-looking chart. It should also let the operator compare the richer product totals against channel context from the Performance Max channel report so a wider product row does not get mistaken for cleaner demand.

If the software cannot separate structural reporting change from actual performance change, the prettier dashboard becomes less trustworthy.

Where This Leaks Into Search-Term And Product Decisions

Product reporting is not isolated from search-term optimization.

If a team uses product performance to decide which product groups deserve broader coverage, which campaigns deserve more budget, or which weak query themes should stay alive a little longer, a reporting artifact can leak into search decisions. More complete Performance Max product data may be helpful, but it should not be used to justify looser query governance until operators know the lift is real.

That matters most when Search, Shopping, Display, YouTube, and other inventory are blended under the same campaign story.

The Review Rules Worth Setting Before June 15

Before the reporting expansion lands, set four rules.

1. Mark June 15 in every affected product dashboard. 2. Compare affected campaign types in separate pre-change and post-change windows. 3. Require a note explaining whether a product lift came from better demand, broader network visibility, or both. 4. Hold budget or governance changes when the only new evidence is a reporting-definition change.

Those rules do not slow the team down much. They stop charts from becoming explanations they did not earn.

The Better Standard

Google is giving operators a more complete product view. That is a real upgrade.

The stronger response is not to trust the chart more because it got richer. It is to demand cleaner baseline discipline now that the chart can change meaning on a known date. The best SEM reporting software will not only expose more product-level detail. It will show exactly when the reporting surface changed, preserve honest comparisons, and keep product, budget, and search-term decisions tied to comparable evidence.

How To Do It

Copy this prompt into ChatGPT or Claude:

```text You are a senior SEM reporting architect. Help me build a June 15 reporting-baseline workflow for Google Ads product and Performance Max reporting. I have API-driven product reports, shopping_performance_view extracts, channel performance reports, campaign budgets, search-term summaries, and weekly stakeholder dashboards. Give me a practical process for separating pre-change and post-change periods, annotating charts, spotting false lifts caused by broader network coverage, deciding which product or search-term decisions must wait for comparable data, and creating a short QA checklist before budget or governance changes are approved. ```

Sources

- [Google Ads Developer Blog: Product reporting changes for Google Ads starting June 15, 2026](https://ads-developers.googleblog.com/2026/04/product-reporting-changes-for-google.html?m=0)

- [Google Ads Help: About the channel performance report for Performance Max](https://support.google.com/google-ads/answer/16260130?hl=en)

- [Google for Developers: Retail campaign performance](https://developers.google.com/google-ads/api/performance-max/retail-reporting)

- [PPC Land: Google Ads API to expand product reporting for all campaign types on June 15](https://ppc.land/google-ads-api-to-expand-product-reporting-for-all-campaign-types-on-june-15/)

- [Seresa: June 15 Google Ads API: Video, PMax Product Costs](https://seresa.io/blog/performance-max-reporting/google-ads-api-adds-video-and-pmax-product-costs-on-june-15-no-backfill)

- [Qwestyon: Performance Max Channel Report Explained: What It Actually Tells You](https://www.qwestyon.com/blog/performance-max-channel-report-explained-what-it-actually-tells-you)