[null,null,["最后更新时间 (UTC)：2025-08-29。"],[[["\u003cp\u003eThe Search Ads 360 Reporting API utilizes resources and a SQL-like query language instead of predefined report types for flexible data retrieval.\u003c/p\u003e\n"],["\u003cp\u003eSearch reporting is handled by the \u003ccode\u003eSearchAds360Service\u003c/code\u003e, enabling retrieval of reporting data and metrics through \u003ccode\u003eSearchStream\u003c/code\u003e and \u003ccode\u003eSearch\u003c/code\u003e methods.\u003c/p\u003e\n"],["\u003cp\u003eResource metadata, including resources, fields, and metrics, can be dynamically accessed through the \u003ccode\u003eSearchAds360FieldService\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe API introduces nested field names (e.g., \u003ccode\u003ecampaign.id\u003c/code\u003e) and a dedicated Search Ads 360 Query Language for precise data querying.\u003c/p\u003e\n"],["\u003cp\u003eAccount management is structured hierarchically, requiring the use of the \u003ccode\u003elogin-customer-id\u003c/code\u003e header when accessing accounts below a manager account.\u003c/p\u003e\n"]]],["The Search Ads 360 Reporting API introduces resources, replacing report types, and uses a SQL-like query language for data retrieval. The `SearchAds360Service` handles data requests via `SearchStream` and `Search` methods. `SearchAds360FieldService` provides resource metadata. Field names use dot notation, like `campaign.id`. The API has a new account hierarchy, custom columns, and `login-customer-id` header requirements for accessing sub-accounts. `GET` requests exist, but are used for accessing entity services and data. The API uses semantic versioning.\n"],null,["# New concepts in the new Search Ads Reporting API\n\nThe Search Ads 360 Reporting API is based on a modern platform and introduces\na number of new concepts. These are described in the following sections.\n\nResources\n---------\n\nResource objects replace report types. Instead of requesting predefined report\ntypes, you can now query all resources using a new SQL-like query language.\nSee [Search Ads 360 Reporting API structure](/search-ads/reporting/concepts/api-structure) to learn more.\n| **Note:** The Search Ads 360 Reporting API provides metrics for most resources only at the client account level. Learn more about the [Search Ads 360 account hierarchy and resource ownership](/search-ads/reporting/concepts/account_level_resource).\n\nSearch reporting\n----------------\n\nSearch has its own service in the new API. The Search service replaces the legacy Reports service. All queries go through\n[`SearchAds360Service`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#google.ads.searchads360.v0.services.SearchAds360Service) that provides two methods, `SearchStream` and `Search`,\nfor searching and retrieving reporting data and metrics. Both search methods\nreturn all `SearchAds360Row` objects that match your search query. See\n[Create search reports](/search-ads/reporting/concepts/search-reports) for more\ninformation.\n\nResource metadata\n-----------------\n\n[`SearchAds360FieldService`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#searchads360fieldservice) allows you to dynamically request the catalog for resources, resource fields, segmentation keys, and metrics available in the\n`SearchAds360Service` search methods. See\n[Retrieve resource metadata](/search-ads/reporting/concepts/resource-metadata)\nto learn more.\n\nField names\n-----------\n\nThe API introduces nested field names separated with the dot notation. For\nexample, `campaign.id` and `ad_group.id`. You can also nest further, for\nexample,`ad_group.campaign.id`. See [Search Ads 360 Reporting API structure](/search-ads/reporting/concepts/api-structure) to learn more.\n\nReporting in the previous Search Ads 360 API is based on separate fields on\ndifferent entities for similar concepts. For example, both the [`campaign`](/search-ads/v2/report-types/campaign) and [`adgroup`](/search-ads/v2/report-types/adGroup) reports include a separate `campaignId`\nfield.\n\nQuery language\n--------------\n\nThe API introduces the Search Ads 360 Query Language. This is a flexible,\nSQL-like language that allows you to define queries to retrieve the specific\nreporting data that best suits your business. See\n[Search Ads 360 Query Language](/search-ads/reporting/query/query-language)\nto learn more.\n\nGet requests\n------------\n\nIn the new API, searching has its own service (`SearchAds360Service`), but\n`GET` requests still exist on each entity's specific service. For example, you\ncan get custom column information from the [`CustomColumnService`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#customcolumnservice). See\n[Format changes in the Search Ads 360 Reporting API](/search-ads/reporting/migrate/format-changes) to learn more.\n| **Note:** `GET` requests serve a different purpose in the new API. You cannot filter as part of a get call. When you pass the entity's resource name as an identifier, the response includes every populated field (there is no need to list them).\n\nCustom columns\n--------------\n\nIn the new Search Ads 360, *formula columns* and *custom conversions* are called\n*custom columns* . [Learn more about custom columns](https://support.google.com/sa360/answer/12177810?hl=en). The new\n[`CustomColumnService`](/search-ads/reporting/api/reference/rpc/google.ads.searchads360.v0.services#customcolumnservice) enables custom columns. Provided you have the necessary permissions, you can request `CustomColumn` resources owned by any account in\nthe account tree.\n\nAccount management\n------------------\n\nThe new Search Ads 360 organizes accounts into a hierarchy of manager accounts,\nsub-manager accounts, and client accounts. A manager account represents the\nagency account, and sub-manager accounts represent advertiser accounts in the\nprevious Search Ads 360. See [About Search Ads 360 manager accounts](https://support.google.com/sa360/answer/9158072) to learn more.\n\nYou can [query the account tree](/search-ads/reporting/concepts/account_level_resource#understanding_the_account_hierarchy) and then submit requests for each account you would\nlike reporting data from.\n\nAs a result of the change in the account hierarchy, fields related to the\nadvertiser/agency concept have been\nreplaced with appropriate alternatives to provide functional parity wherever\npossible. See [Fields mappings](/search-ads/reporting/migrate/mappings/field-mappings) for a list of affected\nfields and their substitutes.\n\nLogin customer ID header\n------------------------\n\n`login-customer-id` is a new header that is required when using a manager\naccount to access a sub-manager or client account. See\n[Login customer ID header](/search-ads/reporting/concepts/call-structure#login_customer_id_header) for\nmore more information.\n\nVersioning\n----------\n\nThe Search Ads 360 Reporting API uses [semantic versioning](https://semver.org/).\nThere are major and minor versions, formatted as\n`v`*MAJOR* `_`*MINOR*. See [Versioning](/search-ads/reporting/concepts/versioning) to learn more."]]
