Google Ads Developer Blog

Learn with us: Google Ads API webinars

2018-05-29T17:07:00.003-07:00

Thank you to the 100+ viewers from 30 different countries who joined our Google Ads API webinars on Tuesday, May 22! We had some great questions during the Q&A and hope it was helpful for everyone who attended.

For those who couldn’t attend the live events, and for anyone who would like a copy of the presentation, both the slides and a video recording of the event are available below.

Webinar Video (May 22, 2018) [1 hr, 13 mins]
Slide Deck

You can find out more about the Google Ads API in our documentation. Please contact us via the forum if you have any questions.

Adam Ohren, on behalf of the AdWords API Team

Limit line item serving with userConsentEligibility in the DFP API

2018-05-24T11:31:00.001-07:00

Using v201805 of the DFP API, publishers can now limit which line items are shown to users in the European Economic Area (EEA) by setting the LineItem.userConsentEligibility field. (Note: this field only takes effect if you have elected to “Limit line items” on the “EU user consent” page.) The userConsentEligibility field can be set to one of three values:

NONE (default) - Don’t serve for any EEA ad requests
CONSENTED_ONLY - Don’t serve for non-personalized ad requests
CONSENTED_OR_NPA - Don’t limit serving

As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

- Donovan McMurray, DFP API Team

Announcing v3.1 of the DCM/DFA Reporting and Trafficking API

2018-05-24T06:16:00.000-07:00

Today we're releasing v3.1 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:

Support for in-stream audio creatives
Landing page mobile deep link management

Details of these and all other changes are covered in our release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v3.0, which will sunset on November 30, 2018. After this date, any requests made against v3.0 will begin returning errors.

As a reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.

Learn More

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

- Jonathon Imperiosi, DCM API Team

Announcing v201805 of the DFP API

2018-05-15T10:27:00.000-07:00

We're happy to announce that v201805 of the DFP API is available starting today. This release brings several new features for DFP Video advertising services, including a new service for DAI authentication and support for CdnConfigurationService actions.

This version also brings support for interstitial and native AdUnits.

For reporting users, v201805 adds support for filtering on many more AD_EXCHANGE dimensions. It also removes several deprecated dimensions and columns.

For a full list of API changes in v201805, see the release notes.

As always, if you have any questions, feel free to reach out to us on the DFP API forums.

- Chris Seeley, DFP API Team

Join us live at the Google Ads API webinars

2018-05-14T08:56:00.001-07:00

A few weeks ago, we announced the beta release of the Google Ads API. We're offering an introductory look into this new API, at two different times:

Google Ads API Webinar, May 22, 2018 @ UTC 1:00 (9:00 AM (GMT+8))
Google Ads API Webinar, May 22, 2018 @ UTC 13:00 (9:00 PM (GMT+8))

The presentation will cover the new API and its features. Topics include capabilities, architecture, set up, and your first API call.

Please submit your questions now so we can answer them in the webinar. We'd love to hear from you!

If you haven’t had a chance to sign up for the beta, you can still submit an application ahead of the webinar. Please contact us via the forum if you have any questions or need help.
Nadine Sundquist, on behalf of the AdWords API Team

Click measurement changes in AdWords

2018-05-07T15:11:00.000-07:00

Update (5/17): Starting October 30, 2018, parallel tracking will be required for all AdWords accounts. See the AdWords blog post for details.
AdWords now allows you to enable parallel tracking for all advertisers from frontend and API. People who click your ads will go directly to your landing page while their browser handles click measurement requests in the background. This helps reduce lost visits which can happen if a customer clicks on your ad but never sees your landing page because they navigate away before the redirect from your tracking URL completes.

All ads using third-party click measurement will begin using parallel tracking at a later date. However, you should start developing for compatibility as soon as possible to give yourself enough time for the migration. If you implement your own click measurement server or provide this service to your customers, refer to our newly published guide for help with implementation. If you are an advertiser who uses a third-party measurement solution, reach out to your service provider to prepare for the switch.

If you need additional support, please email us at ads-clicktracking-support@google.com.
- Anash P. Oommen, AdWords API Team

Sunsetting Flash in the IMA SDKs

2018-04-24T12:26:00.000-07:00

