Google Ads Developer Blog

Announcing v202411 of the Google Ad Manager API

2024-11-21T11:40:00.000-08:00

We're pleased to announce that v202411 of the Google Ad Manager API is available starting today, November 21, 2024. This release brings support for INVENTORY_FORMAT reporting dimensions and removes GOOGLE as a GrpProvider.

In the PublisherQueryLanguageService Line_Item table, the field EndDateTime has been renamed to ServingEndTime. In both v202411 and earlier versions, the value is inclusive of any grace period. The new name differentiates the PQL field from the LineItem.endDateTime field which is exclusive of any grace period.

Version	Service	End time including grace period	End time excluding grace period
v202411	PublisherQueryLanguageService	`ServingEndTime`	Not available
v202411	LineItemService	`endDateTime` + `autoExtensionDays`	`endDateTime`
v202408	PublisherQueryLanguageService	`EndDateTime`	Not available
v202408	LineItemService	`endDateTime` + `autoExtensionDays`	`endDateTime`

For the full list of changes, check the release notes. Contact us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

Introducing lower confidence reach data in the Bid Manager API

2024-11-20T12:22:00.000-08:00

Starting today, you can populate reports in the Bid Manager API with data that had been previously omitted due to lower statistical significance by using a new filter, FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID, and setting the value to “0”.

This filter setting only impacts reach metrics with the following Metric prefixes as defined in the Bid Manager API:

METRIC_UNIQUE_REACH_
METRIC_VIRTUAL_PEOPLE_DUPLICATE_
METRIC_VIRTUAL_PEOPLE_EXCLUSIVE_
METRIC_VIRTUAL_PEOPLE_OVERLAP_

queries.create requests with queries that filter by FILTER_UNIQUE_REACH_SAMPLE_SIZE_ID but don’t include impacted metrics will return a 400 error.

On February 4, 2025, Display & Video 360 will include unique reach data with lower statistical confidence by default. If you want to ensure that your reports continue to only return high-confidence data, we recommend that you update your integration to use the new filter value to filter to "1" when creating reports with any of the impacted metrics.

Read more about these changes in our release notes.

If you run into issues or have questions about these changes, please contact us using our new Bid Manager API Technical support contact form.

- Trevor Mulchay, Bid Manager API Team

Google Ads API 2025 release and sunset schedule

2024-11-20T11:16:00.000-08:00

We’re announcing our tentative 2025 release and sunset schedule for upcoming versions of the Google Ads API to bring greater clarity to your planning cycle. Please keep in mind that these dates are only estimates and may be adjusted going forward. Additionally, releases may be added, removed, or switched between major and minor versions.

Version	Planned Release Type*	Projected launch*	Projected sunset*
V19	Major	February/March 2025	February 2026
V19_1	Minor	April/May 2025	February 2026
V20	Major	June/July 2025	June 2026
V20_1	Minor	August/September 2025	June 2026
V21	Major	October/November 2025	October 2026

*Estimated and subject to change

Where can I learn more?

Check back for any updates as the blog is the best place to stay informed about developments in this space.

If you have any questions or need additional help, contact us via the forum.
- David Stevens, Google Ads API Product Manager

Launching Structured Data Files v8

2024-11-13T10:10:00.000-08:00

Today we’re announcing the general availability of Structured Data Files (SDF) v8. All users can now use SDF v8 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

SDF v8 adds support for Demand Gen Line Item, Ad Group, and Ad resources, as well as the companion banner field for YouTube and Demand Gen Ads.

Full details on the changes made in v8 can be found in our Structured Data Files release notes and instructions for migrating from v7.1 to v8 can be found in our migration guide. If you are currently using SDF v6, follow the instructions in our v7 migration guide first before migrating to v8.

If you run into issues or need help with this new version, please follow the instructions on our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

Consent unbundling in Google Ads scripts

2024-11-12T06:25:00.000-08:00

Starting in January 2025, we will enable consent unbundling in Google Ads scripts. This is a new feature of OAuth that allows you to customize which specific scopes you want to authorize, rather than the current all-or-nothing approach. Consent unbundling is being rolled out in all Google OAuth applications.

Google Ads scripts already runs a static analysis on your code before presenting the OAuth consent screen, and only requests the specific features that are required to run the script. Therefore, when you authorize Google Ads scripts, ensure that you select all the boxes on that screen, or else you will experience execution errors.

Any existing scripts you already have will continue to work without any user action needed when this feature rolls out, unless you make changes that require reauthorization. Existing unmodified scripts will continue to run as usual.

