via the AdMob API forum if you have questions or feedback regarding the AdMob API.
Today we are announcing the launch of two new features in the AdMob API:
New admob.readonly OAuth 2.0 scope
Inventory methods including list apps and ad units
New OAuth 2.0 scope
While the admob.report scope is only intended for reports, the new admob.readonly scope is intended for all read methods, including reports and inventory. We recommend using the admob.readonly scope as it can be used for all read only methods.
Scope
Functionality
https://www.googleapis.com/auth/admob.readonly
See all of your AdMob data. This may include your account information, inventory and mediation settings, reports, and other data. If you agree, this app will be allowed to see, but not make changes to your AdMob data. This doesn't include sensitive data, such as payments or campaign details.
https://www.googleapis.com/auth/admob.report
See ad performance and earnings reports.
See publisher ID, timezone and default currency code.
New methods
We have added the following new methods to the v1beta AdMob API, which allow you to view your AdMob apps and ad units.
How can I start using the new methods and scope?
The beta is available to all AdMob users. You can start with the client libraries that we have created for you.
Where can I learn more?
Feel free to reach out to us via the AdMob API forum if you have questions or feedback regarding the AdMob API.
The Google Ads API Developer Relations team will be hosting a live webinar, Intro to Reporting & the Google Ads Query Language , on December 4 at 10 AM EST (3 PM GMT).Mark your calendar Agenda
Reporting in the Google Ads API vs. the AdWords API
Types of search requests you can perform with the Google Ads API
The syntax and structure of Google Ads Query Language queries
How to discover available fields to construct Google Ads Query Language queries
Prerequisites API Overview documentation or check out this Google Ads API Overview workshop from 2019. In addition, you may find this guide useful to learn about reporting with the Google Ads API, though much of this information will be covered in the webinar.Reminders add the event to your calendar . In addition, you can set a reminder for the event on YouTube by clicking the “Set reminder” button on the YouTube event page .forum or at googleadsapi-support@google.com.
What’s changing?
The Content API for Shopping will gradually roll out improvements to request validation from January 1, 2021 to February 15, 2021 . These changes will be applied to a growing percentage of requests during that time, reaching 100% by February 15, 2021 . The validation improvements will ensure that certain requests that are not in the proper format result in an error instead of having the Content API attempt to infer the request's intent. As long as you are submitting the proper type and structure for each field, you will not be affected by this change.
The following sections describe two examples of incorrectly formatted requests that may fail after January 1st, 2021. If your requests start to fail after January 1st, 2021, please refer to the error message returned and correct the formatting issue.
Example: Providing an invalid structure for a repeated field
This error applies to providing any invalid type for a repeated field, such as providing a list of objects instead of a list of strings, or vice versa.
Example invalid v2.1 request
The following request is invalid because the includedDestinations field requires a list of strings, not a list of objects:
{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"includedDestinations": [{"destinationName": "Shopping", "intention": "default"}]
}
Example valid v2.1 request
To correct this issue, change the list of objects to a list of strings:
{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"includedDestinations": ["Shopping", "SurfacesAcrossGoogle"]
}
Other common fields affected by this change
v2.1:
product.excluded_destinations (a common mistake is providing the v2 format of this field for requests to v2.1)
v2:
product.destinations (a common mistake is providing the v2.1 format of this field for requests to v2)product.sizesproduct.additional_image_linksproduct.shipping
Example: Submitting a string that represents a float instead of an integer
This error applies to providing a string containing a floating point number when an integer is required.
Example invalid v2.1 request
The following request is invalid because the sellOnGoogleQuantity requires a string in int64 format
{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"sellOnGoogleQuantity": "100.0"
}
Example valid v2.1 request
To correct this issue, change the value to an integer:
{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"sellOnGoogleQuantity": "100"
}
Other common fields affected by this change
v2.1:
product.unit_pricing_base_measure.value
v2:
inventory.sell_on_google_quantityproduct.unit_pricing_base_measure.value
What do I do?
We recommend that you address any incorrectly formatted requests before January 1st, 2021 to avoid any disruptions to your application.
If you are already submitting the proper type for each field as described in the Content API for Shopping reference docs , no action is required.
Need More Help?
If you have any questions or need assistance, please reach out to us on the forum .
We are writing to remind you that the Content API for Shopping v2 will sunset on March 29, 2021 . On this date, all requests made against v2 of the Content API will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected.
To help with the migration to v2.1, we have prepared the following resources:
Migration guide -- Explains how to update your applications for v2.1.
Supplemental feeds guide — In v2.1, supplemental feeds replace the v2 inventory service for partial updates to online products.
Local inventory service guide — In v2.1, the local inventory service replaces the v2 inventory service for updates to local inventory.
Release notes -- Lists all changes and new features added in v2.1, organized by release date.
If you have questions about the migration or encounter challenges that prevent you from migrating, we want to hear from you. Please reach out to us on the forum so we can help.
We're happy to announce that
v202011 of the Google Ad Manager API is available starting today. Upgrade to this version to take advantage of new functionality, like support for
Ad Speed reports. Now you can programmatically monitor ad speed, because
fast ads matter to both you and your users.
This release also brings a new ForecastService method to let you explore historical and future impression opportunities. This is backed by the same data as your network's
Traffic Forecast .
For the full list of changes for v202011 check the
release notes . Feel free to reach out to us on the
Ad Manager API forum with any API-related questions.
If you run into issues or need help with these new features, please contact us using our
support contact form .
Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features: If you run into issues or need help with these new features, please contact us using our
support contact form .
Today, we’re announcing the v6 release of the Google Ads API . To use the v6 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published this week. For more information on breaking changes, see the migration guide .
The API now has Change History similar to the Google Ads UI with ChangeEvent
You can now manage user access in your Google Ads account.
Maximize conversion value and maximize conversions are now available as portfolio bidding strategies, which includes Search.
The new Customer.optimization_score_weight
New audience types are available including CombinedAudienceCustomAudience
Where can I learn more? forum .
On Monday, November 30, 2020, in accordance with the
deprecation schedule , v201911 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.
If you’re still using v201911, now is the time to upgrade to a newer release and take advantage of additional functionality. For example,
in v202002 we added a number of video and reporting features.
When you’re ready to upgrade, check the full
release notes to identify any breaking changes, like
Activity and
ActivityGroup IDs
changing from type int to type long in v202005. Then, grab the latest version of your client library and update your code.
As always, don't hesitate to reach out to us on
the developer forum with any questions.
What's changed for Shopping ads
In August 2020, we simplified how you use product data across countries . In the past, you needed to submit duplicate products with separate targetCountry values for each country in which you wanted to serve Shopping ads. Now you can simply configure additional countries of sale for each primary feed in Google Merchant Center to serve ads for the same product in multiple countries. You can also add additional countries on a per-product basis by using the shipping
What's changed for free product listings
In October 2020, we announced that free listings will soon be available across the world . We also removed the ability to use account-level shipping settings to allow ads and free listings to be served in multiple countries. For more information, see the Merchant Center announcement: Use additional countries to determine your reach .
What you should do
As a result of these recent enhancements, we recommend that you do the following when serving ads and listing your products in multiple countries:
Stop submitting duplicate products with separate targetCountry values for each country you want to advertise in.
If you want all of the products in your primary feed to be eligible for ads and free listings in multiple countries, add the additional countries to the feed in Merchant Center .
If you only want specific products to be eligible for ads and free listings in multiple countries, add the additional countries on the shipping
Check out our Content API guide, Targeting Shopping ads and free listings in multiple countries , for examples and additional details.
If you have any questions or need assistance, please reach out to us on the forum .
Starting January 18, 2021, we will start migrating Maximize Clicks bid strategies that still utilize the deprecated target_spend setting to use campaign daily budget pacing instead. This follows last year’s sunset of the target_spend field for Maximize Clicks . After that sunset went into effect, Google Ads has prevented users from creating any new Maximize Clicks strategies that have a target_spend setting.
What’s changing
As part of this migration, any Maximize Clicks bid strategies that still use the target_spend setting may have their maximum CPC bid limit lowered to minimize the performance impact that may result from this change. This would affect the following API fields:
What you can do
You can avoid the above changes by removing the target spend setting on your campaigns’ bidding strategies before January 18, 2021. To do so, unset the following field (set its value to 0) on any existing Maximize Clicks bid strategies:
If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com .
As of October 1, 2020, any Google Cloud app used to obtain credentials for the Google Ads API or AdWords API scope (https://www.googleapis.com/auth/adwords) in its projects (i.e. any new AdWords API or Google Ads API developers) will need to undergo a Google OAuth verification to avoid an unverified app screen for its users. An app, in this context, is defined as a unique OAuth 2.0 Client ID in Google Cloud. This verification is independent and in addition to any reviews conducted as part of the developer token approval process . 3 to 5 business days . Information on how this process fits in the larger task of authorizing requests can be found in our guide . The verification status of a given app can be viewed at the OAuth consent screen of a Google Cloud Project.Google OAuth verification process at their earliest convenience to avoid any business interruptions.forum or at googleadsapi-support@google.com.
Today’s update also includes changes to
how quota is handled in the Display & Video 360 API. The following usage limits are now in effect:
A default daily limit of 86,400 total requests made to the API per project. This limit can be increased on a case-by-case basis to customers who have demonstrated need for a higher limit. A rate limit of 600 total requests per minute. A rate limit of 300 write requests per minute, which are calls to methods (such as create, patch, delete, and bulkEdit) that modify resources. More detailed information 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 run into issues or need help with these new features, please contact us using our
support contact form .
Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:
Today’s update also includes changes to
how quota is handled in the Display & Video 360 API. The following usage limits are now in effect:
A default daily limit of 86,400 total requests made to the API per project. This limit can be increased on a case-by-case basis to customers who have demonstrated need for a higher limit. A rate limit of 600 total requests per minute. A rate limit of 300 write requests per minute, which are calls to methods (such as create, patch, delete, and bulkEdit) that modify resources. More detailed information 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 run into issues or need help with these new features, please contact us using our
support contact form .
Beginning October 1, 2020, any new Google Cloud app with a unique OAuth 2.0 Client ID used to obtain credentials for the Google Content API scope (https://www.googleapis.com/auth/content) in its projects will need to undergo a Google OAuth verification to avoid an unverified app screen for its users. Users of unverified apps that access the Content API will see warnings and the apps will have limited functionality .Using OAuth guide .OAuth API verification FAQs . If you have any questions or need additional help, please reach out to us on the forum .
You can then create Ad GameObjects that reference these Ad Placements entirely from the Unity Editor, which means no need for additional scripts!
Developers don’t need to write code to manage the ad unit. Callback functions and ad unit creation are all managed directly in the Unity UI.
Why use Ad Placements?
We’ve developed Ad Placements to help address the feedback that many of you have shared, which is integrating the Google Mobile Ads Unity plugin APIs requires too much scripting. Now with Ad Placements and their associated Ad GameObjects, implementing Google Mobile Ads into your Unity games should be a lot easier and more intuitive. You can add placements, load ads and show them all from easy-to-use Unity Editor integrations. With this new UI-driven approach, we can help you insert ad placements into your game with almost no additional code.
How do I get started?
See the Ad Placement documentation for a download link to the early access build and instructions to help you get started.
As always, please reach out on our developer forum if you have any questions.
We’re excited to announce a new feature for app developers who use Unity: Ad Placements. It is now available in Open Beta .
What are Ad Placements?
Ad Placements provide a cleaner and more intuitive way to place ad units from Google AdMob in your games. Ad Placements allow developers to add ad units with a Unity Editor interface, making the specification of ad units for your game centralized, re-usable, and decoupled from your scripts.
You can then create Ad GameObjects that reference these Ad Placements entirely from the Unity Editor, which means no need for additional scripts!
Developers don’t need to write code to manage the ad unit. Callback functions and ad unit creation are all managed directly in the Unity UI.
Why use Ad Placements?
We’ve developed Ad Placements to help address the feedback that many of you have shared, which is integrating the Google Mobile Ads Unity plugin APIs requires too much scripting. Now with Ad Placements and their associated Ad GameObjects, implementing Google Mobile Ads into your Unity games should be a lot easier and more intuitive. You can add placements, load ads and show them all from easy-to-use Unity Editor integrations. With this new UI-driven approach, we can help you insert ad placements into your game with almost no additional code.
How do I get started?
See the Ad Placement documentation for a download link to the early access build and instructions to help you get started.
As always, please reach out on our developer forum if you have any questions.
On October 1, 2020, we are upgrading the classification of the authorization scope used for the DoubleClick Bid Manager API ( https://www.googleapis.com/auth/doubleclickbidmanager ) to “sensitive ”. This upgrade is taking place to better secure the DBM API and the data retrieved from it.for the first time will encounter an “unverified app screen” upon attempted authentication. This screen can be removed by submitting your app to our verification process . This process usually takes about 3 to 5 business days. Information on how this process fits in the larger task of authorizing requests can be found in our guide .In anticipation of this requirement, it is recommended that existing apps complete the verification process at their earliest convenience. If you run into issues or need help with this process, please contact us using our
support contact form .
We are excited to announce that the Google Ads API is now generally available. This means you can use the Google Ads API for your production applications with confidence that prior performance issues have all been addressed. Batch processing is now available to everyone.Where can I learn more? forum or at googleadsapi-support@google.com .
Updated (3/16/2021): We have launched the new “pause” behavior on 25% of IMA traffic. This feature will be enabled on 100% of IMA traffic by April 16, 2021. Publishers looking to temporarily disable the new pause behavior may do so using the ImaSdkSettings.setFeatureFlags() API:
adsLoader.getSettings().setFeatureFlags({'disableClickAdPause': true});
This feature flag will be available to publishers to disable the new pause behavior until June 1, 2021 to give publishers more time to make the recommended changes outlined below. After June 1, 2021, this feature flag will no longer function and will become a no-op.
Update (1/14/2021): The new target date for the changes to pause behavior to begin to launch is February 14th, 2021 . Initially these changes will only affect a low percentage of requests in order to allow publishers time to make any adjustments without affecting their entire inventory. These changes will ramp up to 100% of IMA impressions on March 2nd, 2021 .
Update (11/13/2020): The November 9th launch got rolled back due to the release negatively impacting some publishers. These changes are now being delayed until Q1 2021, with a more specific date to follow. The new date has now been updated in the below text.
Update (10/27/2020): The targeted date for the changes to pause behavior is now set for November 9th, 2020 . This has been updated in the below text, instead of the original date of October 13th, 2020.
The IMA SDK is preparing to release changes to pause behavior when user clicks cause navigation away from the page or app. When this happens, the ad will be paused automatically by the SDK. These changes will launch on February 14th, 2021 for a low percentage of IMA requests. By April 16th, 2021 the changes to pause behavior will ramp up to affect 100% of IMA requests.
The IMA client-side SDKs already pause ad playback for ad click-throughs, but these changes add automatic pausing to many other user actions. The IMA DAI SDKs currently do not pause for any click events. For either implementation, if your code does not already provide a way for users to resume ad playback when ads are paused, we recommend adding a way to resume ad playback following ad pause events.
When the SDK automatically pauses the ad, the PAUSEDIf this UI is not shown, the player may be permanently paused on the ad without a way for the user to resume ad or content playback .
Client-side changes
On Desktop web, the SDK will automatically pause when the user clicks on an ad which results in navigation away from the page.
This behavior already exists for mobile web and mobile apps.
On all platforms, the SDK will attempt to automatically pause if the user clicks on the:
Learn more button
Ad click (desktop)
Non-linear ad
Icon click
AdChoices icon
Dynamic Ad Insertion (DAI) changes
On all platforms for DAI, the SDK will attempt to automatically pause if the user clicks on the:
Learn more button
Ad click (desktop)
Icon click
AdChoices icon
Pause events
The table below shows which API is called when a pause event occurs:
Note: For Android, the onPause event is only available on v3.20.0 and later. For previous versions the IMA SDK will not automatically pause ads, and developers will not have to implement these changes.
Please see the following code snippet as an example of setting up a listener for the PAUSED event for a client-side HTML5 IMA SDK implementation:
adsManager.addEventListener(google.ima.AdEvent.Type.PAUSED, function() {
showAdResumeUI();
});
function showAdResumeUI() {
// TODO: Add a play button that resumes playback.
}
Please review your IMA SDK integrations and make any necessary adjustments to handle the pause event so that you’re prepared for when the changes go live on February 14th, 2021 . Please look for announcements about pause behavior changes in the IMA HTML5 SDK release notes . If you have questions about making these changes for your own IMA SDK integrations, feel free to reach out to us on the IMA SDK forum .
Starting September 29, 2020, the default version for all search queries and report queries that use Google Ads Query Language (GAQL) will be updated from v4 to v5. If you're manually specifying a version for your queries, nothing will change. If you haven't already migrated to the new beta search feature , then this doesn't affect you.
var report = AdsApp.search(query, {
apiVersion: 'v5'
});
See the Google Ads API release notes for a complete list of changes in v5. Some highlights for reporting include:
Fetching stats for entity types not explicitly supported by the API, such as Discovery campaigns
Improved policy summary fields for ads with more selectable options
If you have any questions, concerns, or feedback, please contact us via our forum . - Mike Cloonan, Google Ads Scripts Team
We’re constantly working to improve our offerings for Google Publisher Tag (GPT) developers. Whether it's writing guides, producing samples, or building tools like the Google Publisher Console and Publisher Ads Audits for Lighthouse, we strive to equip you with everything you need to succeed.
Update (Feb 1, 2021): Correction to some of the category mappings. this Google Ads Help Center article .October 15th 2020 , these suggestions will be automatically applied if you haven’t already accepted them. Google Ads API, AdWords API and Google Ads Scripts users will see the following changes:ConversionActionCategoryEnumConversionTracker.Category
New Conversion Category
ConversionTracker.Category
Add to cart
LEAD
Begin checkout
LEAD
Purchase
PURCHASE
Subscribe
PURCHASE
Sign-up
SIGNUP
Phone call leads
LEAD
Imported lead
LEAD
Submit lead form
LEAD
Book appointment
LEAD
Request quote
LEAD
Get directions
LEAD
Outbound click
LEAD
Contact
LEAD
Download
DOWNLOAD
Page view
PAGE_VIEW
Engagement
DEFAULT
Store visit
DEFAULT
Store sale
PURCHASE
Other
DEFAULT
Therefore, if you are using the AdWords API to retrieve conversion category types (via reports or services), you will still see existing conversion category types being returned based on the mapping above, which will be different from the migrated new types in Google Ads UI.existing category types . The AdWords API will automatically translate the created conversions to new category types, based on machine learning models. You can find code examples on how to set category type for conversion actions on the AdWords API developer site .ConversionCategoryName, you will see the same existing category types as the ones used in AdWords API, based on the mapping in the above table.forum . - Fei Xiang, Google Ads API Team
Today we’re excited to announce the general availability v1 release of the new AdMob API . It allows publishers to programmatically get information on their AdMob account.
The AdMob API v1 release offers the following benefits for app developers compared with the existing AdSense API used to access AdMob data:
Retrieve metrics that are consistent with how the AdMob UI defines and calculates them
Retrieve mediation reports previously not available through the AdSense API
How can I get started?
The AdMob API is now available to all AdMob users. You can use the Getting Started guide and the client libraries to get started.
If you’re already working with the AdSense API, please refer to our migration guide to get started. Please make plans to migrate to the new AdMob API, as we will sunset access to AdMob data via the AdSense API in the fall of 2021.
If you have any questions, please contact us via the AdMob API Developer Forum . We will be able to provide suggestions on how to best migrate your workflow . We look forward to hearing your feedback.
Today, we're announcing the general release of
Publisher Ads Audits for Lighthouse v1.2.0. The major highlights of this release are:
A number of smaller enhancements and bug fixes are also included. For complete details, see the
changelog on GitHub .
Measuring the impact of ads on the user experience The new cumulative ad shift metric is the first publisher ads audit aimed at measuring the impact of ads on
Core Web Vitals metrics. In particular, this metric provides insight into how ads affect the stability of your page's layout. To learn more about how ads affect layout stability and steps you can take to address this, see our article on
minimizing layout shift with GPT .
The APIs for measuring layout stability are new and still evolving, so it's not currently possible to attribute layout shifts to ads with 100% accuracy. We'll be updating this audit as these APIs mature, so scores may change over time.
Try it out and let us know what you think Publisher Ads Audits v1.2.0 is available to use right now. You can try generating an updated report from the
web app , or grab the latest CLI release from
GitHub or
npm to run locally. Updates to the Chrome DevTools version will land in Chrome Stable with the Chrome 87 release (mid-November).
Have questions about this or anything else Ad Speed related? Interested in contributing? Visit our
GitHub repo .
Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:release notes page.support contact form .
Google Ads API beta v2 will sunset on October 21, 2020. After this date, all v2 API requests will begin to fail. Please migrate to a newer version prior to October 21, 2020 to ensure your API access is unaffected.forum or at googleadsapi-support@google.com .Thanet Knack Praneenararat , Google Ads API Team
Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1.1 Line Item service and the sunset of all deprecated DBM API services on February 26, 2021 . Deprecated DBM API services include the entirety of DBM API v1 and DBM API v1.1 Structured Data File (SDF) Download service . This sunset was originally scheduled for June 15, 2020 , but was postponed due to COVID-19 .DBM API v1 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. Differences to note during this migration include: 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 generated in v1. Responses from queries.listqueries and reports.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. Display & Video 360 (DV360) API .set up the Display & Video 360 API and get started using it to download SDFs and manage your line items .If you encounter issues with your migration or want to report a separate issue, please contact us using our
support contact form .
Today, we’re announcing the v5 release of the Google Ads API beta . To use the v5 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. For more information on breaking changes, see the migration guide .
Return metrics for entities not formally supported in the API, such as Discovery campaigns, are now available. These entities will show UNKNOWN enum values returned. See the release notes for more details.
New request parameter to opt into returning all mutable fields in the response during a mutate.
The API is moving towards using field presence such as optional string and optional double instead of wrapper types such as StringValue and DoubleValue. Your code will be easier to use and simplifies the API with payloads that are significantly smaller. Approximately half of our resources have been updated in this release. The full list is in the migration guide , and our code examples have been updated. The rest of the resources will change to field presence in a future release.
Subfields of AdGroupAd.policy_summaryAdGroupAd.policy_summary
Support for Keyword Planner :
Where can I learn more? forum .
- Trevor Mulchay, Display & Video 360 API Team
- Jonathon Imperiosi, Publisher Ads Audits Team
- Amira Badreldin, AdMob API team
- Chris Seeley, Ad Manager API Team
- Donovan McMurray, Ad Manager API Team
- Samuel Stow, Mobile Ads Developer Relations