On May 15, 2018, Google will be sunsetting Flash in the IMA SDKs. This change will affect all users of the Flash IMA SDK, and a very small number of users of the HTML5 IMA SDK.

Changes to the Flash SDK

As of May 15, 2018, attempts to load the Flash IMA SDK will fire an AdErrorEvent.AD_ERROR from the AdsLoader. This is a change to the portion of the Flash SDK that is loaded at run time, and therefore will affect all Flash SDK implementations in production. If you've followed our implementation best practices, your handler for this error will play your content video:

private function initAdsLoader():void {
  ...
  adsLoader.addEventListener(AdErrorEvent.AD_ERROR, adsLoadErrorHandler);
}

private function adsLoadErrorHandler(event:AdErrorEvent):void {
  trace("warning", "Ads load error: " + event.error.errorMessage);
  videoPlayer.play();
}

We strongly encourage all publishers still using the Flash SDK to migrate to the HTML5 SDK. As part of this sunset, we will also be removing the Flash SDK documentation from developers.google.com and removing the Flash samples from GitHub.

Changes to the HTML5 SDK

As of May 15, 2018, the HTML5 IMA SDK will stop supporting all Flash ads. This includes linear, non-linear, and companion ads. If your VAST response includes only Flash media files, the IMA SDK will throw error 403 - VAST_LINEAR_ASSET_MISMATCH for linear ads, and error 503 - VAST_NONLINEAR_ASSET_MISMATCH for non-linear ads. Flash companion ads will fail silently. The HTML5 SDK stopped supporting Flash VPAID ads with the deprecation of the Flash IMA SDK last June.

As always, if you have any questions, feel free to contact us via the support forum.

- Shawn Busolits, IMA SDK Team

Join the beta for the new AdWords API

2018-04-23T11:01:00.001-07:00

Update (5/16): Typo fix.
Today we’re announcing the beta release of Google Ads API v0. The Google Ads API is the next generation of our current AdWords API, and it can be accessed via gRPC and JSON REST from a variety of client environments. As this API gradually rolls out, it will reach full parity with the current API.

What’s in the beta?
For the beta, you have the ability to manage search campaigns from creation all the way to reporting. By getting in early, you’ll get to:

Integrate newer technologies like gRPC or JSON REST into your product sooner.
Provide feedback when requested on the beta in order to influence the new Google Ads API.
Try out features such as the new Google Ads Query Language that gives more querying flexibility.
Start using the API to query metrics with the accompanying resources and then mutate those resources. For example, you can query all the keywords that have zero impressions and then immediately mutate those keywords to change their bids.

The functionality for Google Ads API v0 includes:

Creating, updating, and removing search campaigns.
Managing campaign budgets.
Managing ad groups in search campaigns.
Managing 5 different kinds of ads in search campaigns.
Setting standard and portfolio bidding strategies.
Setting up targeting using keywords in search campaigns.
Retrieving detailed advertiser information.
Reporting on various metrics for search campaigns.

Please see the release notes for more details.

How do I join the beta?
Anyone with an existing developer token can apply to join this beta by submitting an application. People who join the beta are expected to submit feedback in order to help us make improvements.

Once you are approved, start with the Get Started guide, and get familiar with our other guides. We’ve also created client libraries for Java, C#, and Ruby with examples to help get you started.

Where do I learn more?
To get started with the API, our team has put together resources:

If you have any questions or need help, please contact us via the forum.
Nadine Sundquist, on behalf of the AdWords API Team

Content API for Shopping Roundup

2018-04-20T07:54:00.002-07:00

There have been some smaller API updates and announcements that we'd like to let you know about!

We've published a new Getting started with Local Inventory Ads guide to walk you through the process of using the new LIA onboarding features in the Content API.
There's a new codelab available on creating and linking AdWords and Merchant Center sub-accounts!
You can now filter results by destination for Productstatuses and Accountstatuses method calls with the new destinations query parameter. If you don't specify a destination, you'll still only get Shopping-related issues, so there is no change to the default functionality.
You can specify holiday shipping cut-offs for shipping services as well. The supported holidays are available via the Shippingsettings.getsupportedholidays method.
You can specify when a particular shipping service is eligible for products. The new services[].eligibility field allows you to specify whether the shipping service applies to products bought via Shopping Actions and/or when bought in some other manner, such as via your own storefront.
We've added a new Datafeeds.fetchnow method to request an immediate fetch of a scheduled feed. Use this method to get feedback on a newly scheduled feed faster than waiting for the first scheduled fetch.

