Stay organized with collections
Save and categorize content based on your preferences.
Google makes aggregated publisher settings lists available by uploading them
to an account-specific Google Cloud Storage bucket (under a project that is
owned by Google). You can download these to use for targeting that cannot be
done at bidding time. Talk to your technical account manager to enable
this feature for your account.
The files containing publisher settings can be downloaded programmatically
by using the Cloud Storage
API, manually through the Google Developer
Console UI, or by using the gsutil command-line tool.
See the Google Cloud
Storage documentation for more details about accessing data stored in
Google Cloud Storage.
The file is gzip-compressed according to RFC 1952. To extract the file from
the command line, run gzip -d <filename>. To extract the
file programmatically, you can use zlib or a similar compression library that
supports gzip format. The result is a serialized protocol buffer, similar to
the payload of the POST request in a BidRequest, which can be
parsed with the following snippet:
The protocol buffer definition for PublisherSettingsList can be
downloaded from the reference data
page. You can also request a compressed
publisher-settings.pb.gz file from your account representative. It
contains the protocol buffer definition as well as an example publisher
settings file.
The ordering of PublisherSettingsList can change at any time.
No specific order or sorting is guaranteed. Each entry in the publisher
settings list contains an identifier, and several settings that apply to
BidRequests tagged with that identifier. You can add a feature to
your bidding systems to periodically check for a new publisher settings list.
When Google receives an impression that is eligible for real-time bidding,
Google includes identifiers in the bid request that correspond to entries in
the publisher settings list. Your bidding system can use the publisher settings
to filter the candidate ads for that impression. To be eligible for a given
impression, the candidate ad must comply with all the publisher setting entries
for which identifiers were sent in the request.
Note that any missing publisher settings from the file are
due to the identifiers not having blocked URLs associated with them.
The publisher settings file is broken into multiple smaller files to reduce
the amount of data that must be downloaded in a single transaction. The files
are broken into approximately 5 MB chunks and names as
publisher-settings.0.pb.gz through
publisher-settings.n.pb.gz (where n is the number of
files minus one.) Contact your account representative to obtain these
files.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-18 UTC."],[[["\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,["Google 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."]]
