RTB 發布商設定
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Google 透過上傳發布商設定清單的方式提供匯總清單
連結至帳戶專屬的 Google Cloud Storage 值區 (在
Google 所有)。您可以下載這些檔案，用於無法指定
出價時完成的調查若要啟用，請與客戶技術顧問聯絡
這項功能就會在您的帳戶中生效
包含發布商設定的檔案可透過程式下載
使用 Cloud Storage
API (可手動透過 Google Developers 應用程式)
控制台 UI，或使用 gsutil 指令列工具。
請參閱 Google Cloud
儲存空間說明文件，進一步瞭解如何存取儲存在 Google Cloud 服務中的資料
Google Cloud Storage
檔案是採用 gzip 壓縮格式，符合 RFC 1952 標準。從
執行 gzip -d <filename>如要擷取
藉由編寫程式，您可以使用 zlib 或類似壓縮程式庫
支援 gzip 格式結果會產生序列化的通訊協定緩衝區，類似
BidRequest 中的 POST 要求酬載，請
是使用以下程式碼片段剖析：
string compressed = /* the payload from the GET request */;
string uncompressed = gunzip(compressed);
PublisherSettingsList publisher_settings;
if (publisher_settings.ParseFromString(uncompressed)) {
// Process the publisher settings.
}
PublisherSettingsList 的通訊協定緩衝區定義可以
從參考資料資料中下載
頁面。你也可以要求壓縮
publisher-settings.pb.gz 檔案。這項服務
包含通訊協定緩衝區的定義以及範例發布者
設定檔
PublisherSettingsList 的順序可隨時變更。
不保證會依照特定順序或排序。發布商中的每個項目
設定清單包含識別碼，以及
BidRequests 會標上該 ID。您可以在
出價系統會定期檢查新的發布商設定清單。
當 Google 收到可用於即時出價的曝光時，
Google 會在出價要求中加入與
發布商設定清單您的出價系統可以使用發布商設定
篩選該次曝光的候選廣告必須符合特定條件
候選廣告必須遵守所有發布商設定項目
以及要求中傳送的 ID
請注意，檔案中任何缺少的發布商設定，
，因為 ID 沒有封鎖相關的網址。
將發布商設定檔案拆分為多個較小的檔案，以便減少檔案數量
每筆交易必須下載的資料量。這些檔案
可分為約 5 MB 區塊和名稱
publisher-settings.0.pb.gz 到
publisher-settings.n.pb.gz (n 是
減 1)。請與您的帳戶代表聯絡，以取得這些
檔案。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-21 (世界標準時間)。
[null,null,["上次更新時間：2025-08-21 (世界標準時間)。"],[[["\u003cp\u003eGoogle provides aggregated publisher settings lists via a Google Cloud Storage bucket for account-specific use, enabling targeting adjustments beyond bidding time.\u003c/p\u003e\n"],["\u003cp\u003eThese publisher settings files can be accessed programmatically using the Cloud Storage API, manually through the Google Developer Console UI, or via the gsutil command-line tool.\u003c/p\u003e\n"],["\u003cp\u003eThe files are gzip-compressed and contain a serialized protocol buffer that can be decompressed using commands like \u003ccode\u003egzip -d <filename>\u003c/code\u003e or with zlib-like libraries.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePublisherSettingsList\u003c/code\u003e protocol buffer definition, which provides details about the settings and an example file, can be downloaded from the reference data page or requested from your account representative.\u003c/p\u003e\n"],["\u003cp\u003ePublisher settings are split into multiple smaller, approximately 5 MB files, named \u003ccode\u003epublisher-settings.0.pb.gz\u003c/code\u003e through \u003ccode\u003epublisher-settings.n.pb.gz\u003c/code\u003e, to ease downloading.\u003c/p\u003e\n"]]],["Google provides aggregated publisher settings lists in account-specific Google Cloud Storage buckets. These files, compressed in gzip format, can be downloaded programmatically via the Cloud Storage API, manually through the Google Developer Console, or using the `gsutil` tool. They contain serialized protocol buffers that can be parsed to extract settings. Bidding systems can utilize these settings to filter ads based on identifiers included in bid requests. Files are split into ~5MB chunks. Missing settings are due to lack of associated blocked URLs.\n"],null,["# RTB Publisher Settings\n\nGoogle makes aggregated publisher settings lists available by uploading them\nto an account-specific Google Cloud Storage bucket (under a project that is\nowned by Google). You can download these to use for targeting that cannot be\ndone at bidding time. Talk to your technical account manager to enable\nthis feature for your account.\n\nThe files containing publisher settings can be downloaded programmatically\nby using the [Cloud Storage\nAPI](//cloud.google.com/storage/docs/json_api/v1/libraries), manually through the [Google Developer\nConsole](//cloud.google.com/storage/docs/cloud-console) UI, or by using the [gsutil](//cloud.google.com/storage/docs/gsutil) command-line tool.\nSee the [Google Cloud\nStorage](//cloud.google.com/storage/docs/overview) documentation for more details about accessing data stored in\nGoogle Cloud Storage.\n\nThe file is gzip-compressed according to [RFC 1952](//www.ietf.org/rfc/rfc1952.txt). To extract the file from\nthe command line, run `gzip -d \u003cfilename\u003e`. To extract the\nfile programmatically, you can use zlib or a similar compression library that\nsupports gzip format. The result is a serialized protocol buffer, similar to\nthe payload of the POST request in a `BidRequest`, which can be\nparsed with the following snippet: \n\n```gdscript\nstring compressed = /* the payload from the GET request */;\nstring uncompressed = gunzip(compressed);\nPublisherSettingsList publisher_settings;\nif (publisher_settings.ParseFromString(uncompressed)) {\n // Process the publisher settings.\n}\n```\n\nThe protocol buffer definition for `PublisherSettingsList` can be\ndownloaded from the [reference data\npage](/authorized-buyers/rtb/data). You can also request a compressed\n`publisher-settings.pb.gz` file from your account representative. It\ncontains the protocol buffer definition as well as an example publisher\nsettings file.\n\nThe ordering of `PublisherSettingsList` can change at any time.\nNo specific order or sorting is guaranteed. Each entry in the publisher\nsettings list contains an identifier, and several settings that apply to\n`BidRequests` tagged with that identifier. You can add a feature to\nyour bidding systems to periodically check for a new publisher settings list.\nWhen Google receives an impression that is eligible for real-time bidding,\nGoogle includes identifiers in the bid request that correspond to entries in\nthe publisher settings list. Your bidding system can use the publisher settings\nto filter the candidate ads for that impression. To be eligible for a given\nimpression, the candidate ad must comply with all the publisher setting entries\nfor which identifiers were sent in the request.\n\nNote that any missing publisher settings from the file are\ndue to the identifiers not having blocked URLs associated with them.\n\nThe publisher settings file is broken into multiple smaller files to reduce\nthe amount of data that must be downloaded in a single transaction. The files\nare broken into approximately 5 MB chunks and names as\n`publisher-settings.0.pb.gz` through\n`publisher-settings.n.pb.gz` (where \u003cvar translate=\"no\"\u003en\u003c/var\u003e is the number of\nfiles minus one.) Contact your account representative to obtain these\nfiles."]]