If you have any questions or feedback about these items or any other questions about the Content API for Shopping, please let us know on the forum.
- Stevie Strickland, Content API for Shopping Team

Structured Data Files v4 now available in the DoubleClick Bid Manager API

2018-04-19T06:24:00.000-07:00

Today we're announcing the general availability of Structured Data Files (SDF) v4 in the DoubleClick Bid Manager API. Highlights of this release include support for:

Bid Multipliers
TrueView bumper ads
Enhanced YouTube tracking
Exchange Targeting settings inheritance

Details of these features and all other changes can be found in the release notes.

All SDF users are encouraged to begin requesting v4 files to take advantage of these new features. To do so, simply pass 4 as the value of 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.

- Jonathon Imperiosi, DBM API Team

Improvements to the DFP API documentation

2018-04-13T12:58:00.000-07:00

An API is only as good as its documentation, which is why we’re pleased to announce some exciting improvements to the DFP API documentation based on user feedback. We hope these changes will make your workflow a little easier.

Additional information on report entities. We have added documentation for each Dimension, DimensionAttribute, and Column that states its UI name. This mapping from API entity names to UI entity names should make it easier to mimic report queries from the UI. Also, each of these report entities now has a list of compatible report types to help you determine which entities can be used with each other before running a report query.

Filtering report entity tables. There are a large number of Dimensions, DimensionAttributes, and Columns over which you can query a report. Also, as mentioned, we have added even more useful information to these entities. In order to better navigate this large body of documentation, you can now filter these entities on their name or description by entering keywords in the textbox that appears above each table.

Overall DFP documentation search. In addition to the reporting documentation improvements, we have also improved the overall search functionality on the DFP API documentation site. When you type a query into the search bar at the top of each page, the list of suggested results are now pulled only from the latest version, which allows more results to be shown instead of showing the same result across multiple versions.

As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

- Donovan McMurray, DFP API Team

Sunset of DFP API v201705

2018-04-09T12:41:00.000-07:00

On Thursday, May 31, 2018, in accordance with the deprecation schedule, v201705 of the DFP API will be sunset. At that time, any requests made to this version will return errors.

If you’re still using this version, now’s the time to upgrade to the latest release and take advantage of new features such as Preferred Deal support, reporting time zone configuration, and reporting currency configuration.

In order 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:

Support for Preferred Deal line items.
Editing AdUnit assignments to Placements now happens in the Placement Service.
AdUnit.inheritedAdSenseSettings has been replaced with AdUnit.adSenseSettings and AdUnit.adSenseSettingsSource.
Old partner metrics have been replaced by new PARTNER_MANAGEMENT fields.

This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

- Gabe Rives-Corbett, DFP API Team

AdWords and DFP client library for Java will soon require Java 8+

2018-03-29T08:15:00.001-07:00

Starting on July 1, 2018, all releases of the Google Ads API Client Library for Java will only be compatible with Java 8 (1.8) and higher.

Why this change is happening
The primary reasons for this change are:

Java 7 was first introduced in July, 2011, and Oracle's support for Java 7 is approaching some key end dates.
Maintaining support for Java 7 means code examples cannot leverage useful features of Java 8, such as lambda expressions, default methods, and stream API support for collections.
Supporting Java 9 in the client library will require upgrading several dependencies to versions that may not support Java 7.
Use of Java 7 among Google Ads API Java Client Library developers is declining, with most users on Java 8 or above.

Next steps
If you are using Java 8 or higher, no action is required.

If you are still using Java 7, you'll have to migrate your runtime to Java 8 or higher. Check out the Java 8 adoption guide from Oracle to get started.

Still have questions? Feel free to file an issue on the library's issues page or contact us via our Google+ page.
- Josh Radcliff, AdWords API Team

Support for v201802 reports in AdWords scripts

