Google Ads Splits Product Clicks: New Metrics Explained

Google Ads has split its Shopping and Performance Max click reporting into two new metrics — Product Clicks and Non-Product Clicks — in a quiet UI rollout that PPC practitioners first flagged on July 28, 2026. There was no announcement post; the only official documentation is a pair of new Help Center glossary entries.

The split sounds simple: clicks on a specific product versus clicks on everything else in the ad. But it carries a counting quirk that Google states outright — a single non-product click is credited to every product shown in the ad — and, based on our own inspection of the live v25 Metrics field reference, neither metric is queryable through the Google Ads API today. Anyone wiring this into a script, Looker Studio connector, or BI pipeline right now is going to hit a wall.

This guide covers exactly what each metric counts per Google’s own definitions, why the non-product number can look inflated, which campaign types and report views expose the columns, what the API does and doesn’t support, and how to use the split as a diagnostic without misreading it. Everything below is sourced from Google’s Help Center, the live API references, and the trade coverage that surfaced the change.

The change was first publicly flagged on July 28, 2026, when Search Engine Roundtable reported that Google Ads had added two new product-reporting metrics to some reports. The authoritative definitions live on Google’s own Help Center glossary pages, and they are worth quoting precisely because the two metrics are narrower than their names suggest.

Per Google’s Product clicks definition, product clicks are “the number of times customers have clicked directly on a specific product within an ad.” Per the companion Non-product clicks definition, non-product clicks are “the number of times that customers click on parts of your ad that aren’t a specific product, such as the ad’s headline or your store name.”

Before this split, product reporting rolled every click into a single number, leaving advertisers to guess whether shoppers were responding to specific items or to the ad as a whole. The separation is genuinely useful — it just arrived with a counting behavior and an access limitation that the column names alone don’t reveal.

The most important sentence in either glossary page is the one about attribution. Google states it plainly on the non-product clicks definition page — and it is the reason this metric will look strange in your reports the first time you add the column.

The worked example — first posted on LinkedIn by the practitioner who spotted the columns, and independently corroborated by a second practitioner — makes the mechanic concrete. If your ad displays five products and a shopper clicks “Visit site” rather than any specific product, Google records one non-product click against all five products. At the per-product reporting level, a single user action reads as five clicks. The chart below recomputes that stated rule across ad sizes: non-product clicks logged = products shown × 1 click event.

The consequence for analysis: per-product non-product clicks are not user actions and must never be summed across products as if they were. A products report where non-product clicks dwarf product clicks may describe one modestly-clicked ad with a large product set — not a flood of header clicks. Any share-of-clicks math you run on these columns needs the denominator stated explicitly: percentage of logged click rows, not percentage of shoppers.

Google’s About Product Reporting page defines the campaign-type scope: Performance Max, Standard Shopping, Video, App, and Demand Gen. There is a catch in the hierarchy, though — account-level product reporting covers only Standard Shopping and Performance Max; for Video, App, and Demand Gen, product data stays campaign-level.

The rollout is explicitly gradual and UI-first. Ecommerce agency Common Thread Collective’s July 29 coverage put it directly: “Both metrics are rolling out to some reports according to Google’s announcement, so check your Shopping campaign columns today to see if they’re live on your account.” In-account, the place to look is the column selector in the Campaigns, Ad Groups, and Products reporting views for Shopping and PMax-with-Shopping-feed campaigns.

This is the single most actionable fact in the story, and none of the trade coverage we reviewed checked it. We inspected the live Google Ads API v25 Metrics field reference directly: there is no product_clicks and no non_product_clicks field. The clicks family contains only the pre-existing entries — clicks, combined_clicks, and their relatives. As of July 30, 2026, this is a UI and report-column feature, not an API-queryable one.

There is a partial mapping worth knowing. In the API’s Shopping ads reporting guide, the existing metrics.clicks field on shopping_performance_view is the one the Ads UI now labels “Product Clicks” — a relabel of a field that already existed, not a new field. The non-product half has no API counterpart at all. If your reporting stack runs on scripts — say, an AI-agent account-QA script or a pipeline built during the Merchant API migration for Google Ads scripts — the only route to non-product clicks today is a manual export from the UI.

