DoubleClick for Publishers (DFP) added a series of features in the upgraded DFP service to help publishers manage and control audience data through one platform, integrated directly with their primary ad serving technology, informs Sean Harvey, Product Manager.
“This first release is focused on first-party segments – as a publisher, you will have the ability to define your own user audience based on criteria that you define (e.g., sports enthusiasts, travel readers),” explains Harvey.
First party audience segmentation was available in the existing DFP service, and is now integrated seamlessly with the upgraded DFP service. First party segmentation is a great tool for publishers.
Explaining, “First-party segmentation involves no implementation or integration effort by you. Simply define the criteria you want for your audience segments, in DFP and DoubleClick technology does the work of populating them directly from the ad tag. Once you’ve defined your audience you can use it to increase the direct sales value of undersold inventory, and gain insights on how different audience segments are engaging with content across your site. We have designed it to be seamless, easy to use and to put you in control of your data,” Harvey said.
Also, the newest version of the API, v201203, is now available and includes a brand new testing environment, read-only access to video creatives, team level filtering, and more.
Here is a list of features that can be found in this release:
Starting v201203, you’ll be able to create test networks, which offer a wider range of functionality than the existing sandbox networks. “To create test networks, you’ll need a new Google account. Once you’ve called NetworkService.makeTestNetwork() with that account, you’ll sign in to test networks the same way as production, without having to sign up for a DFP account,” explains Adam Rogal, DFP API Team.
Additionally, all SOAP requests can now be sent to https://www.google.com instead of https://sandbox.google.com; moving from test networks to production now will only require you to change your network code.
Network codes will now be required for all requests except NetworkService.getAllNetworks() and NetworkService.makeTestNetwork(). “This change will reduce latency for some requests and will make it easier for you to keep track of which requests are going to which networks, especially now that test and production networks have the same domain for requests,” Rogal explained.
Video creatives are now read-only accessible through the CreativeService.
Teams – In v201203, you’ll be able to set team IDs on inventory, orders, and company. Then, when calls are made with that user, only objects that belong to their team will be returned. You will also receive an error if you attempt to update an object that you don’t have access to.