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.
The Search Ads 360 API returns only aggregated data unless you request more detailed, segmented
data. For example, the clicks column in a keyword
report lists the total number of clicks on a keyword during the time range you specify.
keywordText
keywordLandingPage
clicks
widgets
http://www.example.com
6000
But if you request a keyword report that segments by quarter, for each keyword you'll
see one row for each quarter, and the clicks column will list the quarterly totals.
keywordText
keywordLandingPage
quarterStart
quarterEnd
clicks
widgets
http://www.example.com
2012-01-01
2012-03-31
1000
widgets
http://www.example.com
2012-04-01
2012-06-30
1000
widgets
http://www.example.com
2012-07-01
2012-09-30
1000
widgets
http://www.example.com
2012-10-01
2012-12-31
3000
Note that a segmented report returns a row only if data is available for a segment.
For example, in a keyword report with the floodlightActivity column, a keyword and
Floodlight activity pair will not appear in the report if there are no metrics attributed
to it for the report date range.
Some segments are incompatible with specific columns
Some segments may cause specific columns to return invalid data. For example, segmenting by
floodlightActivity is meaningful only if you include columns that report Floodlight
data, such as dfaActions, dfaRevenue, dfaTransactions,
and dfaWeightedActions. Other types of conversion columns (such as
adWordsConversions), or columns that report engine metrics (such as clicks and
impressions), don't contain data reported by Floodlight, so they return invalid values if you
segment a report by floodlightActivity.
How to request a segmented report
To request a segmented report, include a column that lists segment as its behavior in the Types of Reports reference.
The following asynchronous request is for a keyword report segmented by quarter. The
clicks column in each row will contain the total number of clicks for the quarter:
Note: Be careful with dates. If you're requesting a quarterly report, make sure that the
report's 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.
Requesting multiple segments
You can include more than one segment column in a request. Note the following:
If you segment by week, month, or quarter, we recommend that you include both the
start and end columns in your request. For example, in a quarterly report, include both
the quarterStart and quarterEnd columns. Including both of these
columns will output the period's start and end dates, which will help confirm that you've
included data for each full period.
You cannot include different types of time-related segments in the same request.
For example, you cannot segment by quarter and month in the same request.
The number of rows could increase exponentially with each additional segment.
[[["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-08-28 UTC."],[[["\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."]]