Update (Sep 1, 2020): Support for path and path attribution report types is now available in v3.4. It has been added back to this post.
Update (Aug 7, 2020): Support for path and path attribution report types, originally listed in this blog post, was not included in the initial release of v3.4 of the DCM/DFA Reporting and Trafficking API. It has been removed from this post.
Today we're releasing v3.4 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:
Details of these and other changes are covered in our
release notes.
Deprecation and sunset reminderIn accordance with our
deprecation schedule, this release marks the beginning of the deprecation period for v3.3, which will sunset on
February 28, 2021. After this date, any requests made against v3.3 will begin returning errors.
Learn MoreAs 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!
- Nikita Agarwal, DCM API Team
