Category Archives: Ads Developer Blog

The official blog for information about the AdWords, AdSense, DoubleClick and AdMob APIs and SDKs

Improving the accuracy of Publisher Ads Audits for Lighthouse mobile reports

Today we're releasing an update to Publisher Ads Audits for Lighthouse, which focuses on improving the real-world accuracy of mobile reports via simulated throttling. Continue reading to learn more about the new simulated throttling option and how it will affect mobile audit scores.

What is simulated throttling?

Until now, all audit scores were based on the result of loading your page on a desktop CPU over an unthrottled, wired broadband connection. While mobile audits request the mobile version of your page (by identifying as a Nexus 5X phone), the results did not reflect actual mobile CPU and bandwidth constraints.

To address this, we are introducing a simulated throttling option. When enabled, mobile audit scores are calculated by first auditing your page under normal conditions, then using this data to simulate page load performance under mobile conditions. The simulation uses the Lighthouse mobile network throttling preset, which artificially limits both CPU speed and network bandwidth. This approximates the performance of an actual mobile device loading your site over a fast 3G connection.

Note that simulated throttling only applies to mobile audits. Desktop audits will not be throttled regardless of whether this new option is enabled or not.

How does this affect me?

The new simulated throttling option will be enabled by default for all newly generated reports, matching the behavior of other performance auditing tools such as Lighthouse, PageSpeed Insights, and the Chrome DevTools Audits' panel. It can be disabled on a per-report basis by toggling the option in advanced settings.

While metric thresholds have been adjusted to account for simulation, we expect this new option may cause scores to change for many pages that were previously audited without throttling. If you audit your page regularly and have established a performance baseline based on the previous mobile audit behavior, you may need to establish a new baseline to account for these differences.


Questions or feedback about this or anything else ad speed related? Reach out on our GitHub issue tracker.
 - Jonathon Imperiosi, Publisher Ads Audits Team

Major Display & Video 360 API v1 Feature Update

Today we’re providing a major feature update to the Display & Video 360 API v1.

This update includes the following features:
Read the release notes for a more detailed list of this new functionality.

You can get started with the Display & Video 360 API and follow our new guides to begin managing your line items and creating new creatives.

If you run into issues or need help using our new functionality, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

Major Display & Video 360 API v1 Feature Update

Today we’re providing a major feature update to the Display & Video 360 API v1.

This update includes the following features:
Read the release notes for a more detailed list of this new functionality.

You can get started with the Display & Video 360 API and follow our new guides to begin managing your line items and creating new creatives.

If you run into issues or need help using our new functionality, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

Google Ads conversion reporting issues starting April 9

Update (April 10, 2020 19:35 PST): Conversion data in all reports has been fixed.

An issue that impacted Google Ads reporting for Search and Shopping conversions occurring between April 9 and April 10 (Pacific Time) for advertisers using non-last click attribution models has been fixed and the data is now correct in all reports.
If you downloaded any of the fields in the table below or any derivative custom columns using the AdWords API, Google Ads API and Google Ads scriptsbetween April 9th 8:00 PM PST and April 10th 7:20 PM PST, you may have incorrect data in your systems. Please re-download the affected fields to ensure accurate conversions reporting.
We appreciate your patience as we worked to resolve this issue as quickly as possible.

AdWords API Google Ads API beta
Conversions
ConversionValue
ConversionRate
ValuePerConversion
CostPerConversion
AllConversions
AllConversionValue
AllConversionRate
ValuePerAllConversion
CostPerAllConversion
CurrentModelAttributedConversions
CurrentModelAttributedConversionValue
ValuePerCurrentModelAttributedConversion
CostPerCurrentModelAttributedConversion		 metrics.all_conversions
metrics.all_conversions_from_click_to_call
metrics.all_conversions_from_interactions_rate
metrics.all_conversions_from_interactions_value_per_interaction
metrics.all_conversions_value
metrics.all_conversions_value_per_cost
metrics.conversions
metrics.conversions_from_interactions_rate
metrics.conversions_from_interactions_value_per_interaction
metrics.conversions_value
metrics.conversions_value_per_cost
metrics.cost_per_all_conversions
metrics.cost_per_conversion
metrics.cost_per_current_model_attributed_conversion
metrics.cross_device_conversions
metrics.current_model_attributed_conversions
metrics.current_model_attributed_conversions_from_interactions_rate
metrics.current_model_attributed_conversions_from_interactions_value_per_interaction
metrics.current_model_attributed_conversions_value
metrics.current_model_attributed_conversions_value_per_cost
metrics.value_per_all_conversions
metrics.value_per_conversion
metrics.value_per_current_model_attributed_conversion


