细分的报告
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
新版 Search Ads 360 Reporting API 现已发布。这一新 API 提供
可以更灵活地生成自定义报告,并将数据整合到您的报告应用程序中
和进程。详细了解如何迁移到和使用
新版 Search Ads 360 报告
API。
除非您请求更具体的、更细致的数据,否则 Search Ads 360 API 仅返回汇总数据
数据。例如,关键字中的“点击次数”
报告会列出指定时间范围内某个关键字获得的总点击次数。
keywordText |
keywordLandingPage |
clicks |
微件 |
http://www.example.com |
6000 |
但是,如果您请求按季度细分的关键字报告,
每个季度会占一行,点击次数列中会列出季度总计。
keywordText |
keywordLandingPage |
quarterStart |
quarterEnd |
clicks |
微件 |
http://www.example.com |
2012-01-01 |
2012-03-31 |
1000 |
微件 |
http://www.example.com |
2012-04-01 |
2012-06-30 |
1000 |
微件 |
http://www.example.com |
2012-07-01 |
2012-09-30 |
1000 |
微件 |
http://www.example.com |
2012-10-01 |
2012-12-31 |
3000 |
请注意,只有在细分数据可用时,细分后的报告才会返回行。
例如,在包含 floodlightActivity
列的关键字报告中,
如果没有指标归因,则报表中不会显示 Floodlight 活动对
以将其纳入报告日期范围内
某些细分与特定列不兼容
某些细分可能会导致特定列返回无效数据。例如,细分依据
仅当您添加用于生成 Floodlight 报表的列时,floodlightActivity
才有意义
数据,例如 dfaActions
、dfaRevenue
、dfaTransactions
和 dfaWeightedActions
。其他类型的转化列(例如
adWordsConversions
)或报告引擎指标(如点击次数和
未包含 Floodlight 报告的数据,因此,如果您将这些代码
按“floodlightActivity
”细分报表。
如何请求细分报告
若要请求细分报告,请在报告类型参考中添加一列,在其中列出 segment
作为其行为。
以下异步请求针对的是按季度细分的关键字报表。通过
每行中的“点击次数”列将包含相应季度的总点击次数:
{
"reportScope": {
"agencyId": "20700000000000123", // Replace with your IDs
"advertiserId": "2170000012345" // Replace with your IDs
},
"reportType": "keyword",
"columns": [
{ "columnName": "campaignId" },
{ "columnName": "keywordText" },
{ "columnName": "keywordLandingPage" },
{ "columnName": "quarterStart" },
{ "columnName": "quarterEnd" },
{ "columnName": "clicks" },
]
"timeRange" : {
"startDate" : "2012-01-01",
"endDate" : "2012-12-31"
},
"downloadFormat": "csv",
"maxRowsPerFile": 5000000,
"statisticsCurrency": "agency",
"verifySingleTimeZone": false,
"includeRemovedEntities": false
}
注意:请谨慎选择日期。如果您要申请季度报告,请确保
报告的
timeRange
包含整个季度。否则,您将只能获得部分结果,
人们认为点击次数、收入等出现了大幅下降。
请求多个片段
您可以在一个请求中包含多个细分列。请注意以下几点:
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-29。
[null,null,["最后更新时间 (UTC):2025-08-29。"],[[["\u003cp\u003eThe new Search Ads 360 Reporting API offers greater flexibility for creating custom reports and integrating data into your workflows.\u003c/p\u003e\n"],["\u003cp\u003eThe API provides aggregated data by default, but you can request segmented data for a more granular view, such as segmenting by quarter to see quarterly click totals.\u003c/p\u003e\n"],["\u003cp\u003eSome segments are incompatible with certain columns, and including multiple segments can significantly increase the number of rows in your reports.\u003c/p\u003e\n"],["\u003cp\u003eWhen requesting segmented reports, ensure the time range covers the entire segment period for accurate results, and be mindful of potential data inconsistencies when combining segments with specific columns.\u003c/p\u003e\n"],["\u003cp\u003eYou can request segmented reports by including columns with "segment" behavior, as demonstrated in the provided code example for a keyword report segmented by quarter.\u003c/p\u003e\n"]]],["The new Search Ads 360 Reporting API allows for building custom reports and integrating data. Segmented reports show detailed data, with each segment (e.g., quarter) receiving its own row and totals. Rows appear only if data exists for the segment. Certain segments are incompatible with specific columns, yielding invalid data. To request a segmented report include a column listing `segment` as it's behavior, and when requesting time-related segments, ensure that the date range encompasses the full period. The use of multiple segments in a report is possible but they can not be time related.\n"],null,["# Segmented Reports\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\n\nThe Search Ads 360 API returns only aggregated data unless you request more detailed, segmented\ndata. For example, the clicks column in a [keyword\nreport](/search-ads/v2/report-types/keyword) lists the total number of clicks on a keyword during the time range you specify.\n\n| keywordText | keywordLandingPage | clicks |\n|-------------|------------------------|--------|\n| widgets | http://www.example.com | 6000 |\n\nBut if you request a keyword report that segments by quarter, for each keyword you'll\nsee one row for each quarter, and the clicks column will list the quarterly totals. \n\n| keywordText | keywordLandingPage | quarterStart | quarterEnd | clicks |\n|-------------|------------------------|--------------|------------|--------|\n| widgets | http://www.example.com | 2012-01-01 | 2012-03-31 | 1000 |\n| widgets | http://www.example.com | 2012-04-01 | 2012-06-30 | 1000 |\n| widgets | http://www.example.com | 2012-07-01 | 2012-09-30 | 1000 |\n| widgets | http://www.example.com | 2012-10-01 | 2012-12-31 | 3000 |\n\nNote that a segmented report returns a row only if data is available for a segment.\nFor example, in a keyword report with the `floodlightActivity` column, a keyword and\nFloodlight activity pair will not appear in the report if there are no metrics attributed\nto it for the report date range.\n\n### Some segments are incompatible with specific columns\n\nSome segments may cause specific columns to return invalid data. For example, segmenting by\n`floodlightActivity` is meaningful only if you include columns that report Floodlight\ndata, such as `dfaActions`, `dfaRevenue`, `dfaTransactions`,\nand `dfaWeightedActions`. Other types of conversion columns (such as\n`adWordsConversions`), or columns that report engine metrics (such as clicks and\nimpressions), don't contain data reported by Floodlight, so they return invalid values if you\nsegment a report by `floodlightActivity`.\n\n### How to request a segmented report\n\nTo request a segmented report, include a column that lists `segment` as its behavior in the [Types of Reports](/search-ads/v2/report-types) reference.\n\nThe following asynchronous request is for a keyword report segmented by quarter. The\nclicks column in each row will contain the total number of clicks for the quarter: \n\n```\n{\n \"reportScope\": {\n \"agencyId\": \"20700000000000123\", // Replace with your IDs\n \"advertiserId\": \"2170000012345\" // Replace with your IDs\n },\n \"reportType\": \"keyword\",\n\n \"columns\": [\n { \"columnName\": \"campaignId\" },\n { \"columnName\": \"keywordText\" },\n { \"columnName\": \"keywordLandingPage\" },\n\n { \"columnName\": \"quarterStart\" },\n { \"columnName\": \"quarterEnd\" },\n { \"columnName\": \"clicks\" },\n ]\n \"timeRange\" : {\n \"startDate\" : \"2012-01-01\",\n \"endDate\" : \"2012-12-31\"\n },\n \"downloadFormat\": \"csv\",\n \"maxRowsPerFile\": 5000000,\n \"statisticsCurrency\": \"agency\",\n \"verifySingleTimeZone\": false,\n \"includeRemovedEntities\": false\n}\n \n``` \n**Note** : Be careful with dates. If you're requesting a quarterly report, make sure that the report's [timeRange](/search-ads/v2/reference/reports#request.timeRange) includes the entire quarter. Otherwise you'll get only partial results, which might make people think there's been a drastic reduction in clicks, revenue, and so on.\n\nRequesting multiple segments\n----------------------------\n\nYou can include more than one segment column in a request. Note the following:\n\n- If you segment by week, month, or quarter, we recommend that you include both the\n start and end columns in your request. For example, in a quarterly report, include both\n the `quarterStart` and `quarterEnd` columns. Including both of these\n columns will output the period's start and end dates, which will help confirm that you've\n included data for each full period.\n\n- You cannot include different types of time-related segments in the same request.\n For example, you cannot segment by quarter and month in the same request.\n\n- The number of rows could increase exponentially with each additional segment."]]