On August 10, 2022, we announced a change to country targeting for shopping products with the introduction of the feedLabel field. We’d like to update you on the progress of this change. Here are our previous announcements:

• See Feed label replaces target country in Content API for Shopping for the original announcement for the Content API for Shopping.
• See Country targeting in Shopping Ads campaigns is changing in August 2022 for the original announcement for the Google Ads API.

What’s already changed

Google Ads:
Any Google Ads account can set the 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.

Merchant Center & Content API:
As of September 14th, 2022 we‘ve started the gradual rollout of feed labels in the Merchant Center UI. When this feature is enabled in the UI, merchants will be able to create a new feed with feed label set to any valid string. See Use feed labels to advertise products from specific feeds for more information.

In the Content API, you might see the following:

• Products that have only feedLabel, and not targetCountry, if they were added in the Merchant Center UI.
• Products with feed labels that aren’t two-letter country codes.

You can now use 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:
HTTP request:

PATCH https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/products/online:en:WINTERPRODUCTS:1111111111

Example request body:

{
  "salePrice": {
    "value": "17.99",
    "currency": "USD"
  }
}

Behavior summary:
Here’s a clarification of the current API behavior for feedLabel:

• Insertion: You can only call 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.
• Targeting: If you set 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.
• Get/List: When you use 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.
• Product IDs: Once a 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.

What’s coming next

Products:
Once the gradual rollout of feed labels in the Merchant Center UI is complete, we will accept Products.insert calls with feedLabel set to any string. At this point, including targetCountry will become optional.

Datafeeds:
In late September, we will also update the datafeeds resource to include feedLabel in the Content API for Shopping.

Opt out of receiving products and datafeeds without a country
If you’re concerned your codebase cannot handle products and datafeeds without a country, and you want to opt out of receiving them via the Content API for Shopping, fill out the following form: Feed label replaces target country in the Content API for Shopping - temporary exemption. When you’re ready to support feedLabel, you can opt back in to receiving these offers.
If you have any questions about this change, please visit the Content API for Shopping forum.
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:

• You can now retrieve YouTube & Partners line items and their targeting settings using get and list methods in the advertisers.lineItems and advertisers.lineItems.targetingTypes.assignedTargetingOptions services.
• You can now retrieve and update assigned targeting options for multiple line items in a single request using the new advertisers.lineItems.bulkListAssignedTargetingOptions and advertisers.lineItems.bulkEditAssignedTargetingOptions methods.
• You can now update the lineItem.entityStatus field across multiple line items in a single request using the new advertisers.lineItems.bulkUpdate method.
• Some targeting types now use enum values as 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 launching support for Performance Max campaigns in Google Ads scripts. This is treated as a brand new campaign type in scripts, similar to how video or shopping campaigns already work.

To get started, check out the performance max campaigns selector on the AdsApp. Once you've selected a PerformanceMaxCampaign, you can perform common operations like pausing or enabling the campaign, as well as selecting and modifying most asset types in asset groups. You cannot modify text assets this way, and you cannot create new campaigns or asset groups through scripts.

Performance Max retail campaigns are supported in only a limited fashion as listing groups cannot be managed via Scripts.

For more information about Performance Max campaigns in general, check out the complete help center article.

If you have any questions or feedback, please leave a post on our forum or send a message to our support alias googleadsscripts-support@google.com so that we can help.
- Mike Cloonan, Google Ads Scripts 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:

• 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

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.

Take the 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