The previous Search Ads 360 Reporting API is decommissioned. You can now create your reports using the new Search Ads 360 Reporting API.
Note that the get and getByCustomerId methods in the Search Ads 360 Conversion API are being deprecated in Q3 2025. To continue accessing conversion data, you must create a report using the conversion resource using the new Search Ads 360 Reporting API. See more details here.
Stay organized with collections
Save and categorize content based on your preferences.
The new Search Ads 360 Reporting API is now available. The new API provides
enhanced flexibility to build custom reports and integrate the data into your reporting applications
and processes. Learn more about migrating to and using the new Search Ads 360 Reporting
API.
Shopping campaigns use product groups instead of keywords to detemine when to show ads.
Product groups differ from keywords in several ways:
Metrics automatically float from one product group to another as the shape of the
product-group tree changes. For example, if an advertiser subdivides the
"All products" product group into "Brand = X" and "Everything else", metrics will move
from "All products" to the new child groups.
Only "Active" product groups are saved in Search Ads 360. Metrics are removed from
deleted product groups and floated onto "Active" product groups.
Product group IDs may change even though the resulting tree is unchanged. For example,
if an advertiser changes a product group setting to exclude it from bidding, the product
group's ID will change.
Parent product groups show the sum of metrics from their child product groups.
When reporting on product groups, do the following:
Use the productGroup column in the
productGroup
report to identify the product group. This column contains the criteria that were used
create the product group, which remain constant even if product group IDs change.
If you're aggregating metrics,
use a filter to
include only those product groups that are leaf nodes. This prevents double-counting
metrics that are rolled up from child to parent groups. Note that filters specify the
types of data you want to include in the report, so your filter should
include only those product groups that are not subdivided. For example,
include this filter in your request:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-07 UTC."],[[["The new Search Ads 360 Reporting API offers increased flexibility for creating custom reports and integrating data into reporting tools."],["Shopping campaigns rely on product groups instead of keywords, with metrics dynamically shifting between product groups as the product-group tree evolves."],["When reporting on product groups, utilize the `productGroup` column for identification and apply filters to aggregate metrics solely from leaf nodes, avoiding double-counting."]]],["The Search Ads 360 Reporting API is available, offering flexibility for custom reports and data integration. Shopping campaigns use product groups, not keywords, to trigger ads. Product group metrics shift with tree changes; only \"Active\" groups are saved, and IDs can change. When reporting, use the `productGroup` column to identify groups. Filter to include only leaf nodes (not subdivided product groups) to prevent metric double-counting. Use the provided filter example.\n"]]