If you have any questions about consent unbundling or other Google Ads scripts features, please post them in the Google Ads scripts forum.
- Mike Cloonan, Google Ads Scripts Team

Announcing Budget Prefills with the Google Ads API

2024-10-23T07:49:00.000-07:00

With v18 of the Google Ads API, you can now use the Recommendations.GenerateRecommendations method during campaign construction to retrieve optimized budget suggestions for Performance Max and Search campaigns.

When using the GenerateRecommendations method with a recommendation type of CAMPAIGN_BUDGET, you can supply inputs, such as final URL and bidding strategy, which Google machine learning models will use to generate budget recommendations. Google Ads API users that provide a campaign creation interface can provide budget prefills that fit into the campaign creation workflow. As with many recommendation types, campaign budget recommendations provide projected impact metrics to help understand the effect that implementing the recommendation will have on account performance.

Explore additional Recommendations API features

Recommendations in the Google Ads API offer several ways to increase your campaigns' performance through customized suggestions like adding new keywords or updating your bidding strategy. With RecommendationSubscriptionService, you can subscribe to automatically apply specific recommendation types of your choosing for your account. To retrieve and process recommendations directly, you can leverage the recommendation reporting resource.

To explore the full recommendations offering, check out our implementation guide.

- Laura Chevalier, Google Ads API Team

October 2024 update to Display & Video 360 API

2024-10-22T11:02:00.000-07:00

Today, we’re announcing the October 2024 update to the Display & Video 360 API. This update adds the following:

Support for cost-per-view performance goals and the targeting of connected devices.
The ability to generate and download Structured Data Files (SDFs) using SDF v8. This version is currently in beta and only available to limited partners.
Additional Adloox brand safety settings under third-party verifier targeting.

In addition, we’ve also officially deprecated the SDF v5.5 enum value given the sunset of v5.5 earlier this month.

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 contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing v18 of the Google Ads API

2024-10-16T12:07:00.000-07:00

Today, we’re announcing the v18 release of the Google Ads API. To use the v18 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week.

Here are the highlights:

You can now use GenerateRecommendations during campaign construction to retrieve optimized budget suggestions for Performance Max and Search campaigns.
A new performance_max_placement_view report allows developers to query performance data for a given placement where Performance Max ads served.
Replaced the summary_row_setting and return_total_results_count fields of SearchGoogleAdsRequest with the search_settings field, which allow developers to freely specify if summary_row, total_results_count and results will be returned with SearchGoogleAdsResponse.
Added new segments for campaign and ad_group reports to allow for segmenting performance data based on a specific destination, such as a city or a country, for Hotel and Search campaigns.
Added support for Travel Feeds in Search Ads with a new click type (ClickType.TRAVEL_ASSETS) and a new asset type (AssetSetType.TRAVEL_FEED).
Added DataLinkService.CreateDataLink, which allows customers to link their Google Ads account to creator videos and enables running partnership ads.
Added content_criterion_view which returns performance metrics of targeted contents, such as keywords, placements and topics, for Display, Demand Gen and Video campaigns.
Renamed AssetType.DISCOVERY_CAROUSEL_CARD to AssetType.DEMAND_GEN_CAROUSEL_CARD.
Added AdGroup.exclude_demographic_expansion which allows excluding demographics from being expanded when optimized_targeting_enabled is true, a feature that was previously only supported for Demand Gen.
PhoneCallDetails.call_recording_url will be empty instead of providing an invalid URL if the call recording doesn’t exist for the given Local Services lead conversation.
Added new metrics related to invalid clicks which can be queried with the campaign report.

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

New data retention policy for Google Ads

2024-10-10T12:37:00.000-07:00

Starting November 13th, Google Ads will be implementing a new data retention policy. All account data, including performance metrics, billing information, and historical reports, will now be retained for a period of 11 years.

This means that when querying the Google Ads API using either GoogleAds.Search or GoogleAds.SearchStream you will only be able to retrieve data up to 11 years before the date of your API request and data before that will not be returned.

Required actions

If you need historical data for more than 11 years ago, we recommend you retrieve it and store it before November 13th, 2024.

Otherwise, no action is required on your end. This update will be applied automatically to your account and GoogleAds.Search and GoogleAds.SearchStream continue to work as usual.

However, be aware that you may notice differences in your reporting due to different values being returned.

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

- Mattia Tommasone, Google Ads API Team

Performance Max Campaign in Detail Placement View

2024-10-02T12:11:00.000-07:00

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

2024-09-23T10:44:00.000-07:00

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

2024-09-19T07:06:00.000-07:00

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

Targeting and pacing changes in the Display & Video 360 API and Structured Data Files

2024-09-04T10:52:00.000-07:00

Update: Updated section on changes to YouTube & partners line item content targeting to clarify that targeting of this type will not be able to be assigned directly to YouTube & partners line items, but can be inherited from the parent advertiser.

In the coming months, the following updates to the Display & Video 360 product might impact your integration with the Display & Video 360 API and Structured Data Files:

On September 30, 2024, directly assigned content targeting will be deprecated for YouTube & partners line items.
On September 30, 2024, audiences from Oracle will no longer be accessible and removed from existing targeting.
On September 30, 2024, optimized targeting will no longer be available for line items using a subset of bid strategies.
On November 5, 2024, “Flight ASAP” pacing configuration will no longer be accepted for insertion orders, and existing insertion orders with this configuration will automatically be updated.

For details on how to prepare for each of these changes, read the rest of this blog post and check the Display & Video 360 API Announced Deprecations page.

Changes to content targeting for YouTube & partners line items

On September 30, 2024, it won’t be possible to directly assign Digital Content Label and Other Content Types exclusion targeting to YouTube & partners line items. Embedded video, live streaming, and Family content rating exclusion will still be available at the advertiser-level, and then will be applied to child YouTube & partners line items only.

In Display & Video 360 API, all TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION and TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION AssignedTargetingOptions will be removed from YouTube & partners line items.

Assigned targeting inherited by YouTube & partners line items are not retrievable at the line item level, so any targeting of these types inherited from the parent advertiser will continue to not be returned. This will impact responses from assigned targeting LIST requests and attempts to retrieve these resources using advertisers.lineItems.targetingTypes.assignedTargetingOptions.get will return a 404 error.

In Structured Data Files, Line Item files will no longer use the following values in the “TrueView Category Exclusions Targeting” column:

“All Audiences”
“Younger Teens”
“Teens”
“Adults”
“Not Yet Rated”

Generated files will no longer populate these values in the column. The values “Embedded Videos,” “Live Streaming,” “Games,” and “Families” will be populated in the column when the targeting is inherited from the parent advertiser. Line Item file entries for YouTube & partners line items updating the “TrueView Category Exclusions Targeting” column will fail on upload.

To avoid any interruption of service, remove any impacted targeting from YouTube & partners line items using the UI or Structured Data Files upload.

Sunset of Oracle first- and third-party audiences

On September 30, 2024, first- and third-party audiences sourced from Oracle will sunset. Once sunset, these audiences will be removed from any resource targeting and combined audiences. This update will automatically pause any line items that target only sunset audiences, or negatively target any sunset audiences.

You can identify sunsetting third-party audiences in the UI as third-party audiences from providers “Bluekai”, “Datalogix”, and “AddThis”. If you have an external account link with Oracle to import audiences from their platform, check with your relevant team to identify sunsetting first-party audiences. These audiences can’t be easily identified using the Display & Video 360 API.

In the Display & Video 360 API, TARGETING_TYPE_AUDIENCE_GROUP AssignedTargetingOptions will be updated to remove sunset audiences. Requests to add sunset audiences to resource targeting will return a 400 error.

In Structured Data Files, IDs of sunset audiences will no longer be included in “Audience Targeting - Include” or “Audience Targeting - Exclude” columns in Insertion Order, Line Item, and YouTube Ad Group files, as well as the “Bid Multiplier” column in Line Item files. File entries using sunset audience IDs in these columns will fail on upload.

To avoid any interruption of service, review the audiences used in your resource targeting, identify any Oracle audiences, and remove them. If you cache audience ID, make sure to remove any of these audiences from your cache.

Ineligibility of Optimized Targeting for certain bid strategies

On September 30, 2024, line items using the following bid strategies will no longer be able to use optimized targeting:

Maximum views with in-view time over 10 seconds
Maximum completed in-view and audible views
Maximum viewable impressions
Target viewable CPM

At this time, line items that use one of these bid strategies combined with optimized targeting will be updated to turn off optimized targeting.

In the Display & Video 360 API, LineItem resources with targetingExpansion.enableOptimizedTargeting set to True and bidStrategy.maximizeSpendAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_CIVA, BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_IVO_TEN, or BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_AV_VIEWED or bidStrategy.performanceGoalAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_VIEWABLE_CPM will be updated to set targetingExpansion.enableOptimizedTargeting to False. Requests creating or updating LineItem resources with any of these sunset configurations will return a 400 error.

