Google Ads UI 中的報表
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本指南會將 Google Ads 使用者介面中報表的概念和命名慣例,對應至您可以使用 Google Ads 查詢語言 (GAQL) 和 Google Ads API 產生的報表。
常見 UI 詞彙
下表列出使用者介面中常見的字詞,以及這些字詞對應的 Google Ads 查詢語言 (GAQL)。
欄

使用者介面中的資料欄等同於 GAQL 中的資源欄位、區隔欄位和指標。
篩選
您可以篩選及整理報表中的資料。
日期範圍
Google Ads 使用者介面會顯示帳戶統計資料表,以及用來控管這些統計資料日期範圍的下拉式選單。

您可以在 GAQL 查詢的 WHERE 子句中,對 segments.date
進行篩選,在 GAQL 中取得相同的控制權。
篩選器

使用者介面中的篩選器等同於 GAQL 的 WHERE 子句中的一或多個條件。
區隔

如要查看更詳細的統計資料,請依區隔分割資料。舉例來說,假設您想分別查看 Google 搜尋聯播網和 Google 多媒體廣告聯播網的曝光次數,在這種情況下,請依聯播網區隔報表。如要瞭解如何在 SELECT 子句中加入區隔欄位,請參閱「區隔」。
在使用者介面中瀏覽報表時,可使用每個資料表底部的控制項切換頁面,並從一組定義的大小中選取要顯示的結果數量。

使用 GoogleAdsService.Search
透過 next_page_token
擷取報表時,可以逐頁瀏覽結果。如要擷取整個結果集,且不使用任何分頁,請使用 GoogleAdsService.SearchStream
。
訂單結果
在使用者介面中,您可以選取資料欄來排序結果。

在 GAQL 中,您可以使用 ORDER BY 子句和 LIMIT 子句,排序查詢結果。
在使用者介面中,報表可以下載為 CSV、TSV 或 XML 等格式。

API 不直接支援輸出不同格式,因此您必須執行一些後續處理作業。請參閱這個程式碼範例,瞭解如何在用戶端實作 CSV 格式。
安排報表執行時間並以電子郵件傳送
您可以在使用者介面中排定報表傳送時間並透過電子郵件傳送,但 API 不支援這些功能。
預先定義報表
您可以在 Google Ads 使用者介面中建立預先定義的報表清單。

