Tag Archives: sunset

Bid Manager API v1.1 sunset reminder

As announced in August 2022, Bid Manager (DBM) API v1.1 will sunset on February 28, 2023. Please migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Google Ads API v10 sunset reminder

Google Ads API v10 will sunset on February 1, 2023. After this date, all v10 API requests will begin to fail. Please migrate to a newer version prior to February 1, 2023 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:
  1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
  2. Click on Google Ads API in the table.
  3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v10.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
  4. (Optional) Click on the time frame at the top right of the page if you need to change it.
If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
 - Thanet Knack Praneenararat, Google Ads API Team

Deprecation of New Smart Display Campaign Creation in the Google Ads API

We are removing the ability to create new Smart Display Campaigns in all versions of the Google Ads API. Version v12 already has these changes implemented.

On January 17, 2023 we will make a breaking change to all active versions of the Google Ads API older than v12, disallowing the creation of new Smart Display Campaigns in the API.

You will still be able to update your existing Smart Display Campaigns until they are auto-migrated in Q1 2023. For more information, please see this Help Center article.

Change Description
In all versions, after January 17, 2023, mutate operations to create a Smart Display Campaign (setting the AdvertisingChannelSubType to DISPLAY_SMART_CAMPAIGN) will throw an OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED error.

Next Steps
If you receive this error during Smart Display Campaign creation, you should create a Standard Display Campaign instead by leaving the optional AdvertisingChannelSubType field blank.

If you have any questions about this change or any other API feature, please contact us via the forum.
- Cory Liseno, Google Ads API Team

Deprecation of New Smart Display Campaign Creation in the Google Ads API

We are removing the ability to create new Smart Display Campaigns in all versions of the Google Ads API. Version v12 already has these changes implemented.

On January 17, 2023 we will make a breaking change to all active versions of the Google Ads API older than v12, disallowing the creation of new Smart Display Campaigns in the API.

You will still be able to update your existing Smart Display Campaigns until they are auto-migrated in Q1 2023. For more information, please see this Help Center article.

Change Description
In all versions, after January 17, 2023, mutate operations to create a Smart Display Campaign (setting the AdvertisingChannelSubType to DISPLAY_SMART_CAMPAIGN) will throw an OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED error.

Next Steps
If you receive this error during Smart Display Campaign creation, you should create a Standard Display Campaign instead by leaving the optional AdvertisingChannelSubType field blank.

If you have any questions about this change or any other API feature, please contact us via the forum.
- Cory Liseno, Google Ads API Team

Google Ads API 2023 release and sunset schedule

We’re announcing our tentative 2023 release and sunset schedule for upcoming versions of the Google Ads API to bring greater clarity to your planning cycle. Please keep in mind that these dates are only estimates and may be adjusted going forward. Additionally, releases may be added, removed or switched between major and minor.

Version Planned Release
Type* 		Projected launch* Projected sunset*
V13 Major January/February 2023 January 2024
V13_1 Minor April/May 2023 January 2024
V14 Major May/June 2023 May 2024
V14_1 Minor July/August 2023 May 2024
V15 Major September/October 2023 September 2024
*Estimated and subject to change

Where can I learn more?
Check back for any updates as the blog is the best place to stay informed about developments in this space.

If you have any questions or need additional help, contact us via the forum.
- David Stevens, Google Ads API Product Manager

Announcing a deprecation schedule for the Google Mobile Ads SDK

To provide Google Mobile Ads SDK developers for AdMob and Ad Manager more transparency and predictability on the expected lifetime of an SDK version, we are introducing a deprecation schedule for the Google Mobile Ads SDKs for Android and iOS.

Benefits

Introducing a predictable deprecation schedule offers the following benefits for app developers and publishers:

  1. Ability to predict and plan for SDK updates with a year of lead time.
  2. Legacy SDK code that only exists to support old versions can be deleted, thereby decreasing SDK size and lowering the risk of bugs.
  3. Engineering resources are freed up to focus more on support for newer SDKs and innovation of new SDK features.

Glossary

To understand the deprecation schedule, let’s first align the terms used to describe the state of a Google Mobile Ads SDK version:

SDK State Impact
Supported
Deprecated
  • Ads will still serve to this SDK.
  • Support questions specific to this SDK version are no longer answered on the Google Mobile Ads SDK developer forum. Users will be asked to validate the issue in a supported SDK version to receive full support.
Sunset
  • Ads will not serve to this SDK.
  • Ad requests return a no fill with an error indicating that this version is sunset.

Timelines

The deprecation and sunset timelines will revolve around major SDK version releases. We plan to do a major version release annually, in the first quarter of each year. The release of a new major version on both Android and iOS will trigger changes in SDK state for older major versions on both platforms.

Once we release a new major version N for both Android and iOS:

  • All SDK versions with major version N-2 on their respective platforms are considered deprecated immediately. Questions specific to these versions will no longer receive support.
  • All SDKs versions with major version N-3 on their respective platforms will sunset after 2 months.
    • We will publish subsequent blog posts communicating specific sunset dates to activate this two-month sunset period. The first sunset announcement is expected in Q1 2023 with a sunset date in Q2 2023.

With this schedule, a new major version will live in the supported state for about 2 years, and in the deprecated state for an additional year before moving to the sunset state.

The graphic below helps visualize the schedule:

How does the change apply to existing versions?

Effective today, Android v19 and iOS v7 versions are considered deprecated. In accordance with the schedule above, we plan to sunset Android v19 and iOS v7 versions in Q2 2023 following the releases of Android v22 and iOS v9 planned for Q1 2023. We will provide more specific sunset dates following the releases of Android v22 and iOS v9.

The graphic below helps visualize the state of existing Google Mobile Ads SDK versions for Android and iOS with today’s announcement.

Note: Versions 6.x.x and below for both Android and iOS have been sunset since 2018.

Exceptions

The deprecation schedule provides a framework for predictable lifetimes for an SDK version. However, there may be exceptions in the future. This schedule does not preclude us from sunsetting an SDK version at an earlier date, but we are committed to providing proactive communication with ample lead time for any future changes.

Next Steps

  1. Refer to the deprecation developer pages (Android | iOS) for the latest updates to the deprecation schedule. If you are on a deprecated version, see the Android migration guide or iOS migration guide for more information on how to update.
  2. Stay tuned for future updates to this blog, where more specific sunset dates will be communicated once new major Google Mobile Ads SDK versions are released.

If you have any questions about this announcement, please reach out to us on the Google Mobile Ads SDK Developer Forum.

 - Eric Leichtenschlag, Mobile Ads Developer Relations

Deprecation of Structured Data Files v5.2 and v5.3

Today we’re announcing the deprecation of the Structured Data Files (SDF) v5.2 and v5.3. These versions will be fully sunset on March 8, 2023.

Please migrate to v5.5, the most recent version, by the sunset date. Once the deprecated versions are sunset:

  • The default version of partners and advertisers using those versions will be updated to the oldest supported version, v5.4.
  • sdfdownloadtasks.create requests declaring the sunset versions in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Deprecation of Structured Data Files v5.2 and v5.3

Today we’re announcing the deprecation of the Structured Data Files (SDF) v5.2 and v5.3. These versions will be fully sunset on March 8, 2023.

Please migrate to v5.5, the most recent version, by the sunset date. Once the deprecated versions are sunset:

  • The default version of partners and advertisers using those versions will be updated to the oldest supported version, v5.4.
  • sdfdownloadtasks.create requests declaring the sunset versions in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Deprecation of Bid Manager API v1.1

Today we’re announcing the deprecation of the Bid Manager (DBM) API v1.1. This version will be fully sunset on February 28, 2023.

Please migrate to Bid Manager API v2 by the sunset date to avoid an interruption of service. v2 introduced a number of new features and breaking changes, which are listed in our release notes. Here are some of the changes introduced in v2:

Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Merchant IDs as 64-bit in Content API for Shopping

In the Content API for Shopping, Merchant IDs are now 64-bit signed integers. Applications that integrate with the Content API must be able to handle ID values in that range.

Historically, Merchant IDs in the Content API for Shopping were within the maximum value of a 32-bit signed integer, but have recently exceeded this range. In order to avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team