Tag Archives: DoubleClick

DoubleClick Ad Exchange Seller REST API Report changes

On November 17th, 2015, we'll be updating the Ad Exchange Seller REST API to make it consistent with the user interface. Specifically, we'll remove the ability to download saved reports or retrieve the dimensions we retired in April.

Requests made after this date for these dimensions will result in that dimension being ignored and requests for saved reports will result in an error.

As a reminder, the dimensions we retired in April are:

  • AD_FORMAT_CODE
  • AD_UNIT_ID
  • AD_UNIT_CODE
  • DSP_ID
  • EXPANSION_TYPE_CODE
  • PLATFORM_TYPE_CODE

For a full list of available dimensions, please see the AdX Seller REST API documentation.

Follow our Google+ page for other announcements and updates.

-- Dean Lukies, Ads Developer Relations

Multiple scenes and ads in Unity

When developing with AdMob in Unity, it is a common practice to make your banner ads persist across multiple scenes. This blog post will highlight best practices to accomplish this with the Google Mobile Ads Unity Plugin.

The most straightforward approach is to link the lifecycle of ads to that of the scenes they’re displayed in. When transitioning from one scene to another, existing ads are destroyed before leaving the first scene. New ads can then be created and displayed in the next scene.

The downside of this approach is that every scene transition would result in a new banner request. This may not be desirable if scene transitions are frequent and occur quickly.

An alternative is to use a GameObject as a wrapper for banners or interstitials. By default, each GameObject in a scene will be destroyed once the new scene is loaded (unless you use additive scene loading). However, you can make a GameObject survive across scenes by marking it with DontDestroyOnLoad. You can then use the GameObject.Find method to obtain references to the wrapper GameObject from scripts in other scenes.

Here is an example of how to use a GameObject to wrap banner ads:


// FirstSceneScript.cs
void Start() {
// Create a wrapper GameObject to hold the banner.
GameObject myGameObject = new GameObject("myBannerAdObject");
myGameObject.AddComponent<BannerWrapper>();
// Mark the GameObject not to be destroyed when new scenes load.
DontDestroyOnLoad(myGameObject);
}
The BannerWrapper GameObject is a wrapper for a BannerView.

// BannerWrapper.cs
using System;

using UnityEngine;
using GoogleMobileAds;
using GoogleMobileAds.Api;

public class BannerWrapper : MonoBehaviour {

public BannerView bannerView;

void Start()
{
bannerView = new BannerView(
"your_ad_unit_id", AdSize.SmartBanner, AdPosition.Bottom);
AdRequest request = new AdRequest.Builder().Build();
bannerView.LoadAd (request);

bannerView.Show();
}
}

In SecondSceneScript.cs, which is attached to the second scene, you can find a GameObject by name, get the BannerWrapper component, and access the BannerView:


// SecondSceneScript.cs
void Start () {
GameObject myGameObject = GameObject.Find("myBannerAdObject");
BannerWrapper bannerWrapper = myGameObject.GetComponent();
bannerWrapper.bannerView.Hide();
}

By managing your ads efficiently and seamlessly across scenes, you are sure to provide a better ad experience for your users. If you have any questions about Unity integration, you can reach us on our forum. You can also find our quick-start guide linked here. Remember that you can also find us on Google+, where we have updates on all of our Google Ads developer products.

Payment IDs now available in DoubleClick Ad Exchange

Last week, the Trustworthy Accountability Group (TAG) announced the “Verified by TAG” initiative to help increase transparency of digital advertising transactions across the industry. We’re fully supportive of both programs outlined in TAG’s announcement and we’re currently in the process of applying for TAG Registration. To support the adoption of Payment IDs across the ecosystem, starting today our version of Payment IDs is available in DoubleClick Ad Exchange to all buyers globally.

Currently, if a programmatic buyer finds they’ve bought fraudulent inventory, there is no way to directly identify the supply source responsible for the fraud. The Payment ID system we proposed to the TAG Anti-Fraud working group fixes this problem by asking all supply sources (e.g. ad exchanges, ad networks, supply side platforms) of advertising inventory to create and provide unique and persistent anonymous identifiers that link every impression to who is paid in their accounting systems. If a buyer finds invalid activity from any source in their supply chain, these Payment IDs will help the buyer to identify who is responsible and blacklist those suppliers from their campaigns.

