实时出价工具发布商设置
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Google 通过上传汇总发布商设置列表来提供这些汇总信息
存储在特定账号的 Google Cloud Storage 存储分区中（位于
归 Google 所有）。您可以下载这些广告素材以用于无法
在出价时完成的转化操作如需启用此功能，请与您的技术支持客户经理联系
此功能
包含发布商设置的文件可以编程方式下载
使用Cloud Storage
API 手动通过 Google Developers
控制台界面，或者使用 gsutil 命令行工具。
请参阅 Google Cloud
Storage 文档，详细了解如何访问
Google Cloud Storage
文件根据 RFC 1952 采用 gzip 压缩格式。要从以下位置提取文件：
命令行中，运行 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。您可以向
让您的出价系统定期检查是否有新的发布商设置列表。
当 Google 收到符合实时出价条件的展示机会时
Google 会在出价请求中包含与
发布商设置列表您的出价系统可以使用发布商设置
以过滤相应展示的候选广告。有资格获得指定的
则候选广告必须符合所有的发布商设置条目，
哪些标识符在请求中发送过来。
请注意，如果此文件中缺少任何发布商设置，
原因是这些标识符未关联被屏蔽的网址
发布商设置文件已拆分为多个较小的文件
在单次事务中必须下载的数据量。文件
分为大约 5 MB 块，每个对象均以
publisher-settings.0.pb.gz到
publisher-settings.n.pb.gz（其中 n 是
文件减 1。）请联系您的客户代表获取这些信息
文件。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-21。
[null,null,["最后更新时间 (UTC)：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."]]
