預先指定設定
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
出價方可以使用 pretargetingConfigs
資源,只接收符合指定條件的曝光的出價要求。您一次最多可有 10 個預先指定設定。
每項預先指定設定會將出價要求分配到所有端點。出價要求不一定會平均分配到所有端點。例如,對於特定地區中的特定地理區域 ID 的預先指定設定,相較於距離該地區較遠的「貿易地點」,其相符程度可能會減少。鄰近交易地點的端點可能會收到的出價要求較少。
最佳做法
您至少必須建立一項預先指定設定,才能接收出價要求。以下是管理預先指定設定的一些提示:
- 範圍
預先指定功能就像篩選。建議您使用預先指定條件,篩選出與您用途相關的出價要求。如果您並未設定任何預先指定條件,就可以收到所有曝光的出價要求。
如果特定預先指定設定的相關出價要求數量不足,建議您擴大預先指定條件。
- 邏輯
系統以邏輯 OR
處理頂層指定目標欄位中的值。也就是說,您收到的出價要求必須具有至少一個頂層欄位所指定的值。舉例來說,如果您的預先指定設定有 languageCodes
值為 en
、de
和 sv
,您可能會收到出價要求,而系統偵測到的語言為 en
、de
或 sv
。
系統以邏輯 AND
處理不同的欄位。在您所設定的每個預先指定欄位中,您只會收到至少符合一個值的出價要求。例如,如果您的設定有 languageCodes
值為 en
、de
和 sv
,而 includedPlatforms
值為 PERSONAL_COMPUTER
,您只會收到偵測到語言為 en
、de
或 sv
且裝置類型為 PERSONAL_COMPUTER
的出價要求。
由於預先指定欄位使用的邏輯 AND
,因此您無法加入衝突條件。例如,如果在 NumericTargetingDimensions
條件中加入相同的 includedIds
和 excludedIds
值,就會導致錯誤。
- 重疊
出價要求可適用於多項預先指定設定。
您最多可建立 10 個預先指定設定來指定不同類型的廣告空間。預先指定設定可能會重疊,因此單一出價要求可能符合多項預先指定設定的資格。在這種情況下,出價要求的 billing_id
欄位包含每個適用設定的 billingId
。如果出價要求中有多個帳單 ID,您必須在出價回應的 billing_id
欄位中指定要出價的帳單 ID。
地理區域 ID
基於政策原因,您無法指定部分地理區域 ID。舉例來說,某些人口較少的地區,因為違反我們的隱私權政策,因此無法做為指定目標。我們的政策可能會隨時變動。如果在預先指定設定的 geoTargeting
中指定地理區域 ID,而該 ID 之後會變成無效,則該 ID 會顯示在該時間的 invalidGeoIds
欄位下方。invalidGeoIds
底下的地理區域 ID 不會影響指定目標。如果 invalidGeoIds
中的持續性 ID 有效,系統會將該 ID 新增至預先指定設定的 geoTargeting
欄位。
geo-table.csv 檔案列出可指定的地理區域 ID,且會在新增及移除 ID 時定期更新。
出價要求數量
您應該為出價工具端點設定 QPS 上限,並允許呼叫配額系統管理針對每個預先指定設定,傳送至端點的流量。
在以下極端案例中,使用 maximumQps
在預先指定設定層級管理 QPS 上限可能會有幫助:
- 接收過多要求
- 如果呼叫配額系統針對特定預先指定設定,向出價方端點傳送異常大量的出價要求,您可以使用
maximumQps
手動調整要求數量。 - 測試新廣告空間的設定
- 如果想支援新的廣告空間 (例如新的廣告格式),可以只針對
maximumQps
較低的廣告空間導入預先指定設定。
對於由多個預先指定設定指定的廣告空間,只要至少一項設定未達到 maximumQps
限制,出價要求就會傳送給出價方的端點,包括各項設定的 billingId
。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-25 (世界標準時間)。
[null,null,["上次更新時間:2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eUse pretargeting configurations to filter bid requests and receive only relevant impressions, with the ability to create up to 10 configurations.\u003c/p\u003e\n"],["\u003cp\u003ePretargeting criteria use logical \u003ccode\u003eOR\u003c/code\u003e within fields and logical \u003ccode\u003eAND\u003c/code\u003e across fields, allowing for flexible but specific targeting.\u003c/p\u003e\n"],["\u003cp\u003eBid requests can match multiple pretargeting configurations, requiring bidders to specify the desired billing ID in their bid response.\u003c/p\u003e\n"],["\u003cp\u003eSome geographic IDs may be untargetable for policy reasons, and the \u003ccode\u003egeo-table.csv\u003c/code\u003e file provides a list of valid targetable IDs.\u003c/p\u003e\n"],["\u003cp\u003eManage bid request traffic using the Callout Quota System and \u003ccode\u003emaximumQps\u003c/code\u003e for specific pretargeting configurations when necessary.\u003c/p\u003e\n"]]],["Bidders use `pretargetingConfigs` to filter bid requests, receiving only those matching their criteria; up to 10 configurations are allowed. These configurations filter requests using logical `OR` within fields and logical `AND` across fields. Bid requests can match multiple configurations, identified by `billingId` in the request. Geographic targeting may have restrictions and invalid IDs are listed under `invalidGeoIds`. You can set `maximumQps` per configuration to manage traffic volume. At least one configuration is required to receive bid requests.\n"],null,["# Pretargeting configurations\n\nBidders can use the `pretargetingConfigs` resource to receive only bid\nrequests for impressions that match their targeting criteria.You can have up to\n10 pretargeting configurations at once.\n\nEach pretargeting configuration distributes bid requests across all endpoints.\nBid requests aren't always distributed evenly across all endpoints. For example,\na pretargeting configuration for specific geographic IDs in a given region might\nhave fewer matches in [trading\nlocations](/authorized-buyers/rtb/peer-guide#trading-locations) that are farther\nfrom that region. Endpoints near those farther trading locations might receive\nfewer bid requests.\n\nBest practices\n--------------\n\nIn order to receive bid requests, you must create at least one\npretargeting configuration. Here are some tips for managing your pretargeting\nconfigurations:\n\nScope\n\n: Pretargeting is like filtering. You should use pretargeting criteria to filter\n bid requests to those that are relevant to your use case. If you don't set any\n pretargeting criteria, you can receive bid requests for all impressions.\n\n If you aren't receiving enough bid requests related to a given pretargeting\n configuration, you might want to broaden your pretargeting criteria.\n\nLogic\n\n: Values in top-level targeting fields are processed with logical `OR`. This\n means you can receive bid requests that have at least one of the values you\n specify in the top-level field. For example, if your pretargeting\n configuration has `languageCodes` values `en`, `de`, and `sv`, you might receive\n bid requests with `en`, `de`, or `sv` as the detected language.\n\n Different fields are processed with logical `AND`. You only receive bid\n requests that have a match for at least one value in every pretargeting field\n you set. For example, if your configuration has `languageCodes` values `en`,\n `de`, and `sv`, and `includedPlatforms` value `PERSONAL_COMPUTER`, you receive\n only bid requests that have a detected language of `en`, `de`, or `sv` and a\n device type of `PERSONAL_COMPUTER`.\n\n Due to the logical `AND` across pretargeting fields, you can't include\n contradictory criteria. For example, including the same value in `includedIds`\n and `excludedIds` in a `NumericTargetingDimensions` criteria results in an\n error.\n\nOverlap\n\n: Bid requests can be eligible for multiple pretargeting configurations.\n\n You can create up to 10 pretargeting configurations to target different\n kinds of inventory. Pretargeting configurations can overlap, so a single bid\n request might be eligible for multiple pretargeting configurations. In this\n case, the bid request's `billing_id` field contains the `billingId` of\n each applicable configuration. If multiple billing IDs are found in the bid\n request, you must specify which billing ID you're bidding on in the bid\n response's `billing_id` field.\n\nGeographic IDs\n--------------\n\nSome geographic IDs aren't targetable for policy reasons. For example, some\nregions with small populations can't be targeted because it would violate our\nprivacy policy. Our policies are subject to change. If you specify\na geographic ID in your pretargeting configuration's `geoTargeting` that becomes\ninvalid at a later date, the ID appears under the `invalidGeoIds` field at that\ntime. Geographic IDs under `invalidGeoIds` have no impact on targeting. If a\ngoegraphic ID in `invalidGeoIds` becomes valid, it's added to your pretargeting\nconfiguration's `geoTargeting` field.\n\nThe\n[geo-table.csv](//storage.googleapis.com/adx-rtb-dictionaries/geo-table.csv)\nfile lists targetable geographic IDs, and is updated periodically as IDs are\nadded and removed.\n\nBid request count\n-----------------\n\nYou should configure the maximum QPS for your bidder endpoints,\nand allow the [Callout Quota System](/authorized-buyers/rtb/callout-quota-system)\nto manage the traffic sent to your endpoints for each of your pretargeting\nconfigurations.\n\nHere are edge cases where managing maximum QPS at the\npretargeting configuration level with `maximumQps` might be useful:\n\nReceiving too many requests\n: If the Callout Quota System is sending an unusually large number of bid\n requests to bidder endpoints for a given pretargeting configuration, you can\n use `maximumQps` to manually adjust the number of requests.\n\nTesting a configuration for new inventory\n: If you're trying to support new inventory, like a new creative format,\n you can implement a pretargeting configuration targeting only that inventory\n with a low `maximumQps`.\n\nFor inventory that's targeted by multiple pretargeting configurations,\nbid requests are sent to the bidder's endpoints, including the `billingId`\nfor each configuration, as long as at least one of the configurations hasn't\nreached its `maximumQps` limit."]]