2018-03-28T12:26:00.002-07:00

We have added support for AdWords API v201802 reports in AdWords scripts. The key changes in this release include:

A new report type, LANDING_PAGE_REPORT, to provide performance stats for the pages that receive traffic from your ads.
ConversionLagBucket field added to various reports to help you determine how long it takes customers to convert.
New fields added to support Gmail ads.

Read the AdWords API release notes for complete details, including additional features not listed here.

If you use API versioning in your reports, you need to modify your code to use v201802:


var report = AdWordsApp.report(query, {
  apiVersion: 'v201802'
});

If you don't use API versioning, no code changes are required. We are updating the default reporting version to v201710 along with this change, and your reports will upgrade automatically.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
- Mike Cloonan, AdWords API Team

Onboarding for local inventory ads via the Content API for Shopping

2018-03-27T09:17:00.001-07:00

Today, we're announcing the ability to configure your local inventory ads (LIA) settings and link Google My Business (GMB) accounts via the Content API for Shopping. This allows you to onboard accounts for LIA programmatically, instead of needing to manually configure each account separately via the Merchant Center website.

The new Liasettings service lets you perform the following actions via the Content API:

Set your target countries for LIA service and their About pages (if needed)
Add and check the status of contacts for local inventory verification
Request access to a GMB account
Request available business accounts from a linked GMB account
Request and check the status of local inventory verification

In addition, the new googleMyBusinessLink field in the Accounts resource states which business account should be linked. After setting this field, you can provide inventory information for the locations in that business account by uploading product and inventory information either through local product feeds and local product inventory feeds or through the Content API for Shopping with the channel field set to "local".

If you have any questions or feedback about these new features or any other questions about the Content API for Shopping, please let us know on the forum.
- Stevie Strickland, Content API for Shopping Team

Google Media Framework for Android is Deprecated

2018-03-26T11:28:00.000-07:00

As previously announced, as of March 15th, 2018, the Google Media Framework (GMF) for Android is deprecated in favor of the IMA ExoPlayer plugin. All development and support for GMF has been halted. If you are a GMF Android user, we recommend you migrate to the IMA ExoPlayer plugin at your earliest convenience. Alternatively, to keep using GMF Android, you will have to fork and maintain it yourself.

Note: We are NOT deprecating GMF for iOS.

If you have any questions, feel free to contact us via the IMA SDK developer forum.

- Yury Pavlotsky, IMA SDK Team

Ad Exchange Seller REST API Deprecation Reminder

2018-03-21T06:57:00.000-07:00

The Ad Exchange Seller REST API is deprecated. Existing API clients should migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

This migration guide provides instructions for getting started, as well as a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.

For general assistance with the DFP API or your migration, reach out on our developer forum.

- Chris Seeley, DFP API Team

Changes to inactive AdWords accounts

2018-03-05T14:05:00.000-08:00

Update May 8, 2018: Updated roll out month.
What's changing?
Beginning mid-May, 2018, once an AdWords account reaches 15 months without any spend, it will be canceled in order to speed up the AdWords experience and help users stay within the manager account limits. This also means that right now, if your account has reached 15 months without spend, it meets the criteria and will be canceled. After an account is canceled:

get requests for ManagedCustomerService will no longer return the account.
Any AdWords API request that specifies the account's customer ID in the clientCustomerId header will fail with an AuthorizationError.CUSTOMER_NOT_ACTIVE starting with v201802 and an OperationAccessDenied.ACTION_NOT_PERMITTED error for earlier versions of the AdWords API.
Any unspent prepaid amount will be refunded back to the advertiser.
All ads in your account will stop automatically within 24 hours.

Note: Test accounts will not be canceled.

What should you do?
If your application issues AdWords API requests against inactive accounts, make sure you download any relevant data for those accounts before the cancellation process starts. For example, you may want to run reports to gather historical stats for the date range where the account had activity.

If you are using an inactive account in order to test your integration with the AdWords API, consider creating a test account instead. Test accounts will not be canceled by the ongoing cancellation process.

To avoid issues once the cancellation process starts, you can proactively cancel accounts as follows:

Log into your manager account.
Go to the Accounts page, where you can adjust the date range and review the performance metrics for each account under the manager account to help you identify inactive accounts.
Check the box next to each account you want to cancel.
Select Edit -> Cancel account.

To reactivate an account, follow the instructions in the AdWords Help Center. If you are logged in as a manager account, you can show canceled accounts by adjusting the filter in the upper left corner as follows:

Note: If the account is under one or more manager accounts, you will only be able to reactivate the account if doing so will not exceed the manager account limits.

If you have any questions, please contact us via the forum.
- Josh Radcliff, AdWords API Team

AdWords API v201705 and v201708 sunset reminder

2018-03-01T10:13:00.000-08:00

Both AdWords API v201705 and v201708 will be sunset on March 28, 2018. After this date, all v201705 and v201708 API requests will begin to fail. If you haven't already migrated to v201710, we recommend that you skip v201710 and migrate directly to v201802. Please migrate prior to March 28, 2018 to ensure your API access is unaffected.

We've prepared the following resources to help you with the migration:

v201802 migration guide
v201710 migration guide
v201708 migration guide (useful if you are migrating from v201705)
Release notes

As always, if you have any questions about this migration, please contact us via the forum.
- Mike Cloonan, AdWords API Team

Announcing v201802 of the AdWords API

2018-02-28T11:48:00.000-08:00

Today we’re announcing the release of AdWords API v201802. Here are the highlights:

Global site tags and event snippets. The AdWords API now supports global site tags and event snippets, which offer more streamlined tagging for website conversions. You can find more details in the updated conversion tracking guide.
Feed item targeting. The new FeedItemTargetService provides more flexible targeting options for feed items. Check out the updated feeds services guide for details.
New landing page report. The new LANDING_PAGE_REPORT gives a performance breakdown for the pages where customers land after clicking your ads.
Gmail ads. The AdWords API now supports an easier way to create Gmail ads with the GmailAd type. The ads overview guide contains step-by-step instructions to help you get started.

In addition to the above changes for v201802, the following improvements were made in all versions of the AdWords API:

Click types for Shopping Showcase ads. The list of click types in reports now includes values for Showcase Shopping ads interactions.
Member uploads by mobile ID/IDFA and address. All users of the AdWords API can now upload mobile ID/IDFA and address member data to CrmBasedUserList. Previously, these features were only available to whitelisted users.

If you’re using v201705 or v201708 of the AdWords API, please note that they will be sunset on March 28, 2018. We strongly encourage you to skip v201705, v201708, and v201710 and migrate directly to v201802. If you're using v201710, be aware it's now marked deprecated and will be sunset on July 11, 2018.

As with every new version of the AdWords API, please carefully review all changes in the release notes and the v201802 migration guide. The updated client libraries and code examples will be published within the next 48 hours.

If you have any questions or need help with migration, please contact us via the forum.
- Josh Radcliff on behalf of the AdWords API Team

Upcoming changes to ad network type columns in AdWords API and Scripts reports

2018-02-20T11:20:00.001-08:00

On March 19, 2018, we are updating how AdNetworkType1 and AdNetworkType2 columns report zero impression rows related to video networks.

Currently, if you request AdNetworkType1 or AdNetworkType2 columns and request zero impression rows by setting the includeZeroImpressions flag to true, you get back zero impression rows for YOUTUBE_SEARCH and YOUTUBE_WATCH values only if you target these networks in your Advertiser account. After this change, we will always return zero rows corresponding to these network types irrespective of whether you advertise on these networks. Other network types are not affected by this change.

This change makes the behavior of YOUTUBE_SEARCH and YOUTUBE_WATCH network types consistent with the behavior of other network types. Once this change goes live, you may start seeing a higher number of zero impression rows than what you see today when requesting AdNetworkType1 or AdNetworkType2 columns along with zero impression rows.

If you have any questions about these changes, post them in our developer forum.
- Anash P. Oommen, AdWords API Team

Announcing the IMA SDK AMP Extension

2018-02-13T13:57:00.000-08:00

We’re excited to announce that we’ve teamed up with the Accelerated Mobile Pages team to bring you amp-ima-video, an IMA-SDK-enabled video player extension for AMP pages. This extension has been an AMP experiment for the past few months, but today we’re moving from experiment to public release.