In Structured Data Files, Line Item file entries with either “Optimized vCPM” in the “Bid Strategy Type” column or a combination of “Maximum” in the “Bid Strategy Type” column and “CIVA”, “IVO_TEN”, or “AV_VIEWED” in the “Bid Strategy Unit” column will be updated, if needed, to set the “Optimized Targeting” column to False. Line Item file entries using the sunset configurations will fail on upload.

To avoid any interruption of service, update and verify that your line items using these bid strategies don’t have optimized targeting turned on.

Sunset of “Flight ASAP” pacing for insertion orders

On November 5, 2024, “Flight ASAP” pacing will sunset for insertion orders. All existing Insertion Orders with “Flight ASAP” pacing will be updated to “Flight Ahead” pacing.

In the Display & Video 360 API, InsertionOrder resources with a pacing.pacingPeriod of PACING_PERIOD_FLIGHT and a pacing.pacingType of PACING_TYPE_ASAP will be updated to use a pacing.pacingType of PACING_TYPE_AHEAD. Requests creating or updating InsertionOrder resources with this configuration will return a 400 error.

In Structured Data Files, Insertion Order file entries with “Flight” and “ASAP” values in “Pacing” and “Pacing Rate” columns, respectively, will be updated to an “Ahead” value in the “Pacing Rate” column. Insertion Order file entries using the sunset configuration will fail on upload.

To avoid any interruption of service, update the pacing of any existing insertion orders currently using the “Flight ASAP” configuration.

If you run into issues or have questions about these changes, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Impact of upcoming reporting changes on Bid Manager API

2024-09-03T07:10:00.000-07:00

On October 1, 2024, the Anonymous Inventory Modeling (AIM) reporting dimension will sunset and DST/ROC (Regulatory Operating Costs) and Total Media Cost metrics will become incompatible with YouTube reports in Display & Video 360. This will impact the structure of the reports that can be created and run using the Bid Manager API.

The relevant AIM dimension is defined by Filter value FILTER_ANONYMOUS_INVENTORY_MODELING. Once sunset, queries.create and queries.run requests creating and running Query resources with this dimension will return a 400 error.

The relevant cost metrics are defined by any Metric value using the prefix METRIC_TOTAL_MEDIA_COST_ or METRIC_FEE32_. Starting October 1, queries.create and queries.run requests creating and running Query resources of ReportType YOUTUBE that use these metrics will return a 400 error. In the weeks following October 1, we will update existing YouTube queries that use these values to remove the metrics. In place of total cost metrics, we recommend the use of individual media cost metrics instead, which can be added together with other supported fees to calculate the now unavailable total media cost.

To avoid any interruption of service, review your reports to remove the AIM dimension from any existing reports and all relevant cost metrics from any existing YouTube reports.

Read more about these changes on our release notes.

If you run into issues or have questions about these changes, please contact us using our new Bid Manager API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing v202408 of the Google Ad Manager API

2024-08-21T09:37:00.000-07:00

We're pleased to announce that v202408 of the Google Ad Manager API is available starting today, August 21, 2024. This release brings support for setting contextual targeting with ContentLabelTargeting and VerticalTargeting. It also adds AdsTxtService for reading MCM supply chain diagnostics.

In reporting, the VIDEO_PLACEMENT_NAME dimension has been replaced by the VIDEO_PLCMT_NAME dimension which reflects the updated IAB definition.

For the full list of changes, check the release notes. Contact us on the Ad Manager API forum with any API-related questions.

- Chris Seeley, Ad Manager API Team

Authorized Buyers OpenRTB migration reminder, and updates to blocked categories

2024-08-19T12:10:00.000-07:00

The Google Real-time Bidding protocol is deprecated and will sunset on February 15th, 2025. As previously announced, Google plans to no longer send bid requests to endpoints configured to use that protocol after it is sunset.

Additionally, starting September 1st, the protocol will enter maintenance mode, and stop receiving non-critical feature and quality of service updates. If your real-time bidding integration uses the deprecated Authorized Buyers RTB protocol, Google strongly recommends that you start migrating to either our JSON or Protobuf OpenRTB implementations in order to continue accessing the latest real-time bidding features, and avoid interruptions on the sunset date.

You can use the OpenRTB migration guide as a reference while you work on your migrations.

