AdGroupBidModifier with its preferred_content field set will fail with an ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error.AdGroupBidModifier with its preferred_content field set will return a zero value for the bid_modifier field.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.
Introducing a predictable deprecation schedule offers the following benefits for app developers and publishers:
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 |
|
| Sunset |
|
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:
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:
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.
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.
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
feedLabel field. We’d like to update you on the progress of this change. Here are our previous announcements: feed_label field in ShoppingSetting for Shopping and Performance Max campaigns. You can set feed_label in the Google Ads UI and the Google Ads API.feedLabel, and not targetCountry, if they were added in the Merchant Center UI.Products.update to update products by feedLabel. For example, if you had a product with offerId of “111111111” and a feedLabel set to “WINTERPRODUCTS”, you can now update attributes such as salePrice for that product by making the following call:Example request body:
PATCH https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/products/online:en:WINTERPRODUCTS:1111111111
Behavior summary:
{
"salePrice": {
"value": "17.99",
"currency": "USD"
}
}
feedLabel: Products.insert on products with a matching feedLabel and targetCountry. Currently, Products.insert might return an error if you don’t provide a matching targetCountry. This behavior hasn’t changed if you continue to use only targetCountry.feedLabel to a valid 2-letter CLDR territory code, you must still set the shipping attribute of the products resource to the same country in order to target that country. For example, if you set a new feedLabel to “US”, you must also set the country field in the shipping attribute to “US”. If you don’t set both fields, the product might not be eligible to serve in that country. You can configure targeting for an entire feed in the Merchant Center UI.Products.list or Products.get, you might see products that only have feedLabel (and not targetCountry) set if they were added in the Merchant Center UI.feedLabel is set for a product it becomes part of the product Id. This means you can’t modify the feedLabel for that product (this is similar to how language works). If you wish to change the feedLabel you will need to create a new product with a different product Id.Products.insert calls with feedLabel set to any string. At this point, including targetCountry will become optional.datafeeds resource to include feedLabel in the Content API for Shopping.feedLabel, you can opt back in to receiving these offers.
Ian Ballantyne, Content API for Shopping Team
We’re pleased to announce that Display & Video 360 API v2 is available in public beta starting today. We're also extending our DV360 API Developer Survey through the end of September so that we can gather more customer feedback on v2 and the API in general.
v2 includes a number of new features and breaking changes. Here are some of the changes introduced in v2:
get and list methods in the advertisers.lineItems and advertisers.lineItems.targetingTypes.assignedTargetingOptions services. advertisers.lineItems.bulkListAssignedTargetingOptions and advertisers.lineItems.bulkEditAssignedTargetingOptions methods. lineItem.entityStatus field across multiple line items in a single request using the new advertisers.lineItems.bulkUpdate method. assignedTargetingOptionId values, enabling the retrieval, creation, and deletion of targeting settings with enums.More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v1 to v2. As it is in beta, be aware that we might make unversioned breaking changes to DV360 API v2 before it exits the beta phase.
If you want to provide feedback and recommend features that should be included in future versions of the API, please fill out our DV360 API Developer Survey. The survey has been extended through the end of September and will help shape the product roadmap for v2 and beyond.
If you run into issues or need help with these new features or samples, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team
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:
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
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:
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
Since 2020, we've asked the Google Publisher Tag (GPT) developer community to provide their valuable feedback through an annual survey. This feedback influences what we work on each year, and has directly inspired improvements to our sample offerings, release notes, and much more.
As we look forward to next year, it's time once again to check in with our developer community to see what's working well and what can be improved. Starting today, we're kicking off the 2022 GPT developer survey.
The survey should take no more than 10 minutes to complete, and it will be open through the end of October 2022. Most questions are optional and your answers are completely anonymous.
Remember that the feedback you provide influences what we work on over the course of the next year, so please let us know what matters most to you. Thanks in advance for taking the time to help improve the GPT developer experience!
- Jonathon Imperiosi, Google Publisher Tags Team
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:
Query and Report resources that use named object types and enums. Report objects via queries.reports.get. queries.list and queries.reports.list requests. queries.run behavior to return a Report object instead of an empty responseFollow 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
UpgradeLocalCampaignToPerformanceMaxRecommendation to help you migrate from Local campaigns to Performance Max campaigns (more details).Campaign.bidding_strategy_system_status to show the system status of the bidding strategy. It’ll help you understand if the bidding strategy is learning, limited, or misconfigured, etc. This addresses a long standing feature request to surface learning status in the API.FlexibleRuleUserListInfo for creating user lists in a more flexible way. This is also a replacement for DateSpecificRuleUserListInfo that was removed in the previous release.GoogleAdsService.Mutate(). Previously, it was possible only when using ExperimentService.ReachPlanService.GenerateReachForecast.YouTubeSelectSettings when calling ReachPlanService.GenerateReachForecast.YouTubeSelectLineUp when calling ReachPlanService.ListPlannableProducts.
Thanet Knack Praneenararat, on behalf of the Google Ads API Team