Search Ads 360 Reporting API는 최신 플랫폼을 기반으로 하며 다양한 새 개념을 도입합니다. 이에 대해서는 다음 섹션에서 설명합니다.
리소스
리소스 객체가 보고서 유형을 대체합니다. 이제 사전 정의된 보고서 유형을 요청하는 대신 새로운 SQL과 유사한 쿼리 언어를 사용하여 모든 리소스를 쿼리할 수 있습니다.
자세한 내용은 Search Ads 360 Reporting API 구조를 참고하세요.
검색 보고
새 API에는 검색 자체 서비스가 있습니다. 검색 서비스는 기존 보고서 서비스를 대체합니다. 모든 쿼리는 보고 데이터 및 측정항목을 검색하고 검색하는 두 가지 메서드인 SearchStream 및 Search를 제공하는 SearchAds360Service를 거칩니다. 두 검색 메서드 모두 검색어와 일치하는 모든 SearchAds360Row 객체를 반환합니다. 자세한 내용은 검색 보고서 만들기를 참고하세요.
리소스 메타데이터
SearchAds360FieldService를 사용하면 SearchAds360Service 검색 메서드에서 사용할 수 있는 리소스, 리소스 필드, 세분화 키, 측정항목의 카탈로그를 동적으로 요청할 수 있습니다. 자세한 내용은 리소스 메타데이터 검색을 참조하세요.
필드 이름
API는 점 표기법으로 구분된 중첩된 필드 이름을 도입합니다. 예를 들면 campaign.id 및 ad_group.id입니다. 더 중첩할 수도 있습니다(예: ad_group.campaign.id). 자세한 내용은 Search Ads 360 Reporting API 구조를 참고하세요.
이전 Search Ads 360 API의 보고는 유사한 개념에 대해 서로 다른 항목의 별도 필드를 기반으로 합니다. 예를 들어 campaign 및 adgroup 보고서에는 별도의 campaignId 필드가 포함됩니다.
쿼리 언어
이 API에서는 Search Ads 360 쿼리 언어를 도입합니다. 이는 비즈니스에 가장 적합한 특정 보고 데이터를 검색하는 쿼리를 정의할 수 있는 유연한 SQL과 유사한 언어입니다. 자세한 내용은 Search Ads 360 쿼리 언어를 참조하세요.
새 Search Ads 360에서는 수식 열과 맞춤 전환을 맞춤 열이라고 합니다. 맞춤 열에 대해 자세히 알아보기 새 CustomColumnService는 맞춤 열을 사용 설정합니다. 필요한 권한이 있는 경우 계정 트리의 모든 계정에서 소유한 CustomColumn 리소스를 요청할 수 있습니다.
계정 관리
새 Search Ads 360에서는 계정의 계층 구조가 관리자 계정, 하위 관리자 계정, 고객 계정으로 구성됩니다. 관리자 계정은 이전 Search Ads 360의 대행사 계정을, 하위 관리자 계정은 광고주 계정을 나타냅니다. 자세한 내용은 Search Ads 360 관리자 계정에 대한 정보를 참고하세요.
[null,null,["최종 업데이트: 2025-08-29(UTC)"],[[["\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."]]
