[go: nahoru, domu]

Today, we are releasing a first-of-its-kind interactive guide to help you get started with standard Performance Max (PMax) campaigns and Performance Max for online sales with a product feed. This new guide walks through the end-to-end process of creating Performance Max campaigns to provide you with a better understanding of the various steps involved. You can build your own custom code dynamically with customization and configuration options.

The Performance Max interactive guide was designed to provide you with a single place to access the entire developer journey. As you step through the guide, you will have the option to enter custom values using form fields in the left-hand navigation panel. As you do, the sample code will automatically update to reflect your inputs.


In addition to variable substitution, the interactive guide offers a number of configuration options, including the ability to interactively create:
  • Standard Performance Max campaigns
  • Performance Max for online sales with a product feed
  • Production partition trees of listing group filters
  • Multiple asset groups
  • Any number of assets supported by Performance Max
  • Any number of campaign criteria support by Performance Max
  • Multiple campaign conversion goals

The Performance Max interactive guide currently supports Java, with additional languages to be added in the future. You can now build your own Google API integrations with this resource. Feel free to provide feedback on this tool by clicking the Feedback button in the top right corner of the guide.

As always, feel free to reach out to us with any questions via the Google Ads API forum or at googleadsapi-support@google.com.

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.

In the Content API for Shopping, your Merchant Center account and the products in it might be disapproved for various reasons. Historically, you have been able to see the status of your merchant center account for free listings and Shopping ads with the accountstatuses service. In Q1 2022 we introduced the freelistingsprogram and shoppingadsprogram services to provide more granular detail. You can now use the requestreview method on the freelistingsprogram and shoppingadsprogram services to request your account to be re-reviewed after making changes to fix your product and account data.

For an in-depth explanation of how to use the freelistingsprogram and shoppingadsprogram services, please refer to the Free listings and Shopping ads guides.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

Today we’re announcing the launch of Display & Video 360 API v2 out of public beta, and into general availability, and updates to both v1 and v2. As Display & Video 360 API v2 enters general availability, it becomes our recommended version. Our existing guides have been updated to reflect v2 features and conventions.

The following features have been added to v2:

The following updates have been made to both v1 and v2:

  • Removed the character limit for the description field in InsertionOrderBudgetSegment objects.
  • Increased the max page size of a subset of list requests from 100 to 200. The default page size for these methods is still 100.

In addition to these updates, we’ve also fixed two known issues in v2 regarding enum targeting and the line item bulkUpdate method. More detailed information about this update can be found in the Display & Video 360 API release notes, and updated instructions on migrating from v1 to v2 can be found in our migration guide. Before using these new features, make sure to update your client library to the latest version.

If you have questions regarding the breaking changes or run into issues or need help with these new features, please contact us using our support contact form.