Ad inspector is an in-app overlay that enables authorized devices to perform real-time analysis of Google Mobile Ads SDK test ad requests directly within your mobile app. It is included with the Google Mobile Ads SDK and you can enable it with no coding required.

Ad inspector is an in-app overlay that enables authorized devices to perform real-time analysis of Google Mobile Ads SDK test ad requests directly within your mobile app. It is included with the Google Mobile Ads SDK and you can enable it with no coding required.

Ad inspector empowers you to thoroughly test all your ad sources before releasing those changes to your users so you can verify everything is working properly. To help you understand and utilize ad inspector effectively, we published a 7-part ad inspector video series on our Google AdMob YouTube channel.

Each video focuses on a specific challenge in testing your ad integration, offering in-depth tutorials and demonstrations on how to:

Check out our ad inspector documentation (Android, iOS, Unity, Flutter) to learn more. If you have questions, comments, or general feedback about ad inspector, contact us in the developer forum. And remember to subscribe to our Google AdMob YouTube channel for more technical content.

 - Justin Malandruccolo, Mobile Ads Developer Relations

라벨: , , , , , ,

Starting on January 20, 2025, new Performance Max (PMax) campaigns created with the UI will have brand guidelines enabled and require business name and logo brand assets to be linked at the campaign level rather than the asset group level. Brand guidelines is a new feature that allows you to control how your brand is represented in your Performance Max campaign automated assets or formats.

Starting on January 20, 2025, new Performance Max (PMax) campaigns created with the UI will have brand guidelines enabled and require business name and logo brand assets to be linked at the campaign level rather than the asset group level. Brand guidelines is a new feature that allows you to control how your brand is represented in your Performance Max campaign automated assets or formats.

What this means for API users

New PMax campaigns created in the UI with brand guidelines enabled will automatically link BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO via the CampaignAsset resource rather than by using the AssetGroupAsset resource, which may impact integrations that attempt to report on or update these assets. You can check if brand guidelines are enabled for a PMax campaign by referencing the Campaign.brand_guidelines_enabled field.

As of v18 of the Google Ads API, it is not possible to create brand guidelines-enabled PMax campaigns via the API, which means new campaigns must link BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO assets using the AssetGroupAsset resource. In a future release, you will be able to create and fully manage PMax campaigns with brand guidelines enabled.

It is important to note that the same asset requirements will continue to apply to all PMax campaigns regardless of whether or not brand guidelines are enabled. However, BUSINESS_NAME, LOGO, and LANDSCAPE_LOGO asset requirements will be evaluated at the campaign level for campaigns with brand guidelines enabled and the asset group level for campaigns without brand guidelines enabled. You can reference the relevant section of our Performance Max optimization and troubleshooting guide for more information, and as always, contact our team if you need support.

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

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

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

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
라벨: ,

Google Ads has rolled out a new feature that allows Google Ads account administrators to grant access to a service account. Once the access has been granted, you can use the service account credentials to make API calls to that Google Ads account and other accounts in that hierarchy, if applicable. Refer to the service account guide to learn more about this option.

Google Ads has rolled out a new feature that allows Google Ads account administrators to grant access to a service account. Once the access has been granted, you can use the service account credentials to make API calls to that Google Ads account and other accounts in that hierarchy, if applicable. Refer to the service account guide to learn more about this option.

This new approach simplifies the Google Ads API authentication process in two important ways:

  1. If your application works entirely offline without any user interaction, then you no longer need to generate a refresh token. This means you can also avoid other steps such as configuring an OAuth consent screen and performing OAuth App verification.
  2. The new service account flow doesn’t require you to be a Google Workspace user or configure the service account for domain-wide impersonation.

We hope this simplifies your experience when working with the Google Ads API.

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

라벨: , ,

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.

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
LineItemService endDateTime + autoExtensionDays endDateTime
v202408 PublisherQueryLanguageService EndDateTime Not available
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
라벨: , ,

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”.

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
라벨: ,

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.
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
라벨: , ,

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.

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
라벨: , ,

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.
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
라벨:

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.

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
라벨: , , , ,

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.

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
라벨: , ,

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.
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: 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
라벨: ,

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.

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
라벨:

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.

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
라벨: , , , ,

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.

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
라벨: , , , ,

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 ...
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
라벨: , , , , , , ,

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.

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:

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
라벨: , , ,

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.

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
라벨: , ,

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.

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
라벨: , ,

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.

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 adxbuyerapi-support@google.com.

