placements.generatetags
PLACEMENT_TAG_STANDARD
generatetag
PLACEMENT_TAG_JAVASCRIPT
PLACEMENT_TAG_IFRAME_JAVASCRIPT
SEARCH_DYNAMIC_ADS
REMOVED
Productstatuses.get
Productstatuses.list
includeAttributes
product
Over the past few months, a couple new projects designed to streamline AdMob and DFP mediation have launched: mediation groups, open source adapters, and network-specific guides.
In partnership with some of our mediation partners, we've open-sourced many of the most popular adapters used with DFP and AdMob mediation. You can see for yourself at our GitHub repos for iOS and Android:
In addition to adapter source, there's also a project containing example adapter and custom event implementations, plus a test app.
In addition to open-sourcing the adapters, we've also made importing compiled adapters into your projects simpler by uploading them to Bintray and making them available via jCenter and CocoaPods. Rather than downloading and manually including libraries, publishers can get the correct adapter simply by updating their Podfile with a line like this:
pod 'GoogleMobileAdsMediationMoPub'
...or their build.gradle file with a line like this:
compile 'com.google.ads.mediation:mopub:11.10.1.0'
With many ad networks choosing to distribute their SDKs in the same manner, it's frequently possible to bring a new mediation network into an app with nothing more that a Podfile or build.gradle tweak. For instructions on which gradle artifacts and CocoaPods to use, check the AdMob Mediation Overview (iOS, Android) and look for networks in the "Open source and versioned" section.
Each mediated network is a little bit different. They have their own front-end, their own reporting systems, and their own vocabulary including things like "placement," "location," or "zone." Once you start trying to add a second or third network to your mediation waterfall, things can get confusing in a hurry.
To help publishers navigate through these details, we've created network-specific guides for the mediation partners who have joined our open source repositories. Each one includes step-by-step instructions (with screenshots) that guide a publisher all the way from configuring their account in the mediated network's web site to setting up their mediation stack and importing the right adapter.
For more details, there's no better place to go than the guides themselves. You can find them in the AdMob Mediation Overview (iOS, Android).
If you've got questions about our open source adapters or the best ways to get up and running with mediation, stop by our support forum.
On Thursday, August 31st, 2017, in accordance with the deprecation schedule, v201608 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 like support for creating ImageOverlayCreatives, Partner companies, new team actions, and the change history table. 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:
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.