The OpenRTB protocol uses IAB Content 1.0 taxonomy rather than Google’s product and sensitive category IDs when describing categories blocked by publishers with BidRequest.bcat. You can use the new detectedCategories field in Real-time Bidding API’s creatives resource to find the detected categories for a given creative in IAB’s taxonomy. Google recommends that you use this to reduce bid filtering by only placing bids with creatives having detected categories that aren’t blocked by the publisher. Learn more about changes related to categories.

If you have questions or feedback about how we can ease your migration, please contact us using the Authorized Buyers support forum, or [email protected]">[email protected].

- Mark Saniscalchi, Authorized Buyers Developer Relations

Google Ads API v15 sunset reminder

2024-08-15T06:44:00.000-07:00

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:

Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
Click Google Ads API in the table.
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.
(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]">[email protected].
- Thanet Knack Praneenararat, Google Ads API Team

Improvements to conversion adjustment uploads

2024-08-12T09:26:00.000-07:00

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:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
- ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION_ACTION
- ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION
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:

The following error codes will no longer be returned in responses from the UploadConversionAdjustments method, and will no longer be visible in diagnostic reports:
- ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION_ACTION
- ConversionAdjustmentUploadError.TOO_RECENT_CONVERSION
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?

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.
Modify your application logic and business processes so that you are not tracking the two conversion adjustment errors that are being removed.
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

Promotion of Structured Data Files QA format to general availability

2024-08-08T13:43:00.000-07:00

Today we’re announcing the promotion of the Structured Data Files (SDF) QA format to general availability.

The SDF QA Format was initially released in open beta on May 30, 2024. The QA format allows you to download SDFs for Line Item and YouTube Ad Group resources that use human-readable values, such as display names, in place of numeric IDs to make it easier to review resource settings in bulk. These QA format files are read-only and can’t be uploaded to modify or create Display & Video 360 resources.

The two new file types using this format are Line Item - QA and YouTube Ad Group - QA and are available in SDF v6 and later. These files can be downloaded in the Display & Video 360 interface or by using Display & Video 360 API v3, by either:

Using the FILE_TYPE_AD_GROUP_QA or FILE_TYPE_LINE_ITEM_QA FileType values in a ParentEntityFilter
Providing relevant IDs to new lineItemQaIds and adGroupQaIds fields in an IdFilter

To help you decide whether the SDF QA format is right for you and your integration, we’ve added information and recommendations to the existing Bulk Tools guide.

If you run into issues, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing v17_1 of the Google Ads API

2024-08-07T12:58:00.000-07:00

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:

ShareablePreviewService.GenerateShareablePreviews() generates the URLs for shareable ad previews for enabled and paused asset groups. The URLs are available for a limited amount of time and the expiration date is returned in the response.
AdGroupAdService.RemoveAutomaticallyCreatedAssets() allows you to remove specified automatically created assets linked to Responsive Search Ads.
Support for returning ASSET_GROUP as a new Change Status resource type.
New report for retrieving offline conversion diagnostics, offline_conversion_upload_conversion_action_summary. This supports returning information about the overall health of your conversion upload and adjustment processes at the conversion action level.
Added metrics to the offline diagnostics reports to convey the number of uploaded conversions that are still being processed. See Monitor offline data diagnostics for updated information.
Added segments.sk_ad_network_version which represents the version of the SKAdNetwork API, such as 3.0, 4.0.
Support for segmenting per_store_view based on segments.date.
Support for retrieving information related to standard bidding strategies for video campaigns (Fixed CPM (cost per thousand impression) and Target CPV (cost per view)) using reports.
Added segments.ad_format_type to segment some compatible reports (such as ad_group and campaign based on the video ad format type.

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

2024-08-05T07:27:00.000-07:00

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

2024-08-01T13:41:00.000-07:00

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

Deprecation of Structured Data Files v6

2024-07-30T10:20:00.000-07:00

Today we’re announcing the deprecation of Structured Data Files (SDF) v6. This version will sunset on April 30, 2025.

Migrate to SDF v7 or higher before the sunset date to avoid any interruption of service. Instructions on how to migrate from v6 to v7 can be found in our migration guide.

After April 30, 2025, the following changes will apply to all users:

The default version of partners and advertisers using those versions will be updated to v7.
sdfdownloadtasks.create requests using SDF_VERSION_6 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 new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Watch Performance Max and the Google Ads API On Demand

2024-07-29T07:29:00.000-07:00

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

Display & Video 360 API v2 will sunset on September 3, 2024

2024-07-18T07:27:00.000-07:00

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