Today we’re announcing the beta release of Google Ads API v0_5. With this version, you’ll continue pointing to v0 as your endpoint, however, you'll need to update your client libraries. Here are the highlights:

• Billing. Multiple services are available for managing billing.
  • BillingSetupService
    • Create a new billing setup
    • Cancel an approved billing setup that is scheduled to start in the future
    • Cancel a pending billing setup that is not yet approved
  • AccountBudgetService
    • View all approved account-level budgets, including budget adjustments
    • View currently pending account-level budget proposals (if any)
  • AccountBudgetProposalService
    • Create account-level budget proposal to update a budget or create a new budget
    • View all account-level budget proposals. All approved values and proposed budget values are visible. Approved values will be exposed as fields prefixed with approved_.
• Conversion tracking. Conversion tracking lets you measure the performance of your advertising against your business goals.
  • Conversion actions - Set up and edit the settings associated with your conversion actions, including website tracking and call-conversion tracking
• Shopping. The ProductGroupView resource provides Shopping campaign statistics aggregated at the product group level (also called listing group in the Google Ads API). Results always reflect the current set of product groups. An impression for a product will be attributed to all product groups that contain the product. ProductGroupView provides features equivalent to the Product Partition Report of AdWords API.
• Location and Demographics. You can now create criteria with CriterionType AGE_RANGE, GENDER, INCOME_RANGE, PARENTAL_STATUS, PLACEMENT, PROXIMITY, TOPIC, YOUTUBE_CHANNEL, and YOUTUBE_VIDEO. The GeoTargetConstantService lets you input locations and receive suggested geos.
• Account Management. CustomerService.ListAccessibleCustomers provides the capability to manage Google Ads accounts.

To get started with the API, review these helpful resources:

• Google Ads API Release Notes
• Google Ads API Reference
• Google Ads API Guides
• Google Ads API Client Libraries

The updated client libraries and code examples will be published within the next 48 hours. If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the Google Ads API Team

Since the early days of the AdWords API, we've continually evolved the platform to help you more efficiently and creatively manage large or complex Google Ads accounts and campaigns. This year, we’ve also announced the Google Ads API Beta, which was rebuilt to stay on the edge with advancements in our advertising platform.

To learn more about what's working well, and what could be improved, we're running our annual developer feedback survey on both the AdWords API and Google Ads API. Your answers will be completely anonymous, so we hope you'll take the opportunity to leave feedback on how we can make managing campaigns even easier.

SHARE YOUR FEEDBACK

The survey should take about 15 minutes to complete, and will close on November 15, 2018. Thank you in advance for helping us continue to improve developer experience for everyone.
Cory Liseno, Google Ads API Team

What's changing?
The URL_PERFORMANCE_REPORT in the AdWords API will exclude information for YouTube video placements starting October 30, 2018, in keeping with our data retention policies. As a result, placements where the Url field has a domain of www.youtube.com will no longer appear in the report. New and improved placement reports will be available in one of the upcoming releases of the new Google Ads API.

What you should do
Review your application and workflows and make the necessary changes to ensure that the exclusion of video placements in this report will not cause problems. Watch this blog for updates regarding new placement reports in the Google Ads API.

If you have any questions or need help, please contact us via the forum.

- Josh Radcliff, AdWords API Team

We’re excited to announce our Ad Manager API Workshop on October 31, 2018. It may be Halloween, but there are no tricks, some treats, and a lot of information on how you can get more out of the Ad Manager API.

What is it?

A half-day event featuring technical talks by Google engineers and office hours with Google's Developer Relations team. Agenda with description for each of the talks is available on the registration site.

Who is the target audience?

The event is targeted toward developers who use or are interested in using the Ad Manager API. The talks will be technical, thus technical background is recommended for all attendees. This event is an opportunity for you to learn more about the API's capabilities and its newest features. This is also an opportunity for you to share feedback and influence direction by talking directly with Googlers who work on the API.

Where is it?

Google’s Chelsea Market Office
75 Ninth Avenue,
New York, NY 10011

How do I sign up?

To register, please visit registration site. Seating is limited, and after you register, we will reach back out to you to confirm your spot at the workshop.
 - Donovan McMurray, Ad Manager API Team