On April 9, 2020 at approximately 8pm PST, a bug caused Google Ads Search and Shopping conversions occurring between April 9 12:01 AM PST onwards to be underreported for advertisers using non-last click attribution models. This bug impacts reports in all Google Ads interfaces, including any report data downloaded via the AdWords API, Google Ads API and Google Ads scripts. Google Ads bid strategies are not impacted by this issue.
We are actively working on fixing the bug and correcting the conversion data.

- Josh Radcliff, Google Ads API Team

Updates to the AdWords API and Google Ads API

As communities respond to COVID-19, we know that this time presents unique challenges for everyone. Below are updates and resources to help you navigate and plan through these challenging times.

How does this impact the APIs?
We realize you are balancing a lot in your life. Here’s what we’re doing to help:
  • Delaying the sunset of the Google Ads API v1: The Google Ads API’s v1 sunset is delayed until July 29, 2020. The AdWords API will continue to be available for production use.
  • Giving additional time: Any new changes that require updates in your AdWords API and Google Ads API code will be given additional time or will be deferred.
We will continue releasing new versions of the Google Ads API to get new features to you.

What are some customer resources?
Google Ads has provided the following resources for business and customers: Where can I get support?
The Google Ads Help Center posted a delay for non-API related support. This delay includes developer token approvals and changes.

If you have any API questions or need help, you can reach us at [email protected] or on our Google Ads API and AdWords API forum.
Nadine Wang, on behalf of the entire Google Ads API Team

Join the beta for the new AdMob API

Today we’re announcing the open beta release of the AdMob API v1. It offers a new and improved way to interact with AdMob reporting data programmatically.

Built with app publishers in mind, the new AdMob API will replace the need for you to use the AdSense API and provide enhanced capabilities to query AdMob reporting data. For example, unlike the AdSense API that uses different definitions of certain ads metrics for app publishers, the AdMob API includes metrics that are consistent with the AdMob UI.

The AdMob API v1 beta release offers the following benefits for app publishers:

  • Receive metrics that are more accurate and consistent with the AdMob UI.
  • Gain access to mediation reporting programmatically.
  • Integrate newer technologies like JSON REST into your product sooner.

We will continue to make improvements to the AdMob API and we encourage you to join the open beta now and provide feedback to influence the product roadmap before the general release.

How can I join the beta?

The beta is available to all AdMob users. You can start with the Getting Started guide or use the client libraries that we have created for you. Additional client library samples will be coming soon.

Where can I learn more?

If you have any questions or need additional help, please contact us via the forum. We look forward to hearing your feedback.

 - Amira Badreldin, AdMob API team

Changing statuses of app and app engagement ads that do not serve

On April 17, 2020, app ads and app engagement ads that do not serve will have their statuses changed automatically from ENABLED to DISABLED. For each ad group in App campaigns, only the first created ad is ever eligible to serve, so we’re disabling other ads in the same ad group to prevent confusion. This means that you may see some changes in the number of report rows if your queries have a condition that includes ad_group_ad.status for the Google Ads API or AdGroupAdStatus for the AdWords API.

What do you need to do?
If you’re not interested in the disabled ads, you don’t need to take any action. Only beware that the number of report rows returned by your query may change. For example, if your queries have a condition to get only enabled ads, you may see fewer report rows.

If you still wish to see the performance data of the disabled ads, make sure your report queries also include the disabled ads. Note that as they don’t serve anymore, these ads won’t accrue any more performance stats beyond the above-mentioned date.

In case you need more information on reporting, follow the below links:
For the Google Ads API, For the AdWords API, As always, if you have any questions, feel free to reach out to us on the AdWords API and Google Ads API forum.
 - Thanet Knack Praneenararat, Google Ads API Team

Upcoming change to the Google Ad Manager API

On Wednesday April 1st, 2020 existing metrics in the Ad Manager API's ReportService will start returning net revenue instead of gross revenue for Programmatic Guaranteed and Preferred Deals. If your application does not process Programmatic Guaranteed and Preferred Deals revenue data, no action is required.

This change will impact all API versions and reports run in the Ad Manager UI. For more information, see the Ad Manager release notes for March 9th.

To help this transition, new metrics have been added in v202002 to allow you to report on gross revenue in order to facilitate historical comparisons. These metrics are temporary and will be removed in future API versions.


Why are we making this change?

This change brings Programmatic Guaranteed and Preferred Deals into alignment with all other transaction types.

How can I tell if I am impacted?

If you use any of the below metrics and your application processes Programmatic Guaranteed and Preferred Deals values as gross revenue, you are impacted by this change:
  • AD_SERVER_ALL_REVENUE
  • AD_SERVER_CPD_REVENUE
  • AD_SERVER_CPM_AND_CPC_REVENUE
  • TOTAL_LINE_ITEM_LEVEL_ALL_REVENUE
  • TOTAL_LINE_ITEM_LEVEL_CPM_AND_CPC_REVENUE
  • TOTAL_LINE_ITEM_LEVEL_WITHOUT_CPD_AVERAGE_ECPM

