We're excited to announce the launch of the new Google Advertising and Measurement Developers Hub!

Come see the new site!

Whether you're looking to automate campaigns, analyze performance, manage tags, or monetize your apps, the new hub is designed to make it easier to find the right tools and information.

We've launched a new technical-user focused site to make it easier than ever for you to find the tools, resources, and support you need to build and innovate with Google's advertising and measurement products.

What's New?

We have created a one-stop shop where you can easily find the resources you need, connect with our team and the community, and get support. Here are some key features:

• At-a-glance homepage: A clear starting point highlighting how we can help, with quick links to our blog, Discord, and information about our team.
• Meet the team: Learn more about the Developer Relations team dedicated to supporting your success.
• Products: A comprehensive directory of the developer products we cover, from the Google Ads API and Google Analytics APIs to Publisher Tools like AdMob and Ad Manager, linking directly to their official documentation. You can browse by categories like Advertising Platforms, Tagging, Measurement & Analytics, and Publisher Tools.
• Connect with us: A streamlined page to help you find the best way to engage:
  • Join our vibrant Discord community.
  • Find links to product or technical support.
  • Download open source projects on GitHub.
• Media and podcast: A new home for our multimedia content, including the Ads DevCast playlist embedded directly on the page.

We're excited to make this the place for you to learn, build, and connect.

Please explore the new site and use the Send Feedback button located at the bottom of each page to share your thoughts!

If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Happy Building!

- Aalap Shastri, Google Ads API Team

Starting today, Google’s OpenRTB implementation will be updated to only include fields and messages for the latest supported version, OpenRTB 2.5. This will affect the OpenRTB protocol and any APIs or tools used to configure bidder endpoints.

OpenRTB protocol changes
As a result of supporting only the latest version, the following fields are deprecated and will no longer be populated:

• BidRequest.imp[].banner.hmax
• BidRequest.imp[].banner.hmin
• BidRequest.imp[].banner.wmax
• BidRequest.imp[].banner.wmin

Additionally, the following fields may now be populated for all bidders:

• BidRequest.device.ext.user_agent_data
• BidRequest.device.geo.accuracy
• BidRequest.device.geo.utcoffset
• BidRequest.imp[].banner.api: This will support the value MRAID_3.
• BidRequest.imp[].banner.format
• BidRequest.imp[].banner.vcm
• BidRequest.imp[].metric
• BidRequest.imp[].native.api: This will support the value MRAID_3.
• BidRequest.imp[].video.api: This will support the value MRAID_3.
• BidRequest.imp[].video.companionad.api
• BidRequest.imp[].video.companionad.format
• BidRequest.imp[].video.companionad.vcm
• BidRequest.imp[].video.linearity
• BidRequest.imp[].video.maxduration
• BidRequest.imp[].video.placement
• BidRequest.imp[].video.playbackend
• BidRequest.imp[].video.skip
• BidRequest.site.mobile
• BidRequest.test
• BidRequest.wlang

If a newer OpenRTB specification is published, Google may upgrade the current supported version to match it. Previously deprecated fields that are removed from the specification will also be removed from the protocol. Non-deprecated fields that are removed will be marked as deprecated in the protocol, and eventually removed following a brief deprecation period.

Authorized Buyers Real-time Bidding API changes
The behavior of the bidders.endpoints resource will change. The following enum values for bidProtocol will be deprecated:

• OPENRTB_2_2
• OPENRTB_2_3
• OPENRTB_PROTOBUF_2_3
• OPENRTB_2_4
• OPENRTB_PROTOBUF_2_4
• OPENRTB_2_5
• OPENRTB_PROTOBUF_2_5

New enum values for bidProtocol will be added to represent the latest supported OpenRTB version in either JSON or Protobuf formats:

• OPENRTB_JSON
• OPENRTB_PROTOBUF

If you have existing endpoints with their bidProtocol set to any of the deprecated values above, they will automatically be migrated to either OPENRTB_JSON or OPENRTB_PROTOBUF depending on the format specified by the original value. Additionally, any modifications to your endpoints that would set bidProtocol to the deprecated values will instead set it to OPENRTB_JSON or OPENRTB_PROTOBUF.

Feel free to reach out to us via the Authorized Buyers API support forum with any feedback or questions you may have related to these changes.
- Mark Saniscalchi, Authorized Buyers Developer Relations