We’ve always invested heavily to keep DoubleClick Ad Exchange free of invalid activity and ensure that money spent on our platform only goes to support legitimate publishers, app developers, and content creators. To show our commitment to a better ads ecosystem, accelerate the adoption of Payment IDs, and help DSPs start integrating them, we’ve implemented the standard as it exists today, and we’ll continue to work closely with TAG and others in the industry to formalize an industry-wide Payment ID program. When the TAG Anti-Fraud Working Group has finalized the broader industry standard, we’ll happily make any changes to ensure we are compliant with TAG’s efforts.

"Google has been at the forefront of the fight against digital ad fraud, and this announcement advances our work together to develop an industry-wide Payment ID system. We look forward to continued collaboration with Google and other programmatic leaders through the TAG Anti-Fraud Working Group to create a fully transparent digital ad supply chain that will expose the bad actors and cut off their financial support."
Mike Zaneis, CEO, TAG

Leading programmatic buyers, DoubleClick Bid Manager, Dstillery, Magnetic, MediaMath, Rocket Fuel, The Trade Desk, and Turn have all committed to integrating Payment IDs into their systems in the coming months.

Posted by:

Vegard Johnsen
Product Manager, Google Ads Traffic Quality
Chetna Bindra
Product Manager, DoubleClick Ad Exchange

Payment IDs now available in DoubleClick Ad Exchange

Last week, the Trustworthy Accountability Group (TAG) announced the “Verified by TAG” initiative to help increase transparency of digital advertising transactions across the industry. We’re fully supportive of both programs outlined in TAG’s announcement and we’re currently in the process of applying for TAG Registration. To support the adoption of Payment IDs across the ecosystem, starting today our version of Payment IDs is available in DoubleClick Ad Exchange to all buyers globally.

Currently, if a programmatic buyer finds they’ve bought fraudulent inventory, there is no way to directly identify the supply source responsible for the fraud. The Payment ID system we proposed to the TAG Anti-Fraud working group fixes this problem by asking all supply sources (e.g. ad exchanges, ad networks, supply side platforms) of advertising inventory to create and provide unique and persistent anonymous identifiers that link every impression to who is paid in their accounting systems. If a buyer finds invalid activity from any source in their supply chain, these Payment IDs will help the buyer to identify who is responsible and blacklist those suppliers from their campaigns.

We’ve always invested heavily to keep DoubleClick Ad Exchange free of invalid activity and ensure that money spent on our platform only goes to support legitimate publishers, app developers, and content creators. To show our commitment to a better ads ecosystem, accelerate the adoption of Payment IDs, and help DSPs start integrating them, we’ve implemented the standard as it exists today, and we’ll continue to work closely with TAG and others in the industry to formalize an industry-wide Payment ID program. When the TAG Anti-Fraud Working Group has finalized the broader industry standard, we’ll happily make any changes to ensure we are compliant with TAG’s efforts.

"Google has been at the forefront of the fight against digital ad fraud, and this announcement advances our work together to develop an industry-wide Payment ID system. We look forward to continued collaboration with Google and other programmatic leaders through the TAG Anti-Fraud Working Group to create a fully transparent digital ad supply chain that will expose the bad actors and cut off their financial support."
Mike Zaneis, CEO, TAG

Leading programmatic buyers, DoubleClick Bid Manager, Dstillery, Magnetic, MediaMath, Rocket Fuel, The Trade Desk, and Turn have all committed to integrating Payment IDs into their systems in the coming months.

Posted by:

Vegard Johnsen
Product Manager, Google Ads Traffic Quality
Chetna Bindra
Product Manager, DoubleClick Ad Exchange

Announcing v2.3 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.3 of the DCM/DFA Reporting and Trafficking API. This release brings a number of enhancements, such as:

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.1, which will sunset on February 29th, 2016.

As a reminder, February 29th is also the end of the extended migration window we've provided to users of v2.0 and earlier versions of the API. The current schedule is as follows:

API Version
Deprecation Date
Sunset Date
v1
3 Aug 2015
29 Feb 2016
v1.1
v1.2
v1.3
v2.0
v2.1
4 Nov 2015

To avoid an interruption in service, all users are required to migrate off of these versions by 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!

Changes to validation for AdWords API iTunes AppConversions

What’s new?

The validation for AppConversions will become stricter starting on November 9, 2015. If you’re using AppConversions in v201509 or v201506 with AppPlatform: ITUNES, you’ll need to make sure that you’re using the correct AppConversionType.

What was the old behavior?

When v201509 was first released, the API would not throw an error if the incorrect value was sent in a request for an iTunes AppConversion. The API automatically converted to the correct AppConversionType. For example, if the value DOWNLOAD was passed into v201509 for an iTunes AppConversion, then that value would automatically be converted to FIRST_OPEN.

What is the new behavior?

In v201509, AppConversionType DOWNLOAD changed to FIRST_OPEN for iTunes apps. Here’s what you will need to do:
  • For v201506 or earlier, you must pass in AppConversionType DOWNLOAD rather than FIRST_OPEN.
  • For v201509 or later, you must pass in FIRST_OPEN instead of DOWNLOAD.
Passing in the incorrect value will result in the error DOMAIN_EXCEPTION from the API starting on November 9.

Note: This only impacts iTunes conversions. There will be no changes to the validation for AppConversions with an AppPlatform of ANDROID.

Where can I learn more?

For more information on mobile apps and conversions, check out these guides: Questions? Visit us on the AdWords API Forum or our Google+ page.

Investing in choice: New Viewability options on YouTube

Cross-posted from the Google Agency Blog
If you can’t measure it, how do you know it worked? With this simple principle in mind, we’ve been investing in a broad set of measurement solutions for brands through a combination of product innovation with our own solutions like Brand Lift and Active View and partnerships with leading third parties like comScore and Nielsen on GRPs.

Viewability has long been a focus for us. Built on the foundation of our Active View technology, we launched the ability to buy only viewable impressions on the Google Display Network back in December 2013 and recently completed moving over the last advertiser campaigns from CPMs to viewable CPMs. We’ve worked to ensure viewability rates on YouTube are amongst the industry’s highest. And Active View now works seamlessly across video, display, mobile web and mobile apps (on YouTube and for publishers using DoubleClick for Publishers), and has been adopted by over 80% of advertisers using the DoubleClick platform.

With the MRC-defined industry standard as a base-line for viewability, we are also helping advertisers and agencies go beyond transacting on the industry standard to also measure individual viewability objectives. In order to support this we have begun launching supplementary metrics in Active View, like the ability to see average viewable time and soon when an ad is 100% in view for any length in time. These are the first few in a lineup of supplementary metrics that will provide advertisers with additional data points relevant to their specific campaigns and needs.

Announcing 3rd party viewability reporting on YouTube - bringing you more choice

Today, we're continuing our approach of driving product innovation and supporting choice by announcing that we're broadening the options for advertisers measuring viewability on YouTube. Along with Active View, advertisers will also be able to choose from third party vendors.

Moat, Integral AdScience, comScore and DoubleVerify are a select set of third party vendors that have been approved to report ad viewability on YouTube, beginning with Moat in early 2016. Through these partnerships, we’ll continue to expand measurement options for marketers on YouTube, while maintaining the highest levels of security and privacy for users, advertisers and creators.
“Independent 3rd party verification is extremely important to ensuring that our clients’ media is running as effectively and efficiently as possible. As a long-time partner, IPG Mediabrands is pleased to see Google continue its work to move the industry forward on viewability by allowing independent verification of YouTube, and applaud this recent decision.”
Mitchell Weinstein, SVP Ad Operations, IPG Mediabrands

Keith Weed, Chief Marketing and Communications Officer at Unilever added:
"Having partners like Google address these challenges helps to push the entire industry forward. This move will generate better industry-wide standards across viewability and third party verification practices and continues the momentum in the right direction."
Keith Weed, Chief Marketing and Communications Officer, Unilever
Stay tuned for continued investments in the viewability space, including ongoing product innovation updates to Active View as well as additional partnerships. Together with our partners, our goal is to help our clients measure every moment that matters.
Posted by Sanaz Ahari
Group Product Manager, Brand Measurement, Google

