Today we're releasing v2.6 of the DCM/DFA Reporting and Trafficking API. This release includes a number of highly anticipated features, such as:
We've also improved
click-through URL management for Display creatives, expanded
custom floodlight variable support, and much more. See our
release notes for full details.
Retiring legacy creative types
Beginning with this release, the DCM API no longer supports creating legacy HTML5 Banner and Image creatives. As
previously announced, these legacy types have been replaced by the new streamlined Display creative.
Additionally, the ability to upload Flash assets into DCM was disabled
back in June. Accordingly, this functionality is also being removed from the API beginning with this release. Previous API versions will continue to support uploading Flash assets until their respective sunset dates, but users are strongly encouraged to begin transitioning to HTML5 now.
Deprecation and sunset reminder
In accordance with our
deprecation schedule, this release marks the beginning of the deprecation period for v2.5, which will sunset on
February 28th, 2017. After this date, any requests made against v2.5 will begin returning errors.
As a reminder, API v2.3 will be sunset on
August 31st, 2016. To avoid an interruption in service, all users are required to migrate off of this version by the sunset date.
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