On Friday, November 30, 2018, in accordance with the deprecation schedule, v201711 of the Ad Manager API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now is the time to upgrade to the latest release and take advantage of new functionality with Preferred Deals, forecasting, and reporting.

To upgrade, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.

Significant changes include:

• The removal of creativePersistenceType from LineItems, impacting the LineItemService and ForecastService.
• The removal of VpaidLinearCreative and VpaidLinearRedirectCreative as part of the Flash creative deprecation.
• The replacement of old partner metrics with new PARTNER_MANAGEMENT fields.
• Changes to how time zones are handled in Sales Manager and Ad Exchange Historical reports. You should now use timeZoneType.

This is not an exhaustive list, so be sure to check the release notes for a list of all changes. As always, don't hesitate to reach out to us with any questions.

To be notified of future deprecations and sunsets, join the Ad Manager API Sunset Announcements group and adjust your notification settings. If you are an administrator on your network, you can now also receive notifications when an application is making requests to your network using a deprecated version, as explained in this post.

 - Donovan McMurray, Ad Manager API Team

Updated on 10/9/2018 to fix the format of the AdMob application ID. The format of an AdMob app ID is ca-app-pub-################~##########.

Google Mobile Ads SDK v17.0.0 for Android has just been released, and it comes with two important changes that you should be aware of:

1. A tag is now required in AndroidManifest.xml.
2. NativeAppInstallAd and NativeContentAd APIs are deprecated in favor of UnifiedNativeAd.

Required AndroidManifest.xml changes

Starting in version 17.0.0, if you are an AdMob publisher you are now required to add your AdMob app ID in your AndroidManifest.xml file. Once you find your AdMob app ID in the AdMob UI, add it to your manifest adding the following tag:

<manifest>
    <application>
        <!-- TODO: Replace with your real AdMob app ID -->
        <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-################~##########"/>
    </application>
</manifest>

Failure to add this tag will result in the app crashing at app launch with a message starting with "The Google Mobile Ads SDK was initialized incorrectly."

What if I'm using Google Ad Manager instead of AdMob?

Publishers using Google Ad Manager will need to declare themselves as an Ad Manager app with a different tag to avoid the same crash:

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

See the getting started guide (AdMob | Ad Manager) for additional details on how to make this change.

NativeAppInstallAd and NativeContentAd APIs are deprecated

This release also officially deprecates the NativeAppInstallAd and NativeContentAd APIs in favor of the previously released UnifiedNativeAd API. The UnifiedNativeAd APIs offer a consolidated way to render any type of native ad, reducing the number of lines of code needed to integrate native ads by up to 50%.

The following example shows how to load both app install and content ads using the new unified API:

AdLoader adLoader = new AdLoader.Builder(context, "ca-app-pub-3940256099942544/2247696110")
    .forUnifiedNativeAd(new UnifiedNativeAd.OnUnifiedNativeAdLoadedListener() {
        @Override
        public void onUnifiedNativeAdLoaded(UnifiedNativeAd unifiedNativeAd) {
            // Show the ad.
        }
    })
    .build();
adLoader.loadAd(new AdRequest.Builder().build());

Check out the native ads guide to get started with the unified API.

What else changed?

See the release notes for a full list of changes. If you have any questions about the release, please reach out to us on the Google Mobile Ads SDK developer forum.

 - Eric Leichtenschlag, Mobile Ads Developer Relations

We’ve heard your feedback regarding the current API sunset notifications, and today we’re pleased to share some upcoming improvements.

Greater User Control
Network administrators will be able to choose whether or not to receive these notifications via the Notification Settings panel in the Ad Manager UI. Check the box next to Deprecated API in use to opt-in to the notifications. Administrators will be automatically opted-in at launch.








More Meaningful Information

Our communications already include a list of applications that are using the deprecated API version. The improved email notification also shows how many requests each application made to the deprecated API. We hope this will help you prioritize which applications need to be upgraded first and expedite the API upgrade process.


UI Notifications

Alongside the email notification, you will also receive a notification card in the Ad Manager UI. Both will be sent on the second Tuesday of each month.







These updates will be rolling out to network administrators in the coming weeks and we will announce in the release notes when they’re available. As always, upcoming deprecation and sunset dates are available on the deprecation schedule page. If you have any questions or feedback, please feel free to reach out to us on the Ad Manager API forums.

 - Nevin Mital, Ad Manager API Team