Bing Shopping Campaigns are now part of the DoubleClick Search Commerce Suite

The holidays are a critical time of year for search marketers, as consumers increasingly research and complete their holiday shopping online. To help you win the moments that matter this holiday season, we recently announced several new features and the DoubleClick Search Guide to the Holidays.

Today, we’ve got another special gift to continue the holiday spirit: Bing Shopping Campaigns are now part of the DoubleClick Search Commerce Suite.

Bing Shopping Campaigns for Bing Ads make it easier and faster to advertise your products from your Bing Merchant Center store online. This streamlined way of getting Product Ads up and running on Bing is also driving meaningful impact for advertisers.

“According to a recent report, Merkle/RKG clients saw Bing Product Ads’ click volume increase by 332% year-on-year.”1
Brian Utter, General Manager of Network and Demand Management, Microsoft

With the addition of Bing Shopping Campaigns to the DoubleClick Search Commerce Suite, you can easily extend the reach of your product-focused advertising. You’ll be able to manage, automate, and measure Bing Shopping Campaigns using the full range of DoubleClick Search tools, the Performance Bidding Suite, Adaptive Shopping campaigns, and Purchase Detail reports.

Learn how to get started with Bing Shopping Campaigns in DoubleClick Search today.

Posted by Henry Tappen
Product Manager, DoubleClick Search

1 Merkle/RKG Digital Marketing Report for Q3 2015

Proguard and AdMob mediation

If you’re an Android developer who uses ProGuard to post-process builds, you already know the improvements it can make to APK size and speed. Just as handy, though, is its ability to obfuscate your compiled code by stripping out debug information and renaming classes, methods, and fields to generic identifiers. It’s a great way to discourage reverse-engineering of your application. If you’re an AdMob publisher who uses mediation, however, you need to take special care when configuring ProGuard in order to avoid obfuscating some of the code used in the mediation process.

AdMob mediation needs two classes to maintain their original names in your final APK: AdUrlAdapter and AdMobAdapter. If either of those has been renamed by ProGuard, it can cause the SDK to incorrectly return “no fill” responses for the AdMob demand in your mediated ad units.

The good news is that it’s easy to avoid this problem. Just add the following two keep options to your ProGuard configuration file:


-keep class com.google.ads.mediation.admob.AdMobAdapter {
*;
}

-keep class com.google.ads.mediation.AdUrlAdapter {
*;
}

These options instruct ProGuard to avoid renaming the two classes, and to leave the names of their fields and methods unobfuscated as well. With the original names intact, the mediation system will be able to instantiate them dynamically whenever they’re needed, and your otherwise obfuscated application won’t miss out on any AdMob impressions.

The third-party networks your app mediates may also need certain classes exempted from obfuscation. Be sure to check with those networks to find out if they have recommendations for ProGuard configuration.

If you have technical questions about this (or anything else relating to the Google Mobile Ads SDK) stop by our forum.

tags: android, admob_mediation, mobile_ads_sdk

Native Ads on DoubleClick boost Trovit’s mobile CPMs by 120%

As consumers spend more and more time on their mobile phones, providing ad experiences that respect their context is more important than ever before. Accordingly, publishers are increasingly embracing native ads -- highly customized advertising units that seamlessly integrate in a user’s content experience without being disruptive. However, creating and delivering these ads can be a challenge. That is why earlier this year we launched Native Ads on DoubleClick, and publishers like Trovit are beginning to see the results.

European publisher Trovit, a classified search engine for property, jobs, cars, products and holiday rentals, had over 50% of its total traffic in some countries coming from mobile devices. To grow mobile revenue while delivering better ad experiences to users, Trovit tested native ads on their apps, powered by DoubleClick, in two of their markets. Based on the promising tests, they expanded their native ads strategy to six more markets. The results: net revenue grew significantly with CPM growth up to 120% in certain markets.

Learn more about Trovit’s strategy and how DoubleClick helped here.

Posted by Nataliya Kozak
Product Marketing Manager, DoubleClick