Useful Links

More Blogs from Google

Today, we are announcing the next
version of the DoubleClick for Publishers (DFP) API - version 201103. In
this release, you’ll find added new targeting features, updated
authentication methods, and increased performance of the reporting service. A full changelog
for v201103 can be found on the release
notes page.

New targeting features

In v201103, two new targeting features have been added: time
and day targeting (day-parting) and user domain targeting
. With day-part targeting, the user can set up which times of
day a particular ad should run, and either in the timezone of the browser
or publisher network. The snippet of code below shows you to target a line
item to only serve ads on the weekends of a
website user.

User domain targeting allows the user to target
specific domains from which to allow or disallow viewing of
ads. The following snippet of code shows you how to restrict ads to not
serve to users coming from IP addresses from “usa.gov” domain.

Along with targeting feature updates, the API has also changed
the way authentication is handled. Previously, a RequestHeader object
could contain both an authToken and an oAuthToken, which would cause an
AMBIGUOUS_SOAP_REQUEST_HEADERexception if both were present. Now,
we’ve replaced both the authToken
and oAuthToken field with an authentication field, which takes a
complex type of either ClientLogin
or OAuth; this enables seamless
integration of new authentication mechanisms.

Notice that in this case the authentication
tag is xsi-typed as ns1:OAuth.
Setting OAuth Authentication header
will still work as it did before. For more information please see the authentication
section of the developer’s guide.

Report enhancements

We’ve also improved the stability of the
ReportService and changed the way reports with custom dates
are fetched. Previous to v201103, ReportQuery could have a
custom startDateTime and endDateTime. To align the
API with the features of the product, the ReportQuery object
now only takes dates for startDate and endDate.
Furthermore, this also fixes an issue where an additional day
past the endDateTime was being returned.

As always, we take developer feedback very seriously and we
look forward to any feature requests on our forum.