ClickType
getServiceLinks()
mutateServiceLinks()
AdWords scripts now fully support responsive ads, image ads, HTML5 ads and multiple Gmail ad formats. See our guide on ad types and related code snippets to learn more about using these ad formats in Scripts.
This update also introduces a media service which can be used to upload and query media for use in ads. See our ad media guide for a more detailed overview of media support.
If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
- Anash P. Oommen, AdWords Scripts Team
We are making two changes related to how various conversion-related stats are retrieved in AdWords Scripts.
New methods for Conversion stats
We are reintroducing two methods in the AdWordsApp.Stats and MccApp.ManagedAccountStats classes to work with Conversions.
Note: Since Conversions is a stat of type Double, the equality operators (= and !=) won’t work with these new methods when using the withCondition filters or comparing values in code. Instead, you need to use comparison operators like < and > or round Conversions off to an Integer.
Double
=
!=
withCondition
<
>
Sunsetting ConvertedClicks
As part of sunsetting Converted clicks in AdWords, we are deprecating the getConvertedClicks() and getClickConversionRate() methods in the AdWordsApp.Stats and MccApp.ManagedAccountStats classes. These methods will be sunset on February 21, 2017.
If your scripts use these methods, update them to use the new Conversion stats methods if applicable before February 21, 2017 to ensure they continue to work.
If you have any questions about these changes please reply to this email or post them on our developer forum and we'll be glad to help you.
Understanding some of the finer details of DFP's OAuth2 flows can come in handy when the unexpected happens.
All DFP API requests are authenticated using access tokens. You can think of these as short-lived (about one hour) passwords. When making a request, you include the access token in the HTTP header:
Authorization: Bearer ACCESS_TOKEN
Every access token is tied to a specific user and one or more API scopes. The scopes control which Google APIs the access token is valid for. The scope for DFP is:
https://www.googleapis.com/auth/dfp
When authenticating as a dedicated API user like a service account, make sure that user is configured with your desired teams and role in DFP. There's no requirement that API users have administrator access.
POST https://www.googleapis.com/oauth2/v2/tokeninfo?access_token=MY_ACCESS_TOKEN { "issued_to": "1234567890-aabbccddgh123.apps.googleusercontent.com", "audience": "1234567890-aabbccddgh123.apps.googleusercontent.com", "scope": "https://www.googleapis.com/auth/dfp", "expires_in": 3496, "access_type": "offline" }
If your refresh token stops working, there are a few possible causes:
The simplest solution to all of these is to create a new client and generate a new refresh token for a current DFP user. Remember that the refresh token is tied to the account that authorizes the application, and not the user who created the OAuth2 client. When accepting the OAuth2 authorization prompt, verify that the user in the top right corner that is logged in is correct:
If OAuth2 still gives you a headache, we're happy to troubleshoot with you. Just reach out to us on our developer forum.
- Chris Seeley, DFP API Team
If you're still working with this version, we strongly encourage you to begin migrating to the most recent release to avoid an interruption in service. If you're not sure, or would like to know more about the migration process, refer to the migration guide.
As always, feel free to reach out to us with any questions that you have. To receive future updates like this directly in your inbox, join the DCM API Announcements group and adjust your notification settings.
- Jonathon Imperiosi, DCM API Team
Following its launch at the 2016 Game Developer’s Conference, AdMob’s mediation support for rewarded video ads has been a hit with publishers and users alike, with rapid adoption on both Android and iOS platforms.
Our growing list of mediation partners includes eight different ad networks. Choosing AdMob for your rewarded video mediation platform gives you access to ad content from all of them, while you develop against a single API from AdMob. Now, with the launch of custom events for rewarded video, you can also request and display rewarded videos from ad networks that are not directly supported by AdMob.
Our implementation guide for rewarded video adapters (Android | iOS) outlines how to implement an adapter that can serve rewarded video ads from a third party ad network. Special attention should be paid to steps specific to custom events that are summarized below:
To define a custom event, you must first create it in the AdMob interface at apps.admob.com. You can find instructions for creating a custom event in this help center guide.
The optional server parameter passed to your custom event is accessed via a special key. Here’s an example showing how to access the value in a rewarded video adapter:
String parameter = serverParameters.getString( MediationRewardedVideoAdAdapter.CUSTOM_EVENT_SERVER_PARAMETER_FIELD);
NSString *parameter = [self.connector.credentials objectForKey:GADCustomEventParametersServer];
You can find additional documentation on rewarded video ads in our Get Started guides (Android | iOS), and more information about mediation is available in our mediation guides (Android | iOS). For any other questions about rewarded video mediation, you can reach us through our developer forum.
If you're still using these versions, now's the time to upgrade to the latest release and take advantage of new features like HTML5 creatives, programmatic support, and retrieving saved report queries. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library, and update your code.
Significant changes include:
ApproveSuggestedAdUnit
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.
CANNOT_ATTACH_CRITERIA_AT_CAMPAIGN_AND_ADGROUP
Episode nine of The Mobile Ads Garage is live on YouTube! If you haven't seen it before, The Mobile Ads Garage is a video tutorial series that covers how to use the Mobile Ads SDK to display ads from AdMob and DoubleClick for Publishers. Each episode covers one aspect of the SDK, breaks down the feature, and shows screencasts of real implementations on both Android and iOS – all in a friendly format.
In this episode of The Mobile Ads Garage, we discuss mediation, which is a way for publishers to get multiple networks of advertisers competing to display ads in their apps. We’ll show you how AdMob mediation works and what it can do for your business. Learn the pros and cons of mediation, see the details of implementation, and find out whether it’s right for your app. You'll also get screencasts for Android and iOS showing the integration of a third-party SDK, plus links to samples, written resources, and Gary the Graphics Guy acting like his usual, snarky self.
If you like the video, save the Mobile Ads Garage playlist to your YouTube Playlist collection and you'll never miss an episode.
We’d love to hear which AdMob features you’d like to learn more about. The comment sections for the videos are open, and you're welcome to toss out ideas for new episodes and examples you'd like to see. If you have a technical question relating to something discussed in one of the episodes, you can bring it to our support forum.
getCustomers()
--
HasQualityScore = false
var report = AdWordsApp.report(query, { apiVersion: 'v201607' });
Have you ever asked yourself, Can I use the IMA SDK and Google Cast together to display videos with ads on a cast-enabled device? The answer is, yes you can!
We’ve put together a new section of guides and examples that show you how to add cast support to your IMA SDK implementation. They also explain the logic behind requesting ads on the sender and receiver devices. We’ve included both Android and iOS example sender apps, and an example HTML5 receiver.
We recommend familiarizing yourself with the Google Cast SDK as well as the IMA SDKs for Android, iOS and HTML5 before diving into these examples.
If you have any questions about these examples, feel free to contact us via the support forum.
UploadConversion
Clicks
attributionModelType
dataDrivenModelStatus
If you’re using v201603 or v201605 of the AdWords API, please note that they’re now deprecated and will be sunset on October 31, 2016 and February 28, 2017, respectively. We encourage you to skip v201607 and migrate straight to v201609.
As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201609 migration guide. The updated client libraries and code examples will be published shortly.
If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page.
- Josh Radcliff, AdWords API Team
