최종 사용자 개인 정보를 보호하는 방법으로 집계되지 않았거나 Ads Data Hub의 다른 개인 정보 보호 검사를 통과하지 못하는 행은 지정된 쿼리의 결과에서 삭제됩니다. 분석 쿼리에서 필터링된 행 요약을 구성하여 상수와 삭제된 행의 합계가 포함된 단일 행을 반환할 수 있습니다.
이렇게 하면 총노출수 또는 총클릭수와 같은 데이터 총계의 불일치를 방지할 수 있습니다. 필터링된 행 요약은 UI를 사용하여 만든 새 분석 쿼리의 경우 기본적으로 사용 설정됩니다. 필터링된 행 요약은 잠재고객 쿼리에 적용되지 않습니다. API를 사용하여 만든 쿼리에는 기본적으로 필터링된 행 요약이 사용 설정되지 않습니다.
예
다음 예에서는 캠페인 124와 125가 포함된 행이 사용자 50명의 집계 요구사항을 충족하지 않으므로 필터링됩니다.
캠페인 ID
사용자
123
400
124
45
125
6
하지만 필터링된 행 요약을 사용하면 필터링된 데이터를 결합하여 사용자 50명의 집계 요구사항을 충족할 수 있습니다. 이 예에서는 합계를 사용하여 필터링된 데이터를 집계하고 상수를 사용하여 행에 라벨을 지정합니다.
Users 열에서 필터링된 데이터를 집계하는 합계
상수(필터링된 행 요약에 라벨을 지정하는 데 사용됨), Campaign ID 열에서 '필터링된 행 요약'으로 설정됨
캠페인 ID
사용자
필터링된 행 요약
51
123
400
자동 모드
자동 모드를 사용하는 것이 좋습니다. 기본적으로 Ads Data Hub에서는 UI를 사용하여 만든 새 쿼리의 경우 필터링된 행 요약을 자동으로 사용 설정하고 구성합니다. 쿼리를 수정하면 Ads Data Hub에서 선택한 열을 기반으로 구성을 자동으로 조정합니다.
보고서를 볼 때 자동으로 구성된 설정을 보려면 수정수정을 클릭합니다. 이 구성은 읽기 전용입니다.
자동 모드를 사용 중지하려면 자동 전환 버튼을 클릭하여 사용 중지 위치로 전환합니다. 현재 구성이 유지되고 자동 모드가 사용 중지됩니다. 변경사항을 유지하려면 쿼리를 저장해야 합니다.
자동 모드를 사용 설정하려면 자동 전환 버튼을 클릭하여 사용 위치로 전환합니다.
변경사항을 유지하려면 쿼리를 저장해야 합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eAds Data Hub uses a filtered row summary to prevent discrepancies in data totals by aggregating data from rows that would otherwise be dropped due to privacy checks.\u003c/p\u003e\n"],["\u003cp\u003eFiltered row summaries are enabled by default for new analysis queries created via the UI but must be manually enabled for queries created via the API.\u003c/p\u003e\n"],["\u003cp\u003eAggregation requirements still apply to the filtered row summary; if the summary itself falls below the thresholds, it will be dropped, but a warning will appear in the job status.\u003c/p\u003e\n"],["\u003cp\u003eYou can manually configure filtered row summaries by adding rules to specify how columns should be aggregated (sum or constant) for the summary row.\u003c/p\u003e\n"],["\u003cp\u003eWhen exporting multiple tables using in-sql syntax, you can add a filtered row summary using column options like \u003ccode\u003emerge_type\u003c/code\u003e and \u003ccode\u003emerge_constant\u003c/code\u003e.\u003c/p\u003e\n"]]],["Filtered row summaries aggregate data from rows dropped due to privacy checks, preventing discrepancies in totals. These summaries, enabled by default in UI-created analysis queries, combine filtered rows using sums and constants. Automatic mode configures summaries dynamically, while manual mode allows custom setup via sums and constant labels. For multiple tables, `merge_type` sums values and `merge_constant` sets a value in the summary. If the resulting summary fails privacy checks, it's also filtered, but with a warning. Using noise instead of difference checks can make filtered row summary unnecessary.\n"],null,["# Filtered row summary\n\n\u003cbr /\u003e\n\nRows that aren't adequately aggregated to protect end-user privacy, or don't\nmeet Ads Data Hub's other [privacy\nchecks](/ads-data-hub/marketers/guides/privacy-checks), will be dropped from the\nresults of a given query. You can configure a filtered row summary in analysis\nqueries to return a single row containing constants and sums from dropped rows.\nThis can help prevent discrepancies in your data totals, such as a total\nimpression or total click count. A filtered row summary is enabled by default\nfor new analysis queries created using the UI. Filtered row summaries don't\napply to audience queries. Queries created using the API don't have a filtered\nrow summary enabled by default.\n| **Key Point:** We recommend using noise instead of difference checks when you run your reports. When you use noise, rows are not filtered due to difference checks, making a filtered row summary unnecessary. To learn more, see [Noise\n| injection](/ads-data-hub/marketers/guides/noise-injection).\n| **Important:** Aggregation requirements still apply to filtered row summary columns. If the resulting filtered row summary contains fewer than 50 users, or fewer than 2 rows, the filtered row summary itself will be filtered. However, a message will appear in your job status summary warning you that the filtered row summary was filtered.\n\n### Example\n\nIn the following example, the rows containing campaigns 124 and 125 would be\nfiltered, as they don't meet the 50-user aggregation requirement.\n\n| Campaign ID | Users |\n|-------------|-------|\n| 123 | 400 |\n| 124 | 45 |\n| 125 | 6 |\n\nHowever, using a filtered row summary, the filtered data can be combined to meet\nthe 50-user aggregation requirement. This example uses a sum to tally filtered\ndata, and a constant to label the row:\n\n- A sum that aggregates filtered data from the `Users` column.\n- A constant (used to label the filtered row summary), set to \"Filtered row summary\" in the `Campaign ID` column.\n\n| Campaign ID | Users |\n|----------------------|-------|\n| Filtered row summary | 51 |\n| 123 | 400 |\n\nAutomatic mode\n--------------\n\nWe recommend using automatic mode. By default, Ads Data Hub automatically\nenables and configures a filtered row summary for new queries created using the\nUI. As you edit the query, Ads Data Hub will automatically adjust the\nconfiguration, based on the selected columns.\n\n- To view the automatically configured settings when viewing a report, click edit **Edit**. The configuration is read-only.\n- To disable automatic mode, click the **Automatic** toggle to the off position. The current configuration is retained and automatic mode is disabled. You must save your query to retain the change.\n- To enable automatic mode, click the **Automatic** toggle to the on position. You must save your query to retain the change.\n- To toggle automatic mode with the API, use [`generateFilteredRowSummaryAutomatically`](/ads-data-hub/marketers/reference/rest/v1/customers.analysisQueries#resource:-analysisquery).\n\nManual mode\n-----------\n\nWe recommend using automatic mode. To manually add a filtered row summary\nto a saved query, or after disabling automatic mode:\n\n1. In Ads Data Hub, open the Reports page.\n2. Click the name of the report you want to edit.\n3. Click edit **Edit** next to **Filtered row summary automatically generated**.\n4. Click the **Automatic** toggle to the off position. Note: When automatic mode is disabled, the current configuration is retained. Edit or delete these rules as needed.\n5. Aggregate a column using a sum. Note that if the sum falls below aggregation thresholds, the filtered row summary will be dropped.\n 1. Click **Add rule**\n 2. Enter the name of the column to aggregate in the **Column name** field.\n 3. Select **Sum** from the **Type** list.\n6. Add a label for the filtered row summary using a constant. Your constant must be a valid data type for your chosen column.\n 1. Click **Add**.\n 2. Decide in which column of the filtered row summary you want the identifier to appear, then enter the name of that column in the **Column\n name** field.\n 3. Select **Constant** from the **Type** list.\n 4. Enter a helpful identifier for the row, such as \"Filtered row summary\", in the **Specify constant** field.\n7. Click **Done**.\n8. Click **Save** to commit your changes. \n\nManual mode with multiple tables\n--------------------------------\n\nWe recommend using automatic mode. If you are exporting multiple tables using\nthe in-sql syntax introduced in [Exporting multiple\ntables](/ads-data-hub/marketers/guides/create-tables#export_multiple_tables), then you can add a filtered\nrow summary in the column options: \n\n```gdscript\nCREATE TABLE `myproject.mydataset.mytable` (\n campaign_id INT64 OPTIONS(merge_constant=0),\n ct INT64 OPTIONS(merge_type=\"SUM\")\n )\nOPTIONS(privacy_checked_export=true) AS\nSELECT campaign_id, COUNT(*) AS ct GROUP BY campaign_id;\n \n```\n\nThis will produce a result table with a filtered row summary where\nthe `campaign_id` is `0` and `ct` will be the sum of rows that were filtered from the result due to privacy checks.\n\nThe available column options for filtered-row summary are:\n\n- `merge_type=\"SUM\"`: Outputs the sum of filtered values in the summary row.\nValid only for numeric types.\n- `merge_constant=\u003cvalue\u003e`: Sets a constant value in the summary row. Must have same type as the column.\n- columns with no specified option will have NULL in the summary row.\n\nOnly one of `merge_type` or `merge_constant` may be specified.\nAny rules for filtered row summaries apply here, too (i.e. if the sum falls\nbelow the aggregation thresholds, the filtered row summary will be dropped)."]]