以下列出基本預先定義的報表,以及相應的 GAQL 資源名稱。
以前表為例,您可以使用下列 GAQL 產生帳戶報表:
SELECT
customer.descriptive_name,
customer.id,
metrics.clicks,
metrics.impressions,
metrics.ctr,
metrics.average_cpc,
metrics.cost_micros,
metrics.absolute_top_impression_percentage,
metrics.top_impression_percentage,
metrics.average_cpm
FROM customer
WHERE segments.date DURING LAST_7_DAYS
常見差異
比較 UI 報表與 API 報表時,最常見的差異之一是 UI 會隱含地篩除已移除的實體,但 API 不會。
如要複製預設 UI 檢視畫面,您需要新增篩選器 (通常使用 status
欄位),排除已移除的資料列。例如:
SELECT campaign.name
FROM campaign
WHERE campaign.status != "REMOVED"
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-27 (世界標準時間)。
[null,null,["上次更新時間:2025-08-27 (世界標準時間)。"],[[["\u003cp\u003eThis guide explains how to generate reports using the Google Ads Query Language (GAQL) and the Google Ads API, mirroring the functionality of reports within the Google Ads UI.\u003c/p\u003e\n"],["\u003cp\u003eIt provides mappings between common UI terms like Columns, Filters, and Segmentation to their corresponding GAQL equivalents, enabling users to construct queries effectively.\u003c/p\u003e\n"],["\u003cp\u003eThe document details how to achieve UI functionalities like filtering by date range, pagination, ordering results, and accessing predefined reports using GAQL.\u003c/p\u003e\n"],["\u003cp\u003eUsers are made aware of common differences between UI and API reports, such as the UI's implicit filtering of removed entities, and are provided with guidance on replicating UI behavior in their queries.\u003c/p\u003e\n"],["\u003cp\u003eWhile functionalities like downloading in various formats and scheduling/emailing are available in the UI, they require additional implementation or are not directly supported within the API.\u003c/p\u003e\n"]]],[],null,["# Reports in the Google Ads UI\n\nThis guide maps the concepts and naming conventions for reports in the Google Ads UI\nto the reports that you can generate using the Google Ads Query Language (GAQL) and\nthe Google Ads API.\n\nCommon UI terms\n---------------\n\nThe following table summarizes some of the common terms used in the UI and their\nmappings to the [Google Ads Query Language (GAQL)](/google-ads/api/docs/query/overview).\n\n| UI | GAQL |\n| [Columns](/google-ads/api/docs/reporting/uireports#columns) | Any resource, segment field or metric in the [SELECT clause](/google-ads/api/docs/query/structure#select) of a GAQL query. |\n| [Date Range](/google-ads/api/docs/reporting/uireports#filtering) | Date ranges map to a [WHERE clause](/google-ads/api/docs/query/structure#where) filtering on `segments.date`. |\n| [Filters](/google-ads/api/docs/reporting/uireports#filtering) | One or more conditions in the [WHERE clause](/google-ads/api/docs/query/structure#where). |\n| [Segment fields](/google-ads/api/docs/reporting/uireports#segmentation) | Apply [segmentation](#segmentation) by including segment fields in your GAQL query. |\n| [Pagination](/google-ads/api/docs/reporting/uireports#pagination) | [Paging](/google-ads/api/docs/reporting/paging) breaks up the result set of the query into multiple pages. |\n|-------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|\n\n### Columns\n\nColumns in the UI are equivalent to\n[Resource fields](/google-ads/api/docs/query/overview#query_for_resource_attributes),\n[Segment fields](/google-ads/api/docs/reporting/segmentation), and\n[Metrics](/google-ads/api/docs/query/overview#query_for_metrics) in GAQL.\n\n### Filtering\n\nYou can filter and organize the data in your reports.\n\n#### Date ranges\n\nThe Google Ads UI has a table displaying account statistics, and a drop-down menu to\ncontrol the date range of these statistics.\n\nYou have the same control in GAQL by filtering on\n[`segments.date`](/google-ads/api/docs/query/date-ranges) in the WHERE clause of a GAQL\nquery.\n\n#### Filters\n\nFilters in the UI are equivalent to one or more conditions in the\n[WHERE clause](/google-ads/api/docs/query/structure#where) of GAQL.\n\n### Segmentation\n\nFor more detailed statistics, split the data by segments. For example, suppose\nyou want to see the number of impressions specific to the Google Search Network\nseparately from the Google Display Network. In that case, segment your report by\nnetwork. See [Segmentation](/google-ads/api/docs/reporting/segmentation) on how to include\nsegment fields in the SELECT clause.\n\n### Pagination\n\nNavigate through your reports in the UI using the controls available at the\nbottom of each table of data that let you switch pages and select the number of\nresults to display from a defined set of sizes.\n\nPaging through results is available when retrieving reports with\n[`GoogleAdsService.Search`](/google-ads/api/reference/rpc/v21/GoogleAdsService/Search) through\n[`next_page_token`](/google-ads/api/docs/reporting/paging). To fetch the entire result set\nwithout any pagination, use\n[`GoogleAdsService.SearchStream`](/google-ads/api/docs/reporting/streaming).\n\n### Order results\n\nIn the UI, you can order results by selecting a column.\n\nIn GAQL, you can use the\n[ORDER BY clause](/google-ads/api/docs/query/ordering-limiting#order_results) and\n[LIMIT clause](/google-ads/api/docs/query/ordering-limiting#limit_the_number_of_results)\nto order your query result.\n\nDownload formats\n----------------\n\nIn the UI, reports can be downloaded in various formats, such as CSV, TSV, or\nXML.\n\nThe API doesn't directly support different formats in its output, so you have to\nperform some post-processing. See this\n[code example](/google-ads/api/samples/campaign-report-to-csv) that shows how\nto implement CSV formatting in a client.\n\nSchedule and email reports\n--------------------------\n\nYou can schedule and email a report from the UI, but these features are not\nsupported in the API.\n\nPredefined reports\n------------------\n\nYou can create a list of predefined reports in the Google Ads UI.\n\nHere's a list of the basic predefined reports and their matching GAQL Resource\nName.\n\n| Basic Predefined Reports | GAQL Resource Name (Specify in the [FROM clause](/google-ads/api/docs/query/structure#from)) |\n|----------------------------|----------------------------------------------------------------------------------------------|\n| Account | [customer](/google-ads/api/fields/v21/customer) |\n| Campaign, Campaign details | [campaign](/google-ads/api/fields/v21/campaign) |\n| Ad group, Ad group details | [ad_group](/google-ads/api/fields/v21/ad_group) |\n| Ad, Final URL | [ad_group_ad](/google-ads/api/fields/v21/ad_group_ad) |\n| Search keyword | [keyword_view](/google-ads/api/fields/v21/keyword_view) |\n| Search terms | [search_term_view](/google-ads/api/fields/v21/search_term_view) |\n| Paid and organic | [paid_organic_search_term_view](/google-ads/api/fields/v21/paid_organic_search_term_view) |\n| Landing page | [landing_page_view](/google-ads/api/fields/v21/landing_page_view) |\n| Expanded Landing page | [expanded_landing_page_view](/google-ads/api/fields/v21/expanded_landing_page_view) |\n\nAs an example from the preceding table, you can use the following GAQL to\ngenerate the Account report: \n\n SELECT\n customer.descriptive_name,\n customer.id,\n metrics.clicks,\n metrics.impressions,\n metrics.ctr,\n metrics.average_cpc,\n metrics.cost_micros,\n metrics.absolute_top_impression_percentage,\n metrics.top_impression_percentage,\n metrics.average_cpm\n FROM customer\n WHERE segments.date DURING LAST_7_DAYS\n\nCommon differences\n------------------\n\nWhen comparing UI reports to API reports, one of the most common differences is\nthat the UI implicitly filters out removed entities, whereas the API does not.\n\nIn order to replicate a default UI view, you need to add a filter, typically\nusing a `status` field, to exclude removed rows. For example: \n\n SELECT campaign.name\n FROM campaign\n WHERE campaign.status != \"REMOVED\""]]