As announced in February 2024, Display & Video 360 API v2 will sunset on September 3, 2024. Please migrate to Display & Video 360 API v3 before the sunset date to avoid an interruption of service. You can read our release notes for more information about v3. Follow the steps in our v3 migration guide to help you migrate from v2 to v3. If you run into issues or need help with your migration, please contact us using our new Display & Video 360 API Technical support contact form. - Trevor Mulchay, Display & Video 360 API Team ..read more

Starting the week of August 19, 2024, we will roll out a change that removes the ability to set the page_size field when making GoogleAdsService.Search requests. All requests will assume a fixed page size of 10,000 rows instead. Developers will receive the following errors if the page_size field is set: Version v16 will throw a PAGE_SIZE_NOT_SUPPORTED error. Versions v15 and older will throw an INVALID_PAGE_SIZE error. This change was previously introduced as a versioned change in version v17 of the API. The current change introduces the change to the older API versions, making the API consi ..read more

On October 31, 2024, Display & Video 360 Entity Read Files (ERFs) will sunset. After this date, new private and public ERFs will not be generated. ERFs were deprecated in June 2021 and the October sunset date was first announced in January 2024. If you are currently using ERFs to programmatically retrieve Display & Video 360 resource configurations, migrate to the Display & Video 360 API. You can either integrate directly with the Display & Video 360 API using REST requests or automatically import Display & Video 360 resource configurations into BigQuery using the Display ..read more

We heard your feedback via Play Console crash reports regarding Application Not Responding (ANRs) errors related to the Google Mobile Ads SDK. After analyzing these reports, we updated our SDK implementation best practices to reduce ANR rates. The recommended best practices are as follows: Initialize the Mobile Ads SDK on a background thread Enable optimization flag for ad loading 1. Initialize the Mobile Ads SDK on a background thread Our previous best practice was to specify the OPTIMIZE_INITIALIZATION manifest flag. However, some work on the calling thread is still required to prepare Mob ..read more

As previously announced, the Performance Max and the Google Ads API workshop is only one week away, on July 17, 2024. Register today to reserve your spot. As a reminder, this developer-focused, virtual workshop will provide you with knowledge, resources, and support to build, manage, and report on Performance Max campaigns in the Google Ads API. We’re offering this live workshop in three regions. Follow the links below to view the full agenda in your region. Regional Workshop Times & Agendas Americas EMEA APAC We look forward to seeing you!  - Laura Chevalier, Google Ads API Te ..read more

What changed? On 24 July 2023, we announced the auto-migration of location extensions to assets. For the majority of accounts, location extensions were automatically migrated to assets. This change was made to expand the variety of ways in which your location extensions can serve. Accounts with no activity (no impressions, no clicks, and no spend) from July 1, 2023 to January 1, 2024 were not migrated. How do I know if an account was migrated? To find the status of an account, use the following fields of the customer resource: bool location_asset_auto_migration_done string location_asset_aut ..read more

Today we're announcing the release of the Merchant API Beta. This is the newest version of the Content API for Shopping which comes with exciting new features. The Merchant API is a redesign of the Content API for Shopping which can help you showcase your products with new features, modular design with isolated sub-API updates, and improved alignment with Google's API improvement proposals. We invite you to try out the Merchant API Beta to provide early feedback so we can improve the Merchant API for you. For more information, we highly recommend reviewing the launch status for Merchant API B ..read more

In the upcoming months, Display & Video 360 instant reports will be made available using the Bid Manager API. We previously announced the migration of certain report types from Offline Reporting to Instant Reporting. Once a partner is migrated, they will see the following changes: Instant reports will be included in queries.list responses. Existing Standard, Reach, YouTube, and URA reports will only be available under the Instant Reporting tab in the Display & Video 360 interface under the same query and report IDs. If you use the Display & Video 360 interface to build new reports ..read more

Today, we’re announcing the June 2024 update to the Display & Video 360 API. This update adds the following: The ability to retrieve and manage keyword targeting assigned at the advertiser level. The optimizationObjective field in the InsertionOrder resource. This field is only writable for allowlisted customers, and will otherwise be set as null. More details about this update can be found in the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version. If you need help with these new features, please conta ..read more

What’s New Starting with Google Ads API v17, BatchJobService supports AssetGroupOperation. With this change you can use batch processing to create and manage entire Performance Max campaigns. Batch processing is a powerful feature in the Google Ads API that lets you dispatch a set of operations, which might be interdependent, to multiple services without waiting for each operation to complete. Batch processing also provides automatic retries for transient errors, and automatic grouping of operations We have made batch processing available for AssetGroupOperation in response to your feedback to ..read more