Tag Archives: google_ads_api

Performance Max Campaign in Detail Placement View

The detail_placement_view can be used to query metrics aggregated by ad group and URL or YouTube video in the Google Ads API. The detail_placement_view is not intended to be used for campaigns with an advertising_channel_type of PERFORMANCE_MAX, as this view is only intended to be used with campaigns containing ad groups, and Performance Max campaigns are constructed with asset groups rather than ad groups. However, this view is currently returning impression data for Performance Max campaigns. The impression metrics returned from the ​​detail_placement_view may not be accurate and should not be relied upon for campaigns with advertising_channel_type of PERFORMANCE_MAX.

In the next release of the Google Ads API, v18, we will be adding a new resource called performance_max_placement_view, which can be used to query placement impression data for Performance Max campaigns, and in a subsequent release, we will stop returning impression data from the ​​detail_placement_view for campaigns with advertising_channel_type of PERFORMANCE_MAX. Once performance_max_placement_view is released, use the data returned from that view for Performance Max campaigns rather than the data returned from the detail_placement_view.

If you have any questions or need help, check out the Google Ads API support page for options.

- Devin Chasanoff, on behalf of the Google Ads API Team

Upcoming changes to search and display campaign reporting in the Google Ads API

Starting on October 16, 2024, we will start rolling out changes to search and display reporting. As a result of this change, Google Ads Query Language (GAQL) queries for campaigns with an advertising_channel_type of SEARCH or DISPLAY will return a value of 0 for any metrics in that GAQL query when you include the fields segments.asset_interaction_target.asset or segments.asset_interaction_target.interaction_on_this_asset in the query.

We are making this change now to ensure the accuracy of reporting data in preparation for future launches. If you have any questions or need help, check out the Google Ads API support page for options.

- Devin Chasanoff, on behalf of the Google Ads API Team

Subscribe to the blog

If you want all new blog posts sent directly to your inbox, we have good news. The blog includes a customizable RSS feed that you can subscribe to with your favorite RSS service. Just paste the URL above into your RSS service and get the blog contents delivered in whatever way you prefer. If you're new to RSS, check out this community resource on GitHub describing how it works and providing a list of well-supported services.

If you want to filter to specific products that interest you, that's possible too. Here are some quick links to the RSS feeds for the products supported by this blog: - Mike Cloonan, Ads DevRel Team

Google Ads API v15 sunset reminder

Google Ads API v15 will sunset on September 25, 2024. After this date, all v15 API requests will begin to fail. Migrate to a newer version prior to September 25, 2024 to ensure your API access is unaffected.

Here are some resources to help you with the migration: You can view a list of methods and services your project has recently called using the Google Cloud Console:
  1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
  2. Click Google Ads API in the table.
  3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, the Methods table shows which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v15.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
  4. (Optional) Click the time frame at the top right of the page if you need to change it.
If you have questions while you’re upgrading, reach out to us on the forum or at [email protected].
 - Thanet Knack Praneenararat, Google Ads API Team

Improvements to conversion adjustment uploads

Starting on September 9, 2024, Google Ads API users will no longer need to wait 24 hours before uploading conversion adjustments - they can be uploaded immediately after the original conversion has been uploaded or recorded by Google tags.

This means that you will no longer need to keep track of the 24-hour window before uploading conversion adjustments, and can stop checking for certain error codes and retrying those upload requests.

Specifically, the following changes will take effect:

  1. The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
  2. Conversion adjustments that would previously be rejected with these error codes will count towards the pending_count in diagnostics until they’re processed, at which point they’ll be counted towards either the successful_count or failed_count fields. This might take up to 24 hours.

Here is how these changes will affect older Google Ads API versions v15 and v16:

  1. The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
  2. Any conversion that would have triggered these codes will, in diagnostic reports, count towards the total_event_count metric while being processed. Once processing is completed they will be counted towards either the successful_count or failed_count. This might take up to 24 hours.

What do I need to do?

  1. Remove any logic from your application that waits before uploading adjustments, and begin uploading conversion adjustments at any time after the original conversion has been uploaded.
  2. Modify your application logic and business processes so that you are not tracking the two conversion adjustment errors that are being removed.
  3. If you rely on the successful or failed event count metrics, revisit your application logic with the understanding that some uploaded events may, at times, when using v17, be represented as pending.

If you have any questions or need help, see the Google Ads API support page for options.

- Ben Karl, on behalf of the Google Ads API Team

Announcing v17_1 of the Google Ads API

Today, we’re announcing the v17_1 release of the Google Ads API. To use some of the v17_1 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This version has no breaking changes.

Here are the highlights: Where can I learn more?
The following resources can help you get started: If you have any questions or need additional help, contact us via the forum.
 - Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Upcoming Changes in Python Version Support for the Google Ads API Client Library for Python

In October, 2024, Python 3.8 will reach end-of-life and will no longer be supported by the Python Software Foundation. Once Python 3.8 officially reaches end-of-life status, it will also no longer be supported by the Google Ads client library for Python. That means we will not make updates to the library, or address any issues related to compatibility with Python 3.8, outside of critical security updates.

In Q1 2025 we will release a new major version of the library that is incompatible with Python 3.8. This new version will include support for Python 3.13. Users of deprecated, or soon-to-be deprecated versions of Python, are at risk of losing access to the Google Ads API. Please note the below timelines:

  • Python 3.7 users will lose access to the API when v15 is sunset on September 25, 2024
  • Python 3.8 users will lose access to the API when v18 is sunset in Q3 or Q4 2025.

Any library users currently relying on Python 3.7 or 3.8 should upgrade their systems to Python 3.9 or higher as soon as possible.

If you have any questions about this change, please file an issue on the client library repository.

- Ben Karl, on behalf of the Google Ads API Team

Google Ads shopping report outage starting August 1, 2024

Update (August 2, 2024 13:30 PST): Follow our Google Ads dashboard at ads.google.com/status for updates. See this Google Ads entry for details on this outage.

We are actively looking into an issue with Google Ads. As of August 1 at about 2 PM EDT, the following reports are down and are returning internal API errors:

Thank you for your patience as we resolve this issue.

Nadine Wang, Google Ads API Team

Watch Performance Max and the Google Ads API On Demand

As previously announced, Ads Developer Relations hosted a workshop on July 17: Performance Max and the Google Ads API. We are grateful to all the Google Ads API and Performance Max enthusiasts who tuned in for the live workshop.

If you didn't get a chance to watch the workshop live, or you want to review content you previously watched, you can still view sessions on demand at the event site.

We hope you will take advantage of this awesome resource to learn more about the power of Performance Max campaigns, and hear from Google Ads API experts on how to build, manage, and report on Performance Max campaigns using the API.

 - Laura Chevalier, Google Ads API Team

Upcoming changes to page size in the Google Ads API

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:

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 consistent across all API versions.

What do I need to change?

If you use version v17 of the API, no changes are required. If you use an older version of the API and set the page_size field in your GoogleAdsService.Search requests, then you should update your application code to stop setting this field.

How to get help

If you have any questions or need help, check out the Google Ads API support page for options.

 - , Google Ads API Team