To make the access picture concrete, the table below maps the four adjacent Google reporting surfaces a PPC manager or developer would reasonably check — what each one measures, where it applies, and whether the new split is reachable there today. Every piece of existing coverage treats the feature as one flat thing; in practice, it lives on exactly one surface.

Here is the part nobody else has reported: there is no Google announcement post for this feature beyond the Help Center glossary. We verified the entire July 2026 archive of the Ads Developer Blog directly — nine posts, July 6 through 30 — and the phrases “product clicks” and “non-product clicks” appear in none of them. The Google Ads API v25 announcement (July 22) covers YouTube sub-format breakdowns, Shorts social metrics, a Loyalty retention goal, and a revamped New Customer Acquisition goal — nothing about a click split. We covered that release in our July 2026 Google Ads API v25 ops sweep. (The nearest same-week dev-blog release, Structured Data Files v10.1 on July 29, is a Display & Video 360 update with no connection to Shopping click reporting.)

The feature instead reached advertisers the practitioner way: PPC specialist Yash Mandlesha spotted the new columns and posted the worked example on LinkedIn around July 28, a second practitioner independently corroborated it, Search Engine Roundtable picked it up the same day, and PPC News Feed logged it on July 30, crediting the original LinkedIn spotting. Every outlet framed it as “spotted” or “observed” — not “announced” — which is the honest framing. It lands in a July already crowded with Shopping-side changes, from this month’s Shopping surface reshuffle to the Local Inventory Ads default-on change announced July 20 and effective August 31.

The shape of this one is worth naming. It reached advertisers the quiet way — new columns appear, a glossary page goes live, and the practitioner community does the announcing. One instance is not a trend, but it is a reminder: Help Center diffs and practitioner networks belong in the monitoring stack alongside official release notes. Advertisers waiting for a developer-blog post on this particular change will not find one.

A naming collision is waiting to trip up anyone who searches Google’s developer docs for this feature. Merchant Center’s Reports API already exposes a resource called NonProductPerformanceView — and it has nothing to do with the new Ads metric. That view tracks clicks, impressions, and click-through rate for “images and online store links leading to your non-product pages” — think brand storefront and about pages — inside the google-shopping-merchant-reports API (v1alpha). Different product, different API, different definition of “non-product.” If a developer on your team finds that resource and declares the new metric queryable, they have found the wrong “non-product.”

One more piece of context stops a misread of historical trends. The product-reporting infrastructure this split rides on was expanded on June 15, 2026, when Google widened shopping_performance_view to return uniform data across all Merchant-Center-linked campaign types and PMax product reporting began including all networks. That expansion caused a one-time, non-comparable jump in reported metrics for affected campaigns, with no historical backfill — as Google’s own announcement put it, “Historical API requests for dates prior to the launch will not contain this expanded data.” If your product-level click counts already stepped up mid-June, that was the infrastructure change, not this metric split — and any month-over-month product-click comparison spanning June 15 is comparing two different measurement regimes.

Treated correctly, the split is a diagnostic, not a lever. Common Thread Collective’s framing is the right starting point: “A campaign with strong non-product clicks but weak product clicks may signal that your imagery or pricing is missing, not your copy or bidding.” In other words, when shoppers engage with the ad shell but not the products inside it, the products are the suspect — which makes your Shopping product-feed strategy (titles, imagery, price competitiveness) the first place to look, not your bid strategy.

Looking forward: the pattern of the June 15 infrastructure change preceding a July UI split suggests Google is progressively deepening product-level reporting, and it would be consistent with that direction for a future API version to expose these fields — but nothing published on or before July 30, 2026 commits to it. Our paid media team is treating the split as read-only diagnostic input this quarter: useful for feed and creative prioritization, too new and too partially-rolled-out to anchor client KPIs.