Today we are releasing v2.2 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:
- User requested enhancements: You asked and we listened! Based on your feedback, new fields--such as computed click-through URL for ad creative assignments--have been added.
- Placement search improvements: You can now search for placements and placement groups by start and end date.
Ins tag support: When the new ins tag is enabled for your account, requests for iframe and javascript tags will return an updated tag format. We've introduced 4 new legacy tag values you can use to access the older versions of these tags, to ensure a smooth transition to the upgraded format. You can begin requesting these legacy tag values today, even if your account hasn't upgraded yet.
Retiring older API versions
Along with this release, we're introducing a new
deprecation schedule and announcing the
deprecation of all versions prior to v2.1. Moving forward, we will generally only support 3 versions of the API and sunset the oldest version 4 months after a new release. In order to help developers adjust to this new schedule, we're providing an extended migration period for users of these newly deprecated versions:
API Version |
Deprecation Date |
Sunset Date |
v1
|
3 Aug 2015 |
29 Feb 2016 |
v1.1
|
3 Aug 2015 |
29 Feb 2016 |
v1.2
|
3 Aug 2015 |
29 Feb 2016 |
v1.3
|
3 Aug 2015 |
29 Feb 2016 |
v2.0
|
3 Aug 2015 |
29 Feb 2016 |
These versions will remain active and supported until the sunset date, and we encourage you to use this time to update your applications.
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!
- Jonathon Imperiosi, DCM API Team
