2018 Ad Manager API Workshop Slides
We’ve already begun planning for our 2019 workshops, so be sure to check this blog for more updates. If you have general API questions or comments, please reach out to us on the Ad Manager API forums.
platformName
of “ConnectedTv” and an ID of 30004. You can also isolate it in reports using a Device segment named CONNECTED_TV
. Note that even though bidding will only be supported for Display and Video ads, some residual traffic may appear in other kinds of reports so you should still pull the new segment for non Display/Video ad reports.login-customer-id
. You then set the customer you want to interact with in the request as usual. This tells the API the level of manager account hierarchy you want to authenticate with.GoogleAdsService.Mutate
.GoogleAdsService
to enable users to query hotel performance metrics that were previously available in the Travel Partner API with the HotelPerformanceView
. Supported performance metrics are cost, clicks, impressions, and average lead values. Some derived metrics are also precomputed: average position, average cost per click, average cost per thousand impressions, and click-through rate. These metrics can be segmented by:
AdGroupFeedService
, CustomerFeedService
, FeedService
, CampaignFeedService
, and FeedMappingService
.CustomerClient
, which provides the ability to get an expanded hierarchy of customer clients (both direct and indirect) for a given manager customer.CustomerService.CreateCustomerClient
method.CustomerService
now supports mutates.DismissRecommendation
method to the RecommendationService
, making it possible to dismiss the recommendations listed in our guide.SearchTermView
resource is now available, providing metrics aggregated at the search term level. SearchTermView provides functionality similar to the Search Query Performance Report of the AdWords API.UserListService
.CriterionType
LANGUAGE
, CARRIER
, USER_LIST
, USER_INTEREST
and IP_BLOCK
.ADVERTISER_NOT_WHITELISTED_FOR_USING_UPLOADED_DATA
error.CrmBasedUserList
results in a CAN_NOT_MUTATE_SENSITIVE_USERLIST
error if the account is not whitelisted.CrmBasedUserLists
in accounts that are not whitelisted using CampaignCriterionService or AdGroupCriterionService results in an INVALID_ID
error.ContentMetadataKeyHierarchyService
. For video targeting, use ContentBundles
or key-values mapped from content metadata.AbsoluteTopImpressionPercentage
and TopImpressionPercentage
are specific indicators of page location. You can use these metrics to determine when and where your impressions are showing above the organic search results.SearchAbsoluteTopImpressionShare
and SearchTopImpressionShare
are your share of the eligible top impressions. They are the best indicators of the headroom available to show your ads in more prominent positions. If your goal is to bid on page location, you should use these metrics. Bidding by average position is not recommended since:
SearchAbsoluteTopImpressionShare
or SearchTopImpressionShare
metrics in your bidding logic.BillingSetupService
AccountBudgetService
AccountBudgetProposalService
approved_
.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.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.CustomerService.ListAccessibleCustomers
provides the capability to manage Google Ads accounts.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.LineItems
, impacting the LineItemService
and ForecastService
.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:
tag is now required in AndroidManifest.xml.
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."
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.
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.
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
require
path and namespace have changed in this version.The AdWords API Resources | The Google Ads API Resources |
trafficSplitType
gives you greater control over how traffic is split in your trials.ConversionAttributionEventType
field in the CAMPAIGN_PERFORMANCE_REPORT allows you to segment AllConversions
and related metrics by event type (impression or interaction). In addition, the new ConversionAdjustment
and ConversionAdjustmentLagBucket
fields allow you to determine if conversion adjustments were applied and segment metrics by the number of days between the impression and either conversions or adjustments.version
when calling Sdf.download
. For users with workflows that are dependent on older SDF formats, details of the file format changes between versions can be found in the release notes.Accountstatuses
now returns aggregated product statistics.Accountstatuses
now includes the new format for product-level issues.itemLevelIssues
objects now contain human-readable descriptions.Accountstatuses
Accountstatuses
. Like the Merchant Center, you can retrieve the following aggregated statistics: active products, expiring products, disapproved products, and pending products. These statistics are given separately for each combination of destination, channel, and target country. For example:
"products": [{ "country": "US", "destination": "Shopping", "channel": "online", "statistics": { "active": "1542", "expiring": "14", "disapproved": "152", "pending": "743" }, ... }]Here, there are 1542 active products that target the USA that can be used in online Shopping campaigns, 14 active but expiring products, 152 disapproved products, and 743 pending products.
Accountstatuses
itemLevelIssues
field similar to the itemLevelIssues
field added to Productstatuses
earlier this year. Using the contents of this field, you can now see explicitly whether a given issue is impacting the servability of a product and whether the issue needs your attention or just further processing on Google's part.itemLevelIssues
Productstatuses
and Accountstatuses
, the objects in the itemLevelIssues
field now have some additional fields, which contain English descriptions and helpful links for issues that are suitable for surfacing to clients. The following fields have been added:
description
contains a short English description of the issue.detail
contains a detailed English description of the issue.documentation
contains a URL for a web page that can help resolve the issue.itemLevelIssues
object that includes these fields:
{ "attributeName": "image link", "code": "image_link_pending_crawl", "description": "Image not retrieved (crawl pending)", "destination": "Shopping", "detail": "Wait for the product image to be crawled (up to 3 days)", "documentation": "https://support.google.com/merchants/answer/160640", "resolution": "pending_processing", "servability": "disapproved" }What do you need to do?
itemLevelIssues
in both systems, we now consider the old dataQualityIssues
fields deprecated. We will no longer include them in Productstatus
or Accountstatus
resources on Dec 1, 2018, therefore you should migrate to the new itemLevelIssues
fields as soon as possible.Old API name | Old column header | New API name | New column header |
---|---|---|---|
FILTER_ACTIVITY_ID
|
Conversion Pixel DCM ID
|
FILTER_FLOODLIGHT_ACTIVITY_ID
|
Floodlight Activity ID
|
FILTER_FLOODLIGHT_PIXEL_ID
|
Conversion Pixel ID
|
FILTER_DV360_ACTIVITY_ID
|
DV360 Activity ID
|
FILTER_MOBILE_DEVICE_MAKE
|
Mobile Make
|
FILTER_DEVICE_MAKE
|
Device Make
|
FILTER_MOBILE_DEVICE_MAKE_MODEL
|
Mobile Make and Model
|
FILTER_DEVICE_MODEL
|
Device Model
|
FILTER_MOBILE_DEVICE_TYPE
|
Device Type
|
FILTER_DEVICE_TYPE
|
Device Type
|
Old API name | Old column header | New API name | New column header |
---|---|---|---|
METRIC_POST_CLICK_DFA_REVENUE
|
DCM Post-Click Revenue
|
METRIC_CM_POST_CLICK_REVENUE
|
CM Post-Click Revenue
|
METRIC_POST_VIEW_DFA_REVENUE
|
DCM Post-View Revenue
|
METRIC_CM_POST_VIEW_REVENUE
|
CM Post-View Revenue
|
METRIC_PIXEL_LOADS
|
Pixel Load Count
|
METRIC_FLOODLIGHT_IMPRESSIONS
|
Floodlight Impressions
|
Placement
criterion where the url
is exactly adsenseformobileapps.com
will fail and result in a CriterionError with reason INVALID_PLACEMENT_URL
. You can read more about this change in the Google Ads help center.Placement
criterion via the AdWords API, and review and modify your mobile targeting to achieve your campaign goals. You will no longer be able to exclude all mobile apps from targeting using this Placement
criterion, but you can refine your mobile app targeting and exclusions using any of the following criteria: