Tag Archives: sunset

Announcing v2 of the AdSense Management API

We're happy to announce that v2 of the AdSense Management API is available starting today. This version adds the ability to fetch the status of sites on your account and aligns the AdSense Management API with current Google API standards.

At this time, v1.4 of the AdSense Management API is now deprecated, and it will sunset on October 12, 2021.

Notable changes from v1.4 to v2 include the following:
  • All deprecated methods in v1.4 have been removed in v2. This includes resource methods that did not specify an AdSense account.
  • Resources are now identified by a name field. For example, an AdClient’s name would be “accounts/{accountId}/adclients/{adClientId}”.
  • With v2, AdSense Management API reporting data now aligns with the AdSense UI. This means that AdMob and YouTube properties are no longer supported. If you need to continue to fetch AdMob data programmatically, please migrate to the AdMob API. Additionally, the AdSense Management API will only support report data going back 3 years.

For a full list of changes, see the release notes. As always, feel free to reach out to us on the AdSense API forum with any API-related questions.

Sunset grace period for existing v2 users of the Content API for Shopping

As we’ve previously announced, we will stop supporting legacy v2.0 of the Content API for Shopping in favor of v2.1, which has been available since March 2019.

As this has been a difficult year for all of us, in order to provide you ample time to migrate to v2.1 we will be extending the sunset date for existing merchant accounts actively using v2.0 to September 30, 2021. However, we will not allow new merchant accounts onto v2.0 after April 30, 2021. The account restrictions will not impact users accessing new sub-accounts via an existing multi-client account (MCA), provided that MCA has been actively making v2.0 requests.

We will publish another blog post in the coming weeks with a process for requesting an exemption to add new accounts to your v2.0 integration after April 30, 2021.

Throughout this grace period, we will continue to provide support for your efforts to migrate to v2.1. We strongly encourage you to migrate to v2.1 as soon as possible.

What do I need to know?
In March 2019, we released version 2.1 of the Content API for Shopping with major improvements to the API management experience for Merchant Center programs, including: See the complete list of changes in the release notes and the migration guide to help with the transition.

If you have any questions or issues during migration, contact your Google representative for Merchant Center programs, or ask questions in the Content API for Shopping forum.

What do I need to do?
Migrate to v2.1 of the Content API as soon as possible.

Sunset date for deprecated DBM API services postponed to April 15, 2021

The sunset of deprecated services in the DoubleClick Bid Manager (DBM) API, originally scheduled for February 26, 2021, has been postponed to April 15, 2021. The deprecated services scheduled for sunset include the entirety of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service.

Prior blog posts regarding this sunset give instructions on how to migrate from these deprecated services to either the DBM API v1.1 Reporting service or the Display & Video 360 (DV360) API. Consult these previous announcements for more information.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.


Combining Similar Bid Strategies

The v6 release of the Google Ads API added support for Maximize conversions and Maximize conversion value bid strategies in Search campaigns. This includes a new read-only MaximizeConversions.target_cpa field. Bid strategies having either this new target_cpa field or the read-only MaximizeConversionValue.target_roas field act identically to TargetCpa and TargetRoas bid strategies, respectively. In the future, bid strategies for Search campaigns will be reorganized for simplification.

What’s Changing

For Search campaigns, TargetCpa and TargetRoas will no longer be separate from the MaximizeConversions and MaximizeConversionValue bid strategies. Instead, they will be represented as MaximizeConversions and MaximizeConversionValue bid strategies with their respective target_cpa and target_roas fields set. Use of TargetCpa and TargetRoas as separate strategies will be deprecated.

There will be no impact to bidding behavior due to these changes. The MaximizeConversions bid strategy using the new optional target_cpa setting will still behave like the TargetCpa strategy does today, and likewise, MaximizeConversionValue using the new optional target_roas setting will behave like TargetRoas.

Before After
TargetRoas MaximizeConversionValue.target_roas
TargetCpa MaximizeConversions.target_cpa


Starting in April 2021, the Google Ads UI will start allowing some users to create MaximizeConversions and MaximizeConversionValue bid strategies with their target_cpa and target_roas fields set, in lieu of the old-style TargetCpa and TargetRoas bid strategies. This change will gradually ramp-up to more accounts over time.

The target_roas and target_cpa will remain read-only to API users until a future version of the API enables mutate functionality.

What to Do
Developers should ensure their code treats Search campaigns that have MaximizeConversions with a set target_cpa field and MaximizeConversionValue with a set target_cpa field the same way it treats TargetCpa and TargetRoas bid strategies, respectively.

We will publish an update on the blog when the above fields are mutable, along with several months' notice before TargetCpa and TargetRoas strategies are deprecated in Search campaigns.

If you have any questions or need additional help, contact us via the forum or at [email protected].

Combining Similar Bid Strategies

The v6 release of the Google Ads API added support for Maximize conversions and Maximize conversion value bid strategies in Search campaigns. This includes a new read-only MaximizeConversions.target_cpa field. Bid strategies having either this new target_cpa field or the read-only MaximizeConversionValue.target_roas field act identically to TargetCpa and TargetRoas bid strategies, respectively. In the future, bid strategies for Search campaigns will be reorganized for simplification.

What’s Changing

For Search campaigns, TargetCpa and TargetRoas will no longer be separate from the MaximizeConversions and MaximizeConversionValue bid strategies. Instead, they will be represented as MaximizeConversions and MaximizeConversionValue bid strategies with their respective target_cpa and target_roas fields set. Use of TargetCpa and TargetRoas as separate strategies will be deprecated.

There will be no impact to bidding behavior due to these changes. The MaximizeConversions bid strategy using the new optional target_cpa setting will still behave like the TargetCpa strategy does today, and likewise, MaximizeConversionValue using the new optional target_roas setting will behave like TargetRoas.

