Tag Archives: deprecation

June 2025 changes to Display & Video 360 API and Structured Data Files

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

June 2025 changes to Display & Video 360 API and Structured Data Files

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

June 2025 changes to Display & Video 360 API and Structured Data Files

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

June 2025 changes to Display & Video 360 API and Structured Data Files

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

June 2025 changes to Display & Video 360 API and Structured Data Files

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Deprecation of Structured Data Files v7

Today we’re announcing the deprecation of Structured Data Files (SDF) v7. This version will sunset on November 4, 2025.

Migrate to SDF v7.1 or higher before the sunset date to avoid any interruption of service. See the differences between SDF v7 and v7.1 in the v7.1 release notes.

After November 4, 2025, the following changes will apply to all users:

If you run into issues or need help with your migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Deprecation of Display & Video 360 API v3

Today, we are deprecating Display & Video 360 API v3. We will sunset v3 on October 7, 2025. Please migrate to Display & Video 360 API v4 before the sunset date to avoid an interruption of service.

New features will not be added to v3 now that it is deprecated. All new feature releases will target v4 exclusively. Read our release notes for more information on updates made to the API in v4 and see our GitHub repository for new code samples using v4. Follow the steps in our v4 migration guide to migrate.

If you run into issues or need help with this new version, please follow the instructions in our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing Android Google Mobile Ads SDK version 24.0.0

Version 24.0.0 of the Android Google Mobile Ads SDK is now available. To take advantage of the latest features and performance improvements, we highly recommend you configure your app to upgrade as soon as possible. Major changes to the SDK are as follows:

Minimum Android API level

Starting with version 24.0.0, the Google Mobile Ads SDK requires all apps to be on a minimum Android API level of 23. To adjust the API level, change the value of minSdk in your app-level build.gradle file to 23 or higher.

Optimized initialization and ad loading

By default, The OPTIMIZE_INITIALIZATION and OPTIMIZE_AD_LOADING flags are now generally available and set to true. These flags help reduce ANRs. You can further prevent ANRs by initializing the Google Mobile Ads SDK on a background thread. For more information, see Optimize initialization and ad loading.

Removed ad services config in AndroidManifest.xml

To prevent merge conflicts for apps that configure API-specific Ad Services, we've removed the android.adservices.AD_SERVICES_CONFIG property tag from the SDK’s manifest file. This change provides greater flexibility for developers who need to customize their Ad Services configurations.

SDK deprecation and sunset timelines activated

With this Android major version 24 launch and the iOS major version 12 launch last month, new deprecation and sunset dates for older releases are as follows:

  • Android Google Mobile Ads SDK versions 22.0.0 - 22.6.0 are officially deprecated, and will sunset in June 2026.
  • Android versions 21.x.x and iOS versions 9.x.x will sunset on June 30, 2025.
    • While there are currently no plans to disable ad serving on Android versions 21.x.x and iOS versions 9.x.x, we strongly recommend updating to the latest SDK version to avoid future impactions.

For a complete list of changes in v24.0.0 and detailed migration steps, check the release notes and SDK migration guide. If you have any questions or need additional help, contact us through Mobile Ads SDK Support.

 - Eric Leichtenschlag, Mobile Ads Developer Relations

Spring 2025 changes to Display & Video 360 API and Structured Data Files

In the coming months, we will make changes to the Display & Video 360 API and Structured Data Files to improve API function and better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page. We recommend you review these individual changes that will take effect on the following dates: If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our new Display & Video 360 API Technical support contact form.
- Trevor Mulchay, Display & Video 360 API Team

Extending the deprecation period for the Authorized Buyers Real-time Bidding protocol

As part of our goal of aligning more closely with industry standards, we previously announced the sunset of the Authorized Buyers Real-time bidding protocol on February 15th, 2025. After the deprecation period, OpenRTB will be the only supported protocol for Authorized Buyers, Open Bidding, and SDK Bidding. Since the announcement, we have worked closely with migrating partners to provide guidance and technical assistance, as well as an A/B experimentation framework.

We have seen a lot of enthusiasm and progress from many partners migrating to OpenRTB, as well as significant improvements in bidding performance for a number of partners compared to Google RTB integrations. However, to provide additional support and further optimize bidding integrations with the OpenRTB protocol, we have decided to extend the Authorized Buyers Real-time Bidding protocol's deprecation period.

The sunset date is now April 30th, 2025. Following this date, bid requests will no longer be sent with the Authorized Buyers Real-time bidding protocol, and the only supported protocol will be OpenRTB.

If you have any questions about how OpenRTB differs from Authorized Buyers Real-time Bidding protocol, we recommend that you reference the OpenRTB migration guide. If you have other questions or feedback concerning your migration, feel free to contact us using the Authorized Buyers support forum, or [email protected].

- Mark Saniscalchi, Authorized Buyers Developer Relations