amp-ima-video provides an AMP-enabled video player with the IMA SDK pre-integrated, so you can easily play and monetize content on your AMP pages. Simply provide your content URL and an ad tag, and we’ll handle playing back the video and ad(s). The extension currently supports linear in-stream single ads and VMAP playlists. To see it in action, check out the AMP by Example page for the extension.

If you have any questions or issues with the extension, please file them via the AMP issue tracker on GitHub.

- Shawn Busolits, IMA SDK Team

Announcing v201802 of the DFP API

2018-02-13T10:19:00.001-08:00

Today we’re pleased to announce several additions and improvements to the DFP API with the release of v201802. Here are the highlights:

LineItemService: The API now supports the Preferred Deals lineItemType, which allows you to programmatically offer inventory to specific buyers. Check out our Preferred Deals overview for more information.

PublisherQueryLanguageService: There are several new columns available through PQL in v201802. In the Audience_Segment PQL table, the newly added PpidSize column contains the number of unique viewers in a segment. In the Programmatic_Buyer PQL table, the new EnabledForPreferredDeals and EnabledForProgrammaticGuaranteed columns allow you to validate whether a buyer can be associated with a proposal based on the types of proposal line items it contains.

ReportService: A number of reporting features have made it from the UI into the API in v201802. The Demand Channel dimension is now available through the API via DEMAND_CHANNEL_NAME and DEMAND_CHANNEL_ID. Also, the Request Type can be accessed via REQUEST_TYPE. You can now filter proposal line items with the PROPOSAL_LINE_ITEM_TYPE dimension attribute. Finally, you can specify the currency type with adxReportCurrency for Ad Exchange Historical reports. You can read more on how Ad Exchange report currency works in Help Center.

For a full list of API changes in v201802, see the release notes.

Like sands through the hourglass, so are the deprecations of our lives. If you're using v201705 or earlier, it's time to look into upgrading. Also, remember that v201702 will be sunset at the end of March 2018.

As always, if you have any questions, feel free to reach out to us on the DFP API forums.
- Donovan McMurray, DFP API Team

Ending support for iOS 8 in the IMA SDK

2018-02-12T11:05:00.000-08:00

With the release of v3.7.0 of the IMA iOS SDK, we will stop providing forum support and bug fixes for iOS IMA SDK issues specifically related to iOS 8 and below.

What does this mean if an app is currently targeting iOS 8?

There are no changes in v3.7.0 specifically designed to break compatibility, so the iOS IMA SDK will continue to work with iOS 8 in the short term. However, future releases are not guaranteed to continue to work with iOS 8.
Bugs that only affect iOS 8 will no longer be investigated.
If you are using our GoogleAds-IMA-iOS-SDK CocoaPod and want to update to v3.7.0, you'll need to start targeting iOS 9+.

What about other iOS versions?

We periodically stop supporting older iOS versions when adoption levels fall below a certain level. Whenever we end support for a major iOS release, we make announcements on our blog and release notes page.

As always, if you have any questions, feel free to reach out to us on our support forum.

- Shawn Busolits, IMA SDK Team

Upcoming changes to reach report metrics in DCM

2018-02-07T11:03:00.002-08:00

Beginning the week of February 20, a number of reach report metrics in DCM will be renamed. This renaming will modify both API names and column header names in generated report files. These changes are being made to prevent confusion as new reach reports and metrics are developed. The changes are as follows:

Reach Metrics

