Google Ads API Now Reports Product-Level Metrics for PMax, Video, and Demand Gen
Google Ads API adds product-level cost and conversion data for Performance Max, Video, Demand Gen, and App campaigns on June 15, 2026. Agencies and in-house teams can now build automated product-ROI alerts without manual UI extraction.
Google Ads API now reports cost and conversion data at the product level for Video, Demand Gen, App, and Performance Max campaigns starting June 15, 2026. Previously, these campaign types returned only impressions and clicks in product-level queries. The change enables automated pipelines that alert on underperforming products without requiring manual extraction from the Google Ads UI.
Key takeaways
- Google Ads API adds cost and conversion metrics at the product level for Video, Demand Gen, App, and Performance Max campaigns on June 15, 2026.
- Performance Max now returns full network-level breakdown data - previously this was unavailable via API, only visible in the UI.
- Any alerting system calibrated on pre-June 15 product data will need recalibration after the structural break in the data series.
- Programmatic product-ROI analysis across Demand Gen and Video is now possible without manual UI extraction.
- Agencies running multi-product accounts can automate spend-to-conversion attribution at the SKU or product group level.
Why product-level API data was missing before June 15
Before this update, the Google Ads API returned product-level data for Standard Shopping and some Search campaigns. For Video, Demand Gen, App, and Performance Max campaigns, the API returned only impressions and clicks at the product level. Cost and conversion data were visible in the Google Ads UI but not accessible programmatically.
This forced performance teams into a manual workflow: log into the UI, navigate to the product view, export a report, paste it into a spreadsheet or BI tool. For accounts with thousands of SKUs across multiple Demand Gen and PMax campaigns, this could mean hours of manual work per week.
The operational problem this creates: product-level anomalies accumulate undetected. A product group losing conversion volume on PMax for three consecutive days might not surface until the weekly review - by which time budget has been wasted on an underperforming segment.
What changes on June 15, 2026
Google's June 2026 API expansion announcement confirmed that the Google Ads API (v21+) will expose the following at the product level for the newly covered campaign types:
- Cost - actual spend attributed to each product
- Conversions - conversion count attributed to each product
- Conversion value - revenue attributed to each product
- Network breakdown (Performance Max only) - clicks and impressions split by Search, Display, Shopping, YouTube, and other networks
For Performance Max specifically, the network-level breakdown closes the longstanding visibility gap. Advertisers could see that PMax was running across multiple surfaces, but could not query the API to get a programmatic split. Now they can.
What the data shows about product performance gaps in PMax
The ICP problem this addresses: Performance Max campaigns pool budget across campaign types and surfaces, which makes it easy to misread aggregate ROAS. As covered in the Performance Max analytics deep dive, PMax tends to overstate top-line ROAS because 20% of products drive 80% of conversions while the rest burn budget. Without product-level conversion data in the API, automated detection of this concentration is impossible.
The Google Ads API expansion enables product-segment anomaly detection - a pattern widely used in Search and Shopping but not available for PMax and Demand Gen until now. The operational implication: teams can now set threshold-based alerts (for example, "flag any product group spending more than $50 in the past 7 days with zero conversions") and run them programmatically via the API or a connected analytics platform.
Prooflytics surfaces this in the daily briefing as product-segment performance anomalies once your Google Ads account is connected - alerting when spend concentration shifts or when specific product groups underperform their account-level ROAS baseline.
Stop stitching platform exports together
Every channel in one brief — plus the memory of what each one actually drove.
14 days free · no credit card
How to use the new product metrics in practice
Step 1: Treat June 15 as a data series break. Do not blend pre- and post-June 15 product data in the same time-series comparison. Cost and conversion metrics that returned zero or null before June 15 (for Video, Demand Gen, App, PMax) will show real values afterward. Any trend line or anomaly detection threshold calibrated on the pre-June 15 period needs to be reset.
Step 2: Build a product-level performance query.
In the Google Ads API, query the shopping_performance_view resource combined with segments.product_item_id, metrics.cost_micros, and metrics.conversions filtered by campaign type. For PMax network breakdown, query campaign_criterion with metrics.clicks segmented by segments.ad_network_type.
Step 3: Set product-level alert thresholds. For each major product or product group, define a baseline ROAS or conversion rate over the first two weeks after June 15. Use those baselines to set alerts for deviation. A product group spending more than 10% of weekly budget with less than 50% of its baseline ROAS is a candidate for bid adjustment or exclusion.
Step 4: Separate Demand Gen product data from Shopping. Demand Gen campaigns using product feeds now return their own product-level cost and conversion data. Keep this data in a separate reporting segment from Standard Shopping - the audiences, placements, and creative contexts differ. Blending them produces misleading ROAS averages.
Step 5: Monitor for PMax surface-level shifts. With network breakdown data now in the API, you can track whether PMax is shifting spend between Search and Display or Shopping over time. A shift toward Display or YouTube at the same overall ROAS could indicate the algorithm is finding easier conversions at lower intent - the same misalignment described in why Smart Bidding underperforms on misconfigured accounts. Flag this in your weekly performance review.
What agencies need to update
If your agency uses a custom Google Ads API integration, automated reporting script, or third-party connector to pull product-level data, check whether your queries are filtering by campaign type. Any query that previously returned empty results for Video, Demand Gen, or App will now return data - which may cause schema issues if your pipeline assumes null values for those fields.
Update your data pipeline documentation to reflect June 15 as the start date for PMax and Demand Gen product-level metrics. While auditing data pipelines, also review what Google Ads historical data needs to be archived before the 37-month retention window removes older records. Add a note to client reporting templates that historical product data for these campaign types is available only from this date onward.
Bottom line
- Google Ads API product-level cost and conversion metrics now cover Video, Demand Gen, App, and PMax from June 15, 2026.
- Performance Max gains network-level breakdown data - enabling programmatic visibility into where PMax spends across surfaces.
- Treat June 15 as a structural break: reset alert thresholds and do not blend pre-June 15 product data in trend comparisons.
- The practical workflow: query
shopping_performance_view, set product-group ROAS thresholds, monitor PMax surface shifts weekly. - You can review independent assessments of marketing analytics platforms, including Prooflytics, on G2 in the marketing analytics category.
Frequently asked questions
Which campaign types gain product-level cost and conversion metrics on June 15?+
Video, Demand Gen, App, and Performance Max campaigns. Standard Shopping and some Search campaigns already had product-level cost and conversion data. The June 15 update closes the gap for the four campaign types that previously returned only impressions and clicks at the product level.
Does Performance Max get the same product-level metrics as Standard Shopping?+
PMax gains cost and conversion metrics at the product level plus a network-level breakdown (Search, Display, Shopping, YouTube). Standard Shopping does not have network breakdown data because it runs only on the Shopping surface. PMax product data and Shopping product data should be kept in separate reporting segments.
Will existing API queries break on June 15?+
Queries will not break - they will return data where they previously returned zeros or nulls. However, any alert or anomaly detection system calibrated on historical zero values will trigger false positives. Recalibrate thresholds after the first two weeks of real data.
How should I compare PMax product performance before and after June 15?+
You cannot directly compare pre- and post-June 15 PMax product-level conversion data because the historical data is incomplete. Establish a fresh baseline using the two to four weeks after June 15 before making optimization decisions based on product-level ROAS in PMax.
Can Prooflytics use this data for automated alerts?+
Yes. Once your Google Ads account is connected to Prooflytics, the platform will surface product-segment anomalies in your daily briefing - including spend concentration shifts, underperforming product groups, and PMax network-level budget distribution changes.
Stop stitching platform exports together
Every channel in one brief — plus the memory of what each one actually drove.
14 days free · no credit card
Continue reading
Microsoft Ads Performance Max Placement Reports: Conversion Data Explained
Microsoft Advertising expanded Performance Max placement reports to include conversion and spend data, closing a major reporting gap that previously forced advertisers to infer placement performance from aggregate metrics. For PMax campaigns on Microsoft Ads, this enables channel-level diagnosis that was not available before May 2026.
Google Ads Marketing Analytics: Metrics, Monitoring, and Setup Guide
The Prooflytics Google Ads integration delivers daily Quality Score trends, keyword waste flags, and cross-channel attribution reconciliation - so you catch CPC inflation before it compounds, not after the quarterly review.
Google Performance Max Partner Network Selection: What the Alpha Changes
Google is alpha-testing independent partner network controls for Performance Max campaigns, allowing advertisers to toggle Search Partner Network and Google Display Network separately for the first time. For brands where partner placement quality directly affects ROAS or brand safety, this changes how PMax campaigns are configured.
Google Ads API v20 Sunsetted June 10: Migration Guide and Priority Order
Google Ads API v20 officially sunsetted on June 10, 2026. Calls to v20 endpoints return errors immediately. This is the migration priority order: what breaks first, what to fix first, and which version to target.