View or download files that support the RTB Protocol.

## Protos

**Important:** When you download a `proto` file, you must rename it, replacing `-proto.txt` with `.proto`.

| File | Description | Version | Last Updated |
|---|---|---|---|
| [cookie-bulk-upload.proto](https://developers.google.com/authorized-buyers/rtb/downloads/cookie-bulk-upload-proto) | Use this message to bulk upload user targeting data. | v.25 | Mar 27, 2024 |
| [openrtb.proto](https://developers.google.com/authorized-buyers/rtb/downloads/openrtb-proto) | Google supports the OpenRTB protocol, using either JSON or Protobuf encoding. This proto is necessary if you use OpenRTB/Protobuf. It also includes documentation of supported fields and their mapping to Google's native protocol. | 2.6 | Oct 15, 2026 |
| [openrtb-adx.proto](https://developers.google.com/authorized-buyers/rtb/downloads/openrtb-adx-proto) | Google's OpenRTB protocol includes some extensions, provided in a separate proto. | v.210 | Aug 04, 2026 |
| [publisher-settings.proto](https://developers.google.com/authorized-buyers/rtb/downloads/publisher-settings-proto) | A set of publisher settings specific to a real-time bidder network. | v.14 | Feb 05, 2024 |

## Open Beta Protos

The open beta protocols contain features that are likely to be included in the official protocols in the future. These protocols are subject to more frequent changes, and are made available to allow for public testing.

| File | Description | Version | Last Updated |
|---|---|---|---|
| [openrtb-adx.proto](https://developers.google.com/authorized-buyers/rtb/downloads/open-beta/openrtb-adx-proto) | Google's OpenRTB protocol includes some extensions, provided in a separate proto. | v.220 | Sep 16, 2026 |

## Reference data

| ### Dictionaries (Click to download .txt file) ||
|---|---|
| [Ad product categories](https://storage.googleapis.com/adx-rtb-dictionaries/ad-product-categories.txt) | Used in the `excluded_product_category` field of `BidRequest`. This field describes categories of products and services that are not allowed by a publisher, for example, if the publisher doesn't want to host ads related to online banking. |
| [Ad restricted categories](https://storage.googleapis.com/adx-rtb-dictionaries/ad-restricted-categories.txt) | Used in the `allowed_restricted_category` field of `BidRequest` and the `restricted_category` field of `BidResponse`. The `allowed_restricted_category` field describes categories that are normally restricted, but explicitly declared by a publisher as allowed, for example, ads containing alcohol-related content. |
| [Ad sensitive categories](https://storage.googleapis.com/adx-rtb-dictionaries/ad-sensitive-categories.txt) | Used in the `excluded_sensitive_category` field of `BidRequest` and the `category` field of `BidResponse`. The `excluded_sensitive_category` field describes sensitive categories that are not allowed by the publisher, for example, if the publisher does not want to host ads related to politics. |
| [Advertisers](https://storage.googleapis.com/adx-rtb-dictionaries/advertisers.txt) | Used in the `advertiser_id` field of SnippetStatusItem. This field specifies the advertiser represented by the creative associated with the snippet. This list reflects advertisers across the exchange and does not reflect the advertisers represented by any one buyer. |
| [Brands](https://storage.googleapis.com/adx-rtb-dictionaries/brands.txt) | List of brands, used in the Client Access API. |
| [Buyer declarable creative attributes](https://storage.googleapis.com/adx-rtb-dictionaries/buyer-declarable-creative-attributes.txt) | Used for the `attribute` field in `BidResponse`. This field describes buyer-declarable attributes on creatives which must not appear in `excluded_attribute` in `BidRequest`. |
| [Content labels](https://storage.googleapis.com/adx-rtb-dictionaries/content-labels.txt) | Used in the `detected_content_labels` field of the `BidRequest`. |
| [Cookie matcher status codes](https://storage.googleapis.com/adx-rtb-dictionaries/cookie-matcher-status-codes.txt) | Used in the `cookieMatcherStatusRate` field of RTB Protocol performance reports. Available codes are described in the [Cookie matching](https://developers.google.com/authorized-buyers/rtb/cookie-guide#status) guide. |
| [Creative status codes](https://storage.googleapis.com/adx-rtb-dictionaries/creative-status-codes.txt) | Used in `creative_status_code` returned in [real-time feedback](https://developers.google.com/authorized-buyers/rtb/request-guide#real-time-feedback). |
| [Hosted match status codes](https://storage.googleapis.com/adx-rtb-dictionaries/hosted-match-status-codes.txt) | Used in the `hostedMatchStatusRate` field of RTB Protocol performance reports. |
| [No bid reasons](https://developers.google.com/static/authorized-buyers/rtb/downloads/no-bid-reasons.txt) | Standard no-bid reason values to be given in the `BidResponse.no_bid_reason` field in the Authorized Buyers bid protocol. |
| [Pretargetable creative attributes](https://storage.googleapis.com/adx-rtb-dictionaries/pretargetable-creative-attributes.txt) | Used in the `supportedCreativeAttribute` field in the PretargetingConfig resource exposed in the Buyer REST API. This field describes creative attributes expected to be present in all creatives corresponding to a single pretargeting configuration. |
| [Publisher-excludable creative attributes](https://storage.googleapis.com/adx-rtb-dictionaries/publisher-excludable-creative-attributes.txt) | Used in the `excluded_attribute` field of `BidRequest`. This field describes the types of creatives that are not allowed by the publisher. For example, they might specify restrictions on whether cookie usage is allowed, or whether media and/or text ads are allowed. |
| [Vendors](https://storage.googleapis.com/adx-rtb-dictionaries/vendors.txt) | Used in the `allowed_vendor_type` field of `BidRequest`. This field lists which Rich Media vendors, such as Campaign Monitor and VoiceFive, are allowed for the creative being served, as specified by the publisher. Includes vendors from the sunsetted `gdn-vendors.txt` dictionary file. |
| [Data providers](https://storage.googleapis.com/adx-rtb-dictionaries/data_providers.txt) | Used in the `SegmentData.id` field of `BidRequest`. This field contains information on the entity that provided the [Publisher Provided Signals](https://support.google.com/admanager/answer/12451124). |
| [Android mobile apps](https://storage.googleapis.com/adx-rtb-dictionaries/android_apps.csv) | List of targetable Android mobile apps with their app IDs, category IDs, and human-readable app names. |
| [Geo tables](https://storage.googleapis.com/adx-rtb-dictionaries/geo-table.csv) | The table used to decode the `geo_criteria_id` field of `BidRequest`. Refer to [Geotargeting](https://developers.google.com/authorized-buyers/rtb/geotargeting) for more information. |
| [LGPD Providers](https://storage.googleapis.com/adx-rtb-dictionaries/lgpd-providers.csv) | The list of ads personalization providers allowed to serve on LGPD traffic, with their ID, a human readable name, privacy URL, and a list of domains which can be attributed to the provider. LGPD enforcement is indicated on a given bid request through the `BidRequest.adslot.regs_lgpd` field in the Authorized Buyers bid protocol and the `BidRequest.regs.ext.lgpd` field in the OpenRTB bid protocol. |
| [Mobile carriers](https://storage.googleapis.com/adx-rtb-dictionaries/mobile-carriers.csv) | List of mobile carriers. |
| [Mobile devices](https://storage.googleapis.com/adx-rtb-dictionaries/mobile-devices.csv) | List of mobile devices. |
| [Mobile operating systems](https://storage.googleapis.com/adx-rtb-dictionaries/mobile-os.csv) | List of mobile operating systems. |
| [Providers](https://storage.googleapis.com/adx-rtb-dictionaries/providers.csv) | Maps ads personalization provider IDs to a human readable name, a privacy policy URL, and a list of domains which can be attributed to the provider. Currently, providers are used in the `BidRequest.AdSlot.consented_providers_settings` field for AdX protocol and `BidRequest.User.UserExt.consented_providers_settings` for OpenRTB protocol. In these fields, the listed providers have user consent as passed by publishers for users in the countries within the European Economic Area. |

### Publisher settings

Request the `publisher-settings.pb.gz` file from your account
representative.

### Creative review policy topics


You can use the policy topics in this file to filter creatives during
[review](https://developers.google.com/authorized-buyers/apis/guides/rtb-api/buyer-creatives#submit_creatives_for_review) in the [Real-time Bidding API](https://developers.google.com/authorized-buyers/apis/guides/rtb-api/overview)
[Download
policy topics as a CSV file.](https://developers.google.com/static/authorized-buyers/rtb/downloads/creative-policy-topics.csv)


*Last updated: April 18, 2022*