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