Before After
TargetRoas MaximizeConversionValue.target_roas
TargetCpa MaximizeConversions.target_cpa


Starting in April 2021, the Google Ads UI will start allowing some users to create MaximizeConversions and MaximizeConversionValue bid strategies with their target_cpa and target_roas fields set, in lieu of the old-style TargetCpa and TargetRoas bid strategies. This change will gradually ramp-up to more accounts over time.

The target_roas and target_cpa will remain read-only to API users until a future version of the API enables mutate functionality.

What to Do
Developers should ensure their code treats Search campaigns that have MaximizeConversions with a set target_cpa field and MaximizeConversionValue with a set target_cpa field the same way it treats TargetCpa and TargetRoas bid strategies, respectively.

We will publish an update on the blog when the above fields are mutable, along with several months' notice before TargetCpa and TargetRoas strategies are deprecated in Search campaigns.

If you have any questions or need additional help, contact us via the forum or at [email protected].

Changes to Showcase Shopping ads

On April 5, 2021, support for Showcase Shopping ads will be removed from the AdWords API. Users will no longer be able to create or update the following Showcase Shopping objects, and attempts to do so will result in the following errors.

Object Error
AdGroups

with adGroupType SHOPPING_SHOWCASE_ADS
OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE
AdGroupAds containing ShowcaseAds OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE


Any remaining Showcase ad groups will be set to REMOVED status, and remaining AdGroupAds containing ShowcaseAds will be set to DISABLED status and stop serving. Developers can still retrieve historical metrics for these ads and ad groups by fetching reports that explicitly filter to include REMOVED or DISABLED objects.

This change only affects AdWords API users. Management of Showcase Shopping ads is not supported by Google Ads API or Google Ads scripts.

If you have any questions or need additional help, contact us via the forum or at [email protected].

Sunsetting Portofolio Enhanced CPC Bid Strategies

On March 22, 2021 we will begin to sunset portfolio (shared) Enhanced cost-per-click (ECPC) bid strategies. The following behaviors will be blocked in all versions of both the AdWords API and the Google Ads API:
  • Creating new portfolio ECPC strategies.
  • Attaching portfolio ECPC strategies to campaigns.
Note that standard (non-portfolio) ECPC strategies will not be affected.

Affected Portfolio Enhanced CPC Strategies
Google Ads API Bidding_strategy.type = BiddingStrategyType.ENHANCED_CPC
AdWords API SharedBiddingStrategy.type = MANUAL_CPC,

SharedBiddingStrategy.biddingScheme.enhancedCpcEnabled = TRUE


Change Description
Any operation creating new portfolio ECPC strategies, or attaching a portfolio ECPC strategy to a campaign, will generate one of the following errors:

Error Upon Creation Error Upon Attaching
Google Ads API BIDDING_STRATEGY_NOT_SUPPORTED CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN
AdWords API BIDDING_STRATEGY_NOT_SUPPORTED CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN


Migration Description
In the future, we will remove the portfolio ECPC strategy entirely, in favor of standard ECPC. In order to prepare for this change, you can proactively migrate all your portfolio ECPC strategies to standard ECPC strategies using the instructions below.

All remaining portfolio ECPC campaigns and strategies will be automatically migrated at a later date. We will post an update on this blog ahead of that migration.

Self-migration using Google Ads API
Update a campaign by using CampaignService.MutateCampaigns() to set its manual_cpc.enhanced_cpc_enabled field to true. Be sure to set the update_mask on your request to match:

operations: [
{
update: {
resource_mame: customers/CUSTOMER_ID/campaigns/CAMPAIGN_ID,
manual_cpc: {
enhanced_cpc_enabled: true
}
},
update_mask: manual_cpc.enhanced_cpc_enabled
}
]
Self-migration using AdWords API
Update a campaign by using CampaignService.mutate() to set its biddingStrategyType to MANUAL_CPC, and its biddingScheme.enhancedCpc field to true:

<operations>
<operator>SET</operator>
<operand>
<id>CAMPAIGN_ID</id>
<biddingStrategyConfiguration>
<biddingStrategyType>MANUAL_CPC</biddingStrategyType>
<biddingScheme>
<enhancedCpcEnabled>true</enhancedCpcEnabled>
</biddingScheme>
</biddingStrategyConfiguration>
</operand>
</operations>
If you have any questions or need additional help, contact us via the forum or at [email protected].

Sunset of the Ad Manager API v202002

On Monday, March 1, 2021, in accordance with the deprecation schedule, v202002 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v202002, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202011 we added the getTrafficData method to the ForecastService, which is capable of exploring historical and forecasted network-level data for a particular date range and targeting configuration.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. Keep in mind that v202002 is the final version to use int types for Activity and ActivityGroup, and all later versions use type long. After you’ve considered all of the changes, grab the latest version of your client library and update your code.

As always, don't hesitate to reach out to us on the developer forum with any questions.

Google Ads API v3 sunset reminder

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

We've prepared various resources to help you with the migration:

If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].

Upcoming sunset for DBM API v1, SDF Download and Line Item services

As announced in August, deprecated services in the DoubleClick Bid Manager (DBM) API, comprised of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service, will be sunset on February 26, 2021.

If you are still using the DBM API v1 Reporting service, you must migrate to the DBM API v1.1 Reporting service before the sunset date to avoid an interruption of service. Consult the API release notes for details of the changes between v1 and v1.1. Differences to note during this migration include:
  • Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure generated in v1.
  • Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. You have to update your implementation to traverse multiple pages if you want to consume more than the first 100 items returned.

If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.
Guides are available to help you set up and start using the Display & Video 360 API to download SDFs and manage your line items.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.