- Mark Saniscalchi, Authorized Buyers Developer Relations
라벨: , , , ,

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.
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 googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team
라벨: ,

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.

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
라벨: , , , ,

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.

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:

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
라벨: , , ,

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.
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
라벨: ,

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 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
라벨: , , ,

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:

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
라벨:

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.

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
라벨: , , ,

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.

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
라벨: , , , ,

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.

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
라벨: , ,

Note: Based on popular feedback, we are extending the sunset date for this change. This feature will continue working in older API versions until v16 sunsets. Sunset Schedule can be found here.

Note: Based on popular feedback, we are extending the sunset date for this change. This feature will continue working in older API versions until v16 sunsets. Sunset Schedule can be found here.

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

라벨: ,

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.

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 & Video 360 API BigQuery Connector.

See our migration guide for more information on migrating to the Display & Video 360 API and the two integration options.

If you have questions or concerns about this migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team
라벨: , , ,

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:

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:

  1. Initialize the Mobile Ads SDK on a background thread
  2. 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 MobileAds to handle other method calls synchronously.

We now recommend calling MobileAds.initialize() on a background thread, enabling the work required on the calling thread to happen in the background. 

import com.google.android.gms.ads.MobileAds
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.launch

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    CoroutineScope(Dispatchers.IO).launch {
      // Initialize the Google Mobile Ads SDK on a background thread.
      MobileAds.initialize(this@MainActivity) {}
      runOnUiThread {
        // Load an ad on the main thread.
        loadAd()
      }
    }
  }
}

Note: When calling MobileAds.initialize() on a background thread, the OPTIMIZE_INITIALIZATION manifest flag is no longer required.

2. Enable optimization flag for ad loading

By enabling the OPTIMIZE_AD_LOADING manifest flag, you can offload most ad loading tasks to a background thread. We recommend enabling this flag in your app's AndroidManifest.xml file to reduce the occurrence of ad loading causing ANRs. 

<manifest>
  ...
  <application>
      ...
      <meta-data
          android:name="com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING"
          android:value="true"/>
  </application>
</manifest>

We’ve updated all of our Android example apps to implement these best practices. For more details on initialization and optimization flags, see Get started and Optimize initialization and ad loading. Contact us if you have any questions or need additional help.

 - Joshua Hui, Mobile Ads Developer Relations
라벨: , , ,

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.

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

We look forward to seeing you!

 - Laura Chevalier, Google Ads API Team
라벨: , , , ,

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.
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_auto_migration_done_date_time
You will also see an alert in the Google Ads UI if your account has been migrated, and assets will appear under your account.

What do I need to do?
If your location extensions were not migrated, and you want to use location assets, you need to create the location assets via the UI or the API.

For questions about the API, please contact us on the forum.

For questions about the UI, please contact us here.
Bob Hancock, Google Ads API Team
라벨:

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 ...
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 Beta expectations and see the following sections.

Highlights:
You can find a complete list of features in the release notes in the GRPC/REST reference sections and accompanying compatibility guides, but here are the highlights:
  • Sub APIs with new features at launch: We are excited to announce an initial set of sub apis which comes with new features:
    • Data Sources: Allows multiple API feed creation and management, improved management of supplemental feeds via creation with linking to primary feeds, and support for other shopping feeds such as promotions.
    • Notifications: Receive push notifications for changes to a given account and product data.
    • Products: Unifying Product & ProductStatuses resources to streamline your workflow, new functionality to support inserting products into non API data sources.
    • Inventory: Improved management with the ability to remove in-store or regional inventories for your products.
    • Accounts: New terms of signing (ToS) functionality via the API and accessing account issues with multi-language support.
    • Local Feeds Partnership: For Point-of-sale data providers, more granular inventory management with availability status submissions and feed labels for inventory.
    • Promotions: Simplified promotion statuses with improved details and support for custom promotion attributes for faster iterations on new features.
    • Quota: Additional fields such as version, sub-api, and adjustments visible through the API to manage your quotas more efficiently.
    • Reports: A new NonProductPerformanceView table which provides insights into non-product performance data such as data on links leading to merchants’ homepage.
  • Merchant API is the future. Going forward, we will start launching new features primarily for the Merchant API which will have the newest Merchant Center features. We recommend you start using the Merchant API and would love to hear your feedback to help shape the future.
  • More features are on the way! Today's release contains many new improvements. Currently, there isn’t feature completeness between the Content API and Merchant API. We will have more features upcoming which are based on establishing parity, your feedback, and completely new features such as creation of file feeds with the Data source Merchant API.
Learn more and check out the following resources:
Benji Rothman, on behalf of the Content API for Shopping Team
라벨: , ,