Old API name	Old column header	New API name	New column header
dfa:activeViewViewableImpressionReach	Active View: Viewable Impression Reach	dfa:activeViewViewableImpressionCookieReach	Active View: Viewable Impression Cookie Reach
dfa:averageImpressionFrequency	Average Impression Frequency	dfa:cookieReachAverageImpressionFrequency	Cookie Reach: Average Impression Frequency
dfa:clickReach	Click Reach	dfa:cookieReachClickReach	Cookie Reach: Click Reach
dfa:impressionReach	Impression Reach	dfa:cookieReachImpressionReach	Cookie Reach: Impression Reach
dfa:incrementalImpressionReach	Incremental Impression Reach	dfa:cookieReachIncrementalImpressionReach	Cookie Reach: Incremental Impression Reach
dfa:incrementalClickReach	Incremental Click Reach	dfa:cookieReachIncrementalClickReach	Cookie Reach: Incremental Click Reach
dfa:incrementalTotalReach	Incremental Total Reach	dfa:cookieReachIncrementalTotalReach	Cookie Reach: Incremental Total Reach
dfa:totalReach	Total Reach	dfa:cookieReachTotalReach	Cookie Reach: Total Reach
dfa:duplicateClickReach	Duplicate Click Reach	dfa:cookieReachDuplicateClickReach	Cookie Reach: Duplicate Click Reach
dfa:duplicateClickReachPercent	Duplicate Click Reach Percent	dfa:cookieReachDuplicateClickReachPercent	Cookie Reach: Duplicate Click Reach %
dfa:duplicateImpressionReach	Duplicate Impression Reach	dfa:cookieReachDuplicateImpressionReach	Cookie Reach: Duplicate Impression Reach
dfa:duplicateImpressionReachPercent	Duplicate Impression Reach Percent	dfa:cookieReachDuplicateImpressionReachPercent	Cookie Reach: Duplicate Impression Reach %
dfa:duplicateTotalReach	Duplicate Total Reach	dfa:cookieReachDuplicateTotalReach	Cookie Reach: Duplicate Total Reach
dfa:duplicateTotalReachPercent	Duplicate Total Reach Percent	dfa:cookieReachDuplicateTotalReachPercent	Cookie Reach: Duplicate Total Reach %
dfa:exclusiveClickReach	Exclusive Click Reach	dfa:cookieReachExclusiveClickReach	Cookie Reach: Exclusive Click Reach
dfa:exclusiveClickReachPercent	Exclusive Click Reach Percent	dfa:cookieReachExclusiveClickReachPercent	Cookie Reach: Exclusive Click Reach %
dfa:exclusiveImpressionReach	Exclusive Impression Reach	dfa:cookieReachExclusiveImpressionReach	Cookie Reach: Exclusive Impression Reach
dfa:exclusiveImpressionReachPercent	Exclusive Impression Reach Percent	dfa:cookieReachExclusiveImpressionReachPercent	Cookie Reach: Exclusive Impression Reach %
dfa:exclusiveTotalReach	Exclusive Total Reach	dfa:cookieReachExclusiveTotalReach	Cookie Reach: Exclusive Total Reach
dfa:exclusiveTotalReachPercent	Exclusive Total Reach Percent	dfa:cookieReachExclusiveTotalReachPercent	Cookie Reach: Exclusive Total Reach %
dfa:overlapClickReach	Overlap Click Reach	dfa:cookieReachOverlapClickReach	Cookie Reach: Overlap Click Reach
dfa:overlapClickReachPercent	Overlap Click Reach Percent	dfa:cookieReachOverlapClickReachPercent	Cookie Reach: Overlap Click Reach %
dfa:overlapImpressionReach	Overlap Impression Reach	dfa:cookieReachOverlapImpressionReach	Cookie Reach: Overlap Impression Reach
dfa:overlapImpressionReachPercent	Overlap Impression Reach Percent	dfa:cookieReachOverlapImpressionReachPercent	Cookie Reach: Overlap Impression Reach %
dfa:overlapTotalReach	Overlap Total Reach	dfa:cookieReachOverlapTotalReach	Cookie Reach: Overlap Total Reach
dfa:overlapTotalReachPercent	Overlap Total Reach Percent	dfa:cookieReachOverlapTotalReachPercent	Cookie Reach: Overlap Total Reach %

Unique Reach (Beta) Metrics

Old API name	Old column header	New API name	New column header
dfa:uniqueReachClick	Unique Reach: Click	dfa:uniqueReachClickReach	Unique Reach: Click Reach
dfa:uniqueReachImpression	Unique Reach: Impression	dfa:uniqueReachImpressionReach	Unique Reach: Impression Reach
dfa:uniqueReachTotal	Unique Reach: Total	dfa:uniqueReachTotalReach	Unique Reach: Total Reach

Questions about this or anything else DCM API related? Contact us via our support forum.
- Jonathon Imperiosi, DCM API Team