产品组数
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
购物广告系列使用产品组（而不是关键字）来确定何时展示广告。
产品组与关键字有以下几方面的差异：
- 指标会按照
产品组树状变化。例如，如果广告客户细分
“所有产品”产品组添加到“品牌 = X”和“所有其他”指标
来自“所有产品”分配给新的下级群组。
- 仅“有效”产品组会保存在 Search Ads 360 中。指标已从以下位置移除：
已删除产品组并置于“有效”状态产品组。
- 即使生成的树状结构保持不变，产品组 ID 也可能会发生变化。例如：
如果广告客户更改了产品组设置以将其从出价中排除，该产品
群组的 ID 会发生变化。
- 父级产品组会显示其子级产品组的指标总和。
在为产品组生成报告时，请执行以下操作：
- 使用
productGroup
productGroup
以找出产品组此列包含所用的条件
创建产品组，即使产品组 ID 发生变化，该产品组也会保持不变。
- 如果要汇总指标
使用过滤条件
仅包含属于叶节点的产品组。这样可以防止重复统计
从下级组汇总到上级组的指标。请注意，过滤条件用于指定
您想要在报告中包含的数据类型，因此您的过滤器应
仅包含那些未细分的产品组。例如：
在您的请求中添加以下过滤条件：
"filters": [
{
"column" : { "columnName": "productGroupPartitionType" },
"operator" : "notEquals",
"values" : [ "Subdivided" ]
}
]
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2024-08-20。
[null,null,["最后更新时间 (UTC)：2024-08-20。"],[[["\u003cp\u003eThe new Search Ads 360 Reporting API offers increased flexibility for creating custom reports and integrating data into reporting tools.\u003c/p\u003e\n"],["\u003cp\u003eShopping campaigns rely on product groups instead of keywords, with metrics dynamically shifting between product groups as the product-group tree evolves.\u003c/p\u003e\n"],["\u003cp\u003eWhen reporting on product groups, utilize the \u003ccode\u003eproductGroup\u003c/code\u003e column for identification and apply filters to aggregate metrics solely from leaf nodes, avoiding double-counting.\u003c/p\u003e\n"]]],["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"],null,["# Product Groups\n\nThe 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\nAPI](https://developers.google.com/search-ads/reporting/overview).\n\nShopping campaigns use product groups instead of keywords to detemine when to show ads.\nProduct groups differ from keywords in several ways:\n\n- 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.\n- Only \"Active\" product groups are saved in Search Ads 360. Metrics are removed from deleted product groups and floated onto \"Active\" product groups.\n- 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.\n- Parent product groups show the sum of metrics from their child product groups.\n\nWhen reporting on product groups, do the following:\n\n1. Use the `productGroup` column in the [`productGroup`](/search-ads/v2/report-types/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.\n2. If you're aggregating metrics, [use a filter](/search-ads/v2/how-tos/reporting/filtered-reports) 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: \n\n ```\n \"filters\": [\n {\n \"column\" : { \"columnName\": \"productGroupPartitionType\" },\n \"operator\" : \"notEquals\",\n \"values\" : [ \"Subdivided\" ]\n }\n ]\n ```"]]