What changes do I need to make?

You must update your application to process Programmatic Guaranteed and Preferred Deals values as net revenue before April 1st, 2020. If you need access to gross revenue values after April 1st, 2020, you can use temporary gross revenue metrics added in v202002. These metrics will be available until the end of February 2021.

Net revenue values starting 2020-04-01 Gross revenue values until 2021-03-01
AD_SERVER_ALL_REVENUE AD_SERVER_ALL_REVENUE_GROSS
AD_SERVER_CPM_AND_CPC_REVENUE AD_SERVER_CPM_AND_CPC_REVENUE_GROSS
AD_SERVER_CPD_REVENUE Not available
TOTAL_LINE_ITEM_LEVEL_ALL_REVENUE Not available
TOTAL_LINE_ITEM_LEVEL_CPM_AND_CPC_REVENUE Not available
TOTAL_LINE_ITEM_LEVEL_WITHOUT_CPD_AVERAGE_ECPM Not available



If you have questions about this change or are unsure if it impacts you, reach out to us on the Ad Manager API forums. We'll be happy to check if you're impacted and work with you to update your applications.
 - Chris Seeley, Ad Manager API Team

Deprecation of DBM API v1 and SDF Download Service

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1 and the DBM API v1.1 Structured Data File (SDF) Download service. These services will no longer be supported and will be fully sunset on June 15, 2020. Refer to the table below to verify if methods you’re using will be available in v1.1 after June 15, 2020:


Service Methods Available in v1.1 after June 15, 2020?
Reporting queries.createquery
queries.deletequery
queries.getquery
queries.listqueries
queries.runquery
reports.listreports		 Yes
Line Item Settings lineitems.downloadlineitems
lineitems.uploadlineitems		 Yes
SDF Download sdf.download No. Use the new Display & Video 360 API instead.



If you are using the DBM API v1 Line Item Settings service or Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer details of the changes between v1 and v1.1. Important things to know are:
  • Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure they generated in v1.
  • Responses from listqueries and listreports calls are paginated in v1.1. Users have to update their implementation to traverse multiple pages if they wish to consume more than the first 100 items returned.
  • The Line Item Settings service had no changes between v1 and v1.1. Users only have to update the version they are using.
The SDF Download service is deprecated in DBM API v1 and v1.1. Users should immediately migrate to the new Display & Video 360 API, which was released earlier this week. The Display & Video 360 API offers a new asynchronous SDF Download Service featuring new filter options and a new download format compared to its DBM API counterpart.

Guides are available to help you set up the new Display & Video 360 API, as well as use it to get started downloading SDFs.

- Trevor Mulchay, Display & Video 360 API Team

Preventing App engagement campaigns for prohibited apps

Starting on April 1, 2020, the Google Ads API will prevent the creation of new App engagement campaigns for apps in prohibited categories.

The Google Ads API currently allows you to create App engagement campaigns for any category of app. But if an app from a prohibited category is chosen, those campaigns are prohibited from serving ads. This can lead to confusion among advertisers.

Enabling the API to validate that such campaigns are indeed eligible to serve before their creation will allow developers to take corrective action early on and also ensure client accounts are able to serve their intended ads.

Change details
App engagement campaigns are identified in the API as campaign objects with the following properties. Once this change goes into effect, API calls to create campaigns of the above type will fail if the campaign’s app_campaign_setting.app_id references an app in a prohibited category.

Versions v3 and later of the API will throw a SENSITIVE_CATEGORY_APP error. Earlier versions of the API will throw a more generic UNKNOWN error, since the error code is not published in those versions. These errors may surface from the following services and operations.

API Version Service Operation Error
v3+ CampaignService create CampaignError.SENSITIVE_CATEGORY_APP
v1, v2 CampaignService create CampaignError.UNKNOWN

For instances of error code CampaignError.UNKNOWN, the GoogleAdsError’s details.unpublished_error_code field will indicate, “CampaignError.SENSITIVE_CATEGORY_APP”.

Implementation and support
If you create App engagement campaigns with the Google Ads API, please add error handling for apps in prohibited categories. In order to leverage the new SENSITIVE_CATEGORY_APP error, please upgrade to v3 of the Google Ads API first where possible.

If you’re unable to upgrade versions before the change goes into effect, please check for error code CampaignError.UNKNOWN upon campaign creation, and verify that the error’s details.unpublished_error_code string matches the error name documented in the previous section, to indicate a prohibited category may be in use.

For more details on implementing support for App campaigns, see our App Campaigns developer guide for more information. And as always, if you have any questions about this change, don’t hesitate to reach out to us on the Google Ads API developer forum.
Adam Ohren, Google Ads API Team