Release Notes
  • 2 Minutes to read

    Release Notes


      Article summary

      This is a list of all new features and updates that have been made to DSP API endpoints.


      Audience Groups A and B Now Supported in the Traffic API

      September 11, 2025

      What happened?

      Group A and Group B audience segments are now supported in the API.

      What to do?

      Use the group parameter to target distinct segment groups via the targeting endpoint.


      Weighted Conversions Support in Traffic and Reporting APIs

      September 1, 2025

      What happened?

      Weighted CPA is now supported in the Traffic API through the Line endpoint.  

      What to do?

      Use the new weight parameter in the Traffic API Line endpoint to assign weights to non-reporting only online conversion rules.

      In the Reporting API, include:

      • Metric ID 747 to retrieve data for the Weighted Conversions metric.

      • Metric ID 748 to retrieve data for the Weighted CPA metric.


      Video Ad Placement Changes across both Traffic API and Reporting API

      August 25, 2025

      What happened?

      To align with the latest IAB Video Placement guidelines, the classification of video ad placement has been updated and a new field for Video Ad Placement (IAB) has been introduced within both the Traffic API and Reporting API.

      What to do?

      Within the Traffic API endpoint, use the new videoAdPlcmts parameter for the new targeting types as detailed in the Video Ad Placements Targeting article. The API call for videoAdPlacements parameter for Video_Placement_Type target type will no longer be accepted after October 1, 2025. Any requests made with this parameter after October 1st will receive a 422 status error.

      For the Reporting API, include Dimension Type ID 1240 to retrieve data for Video Ad Placement (IAB).


      Phone Number Audiences Now Supported

      August 12, 2025

      What happened?

      To better align with the DSP UI, phone number audiences are now supported via the email_address  endpoint.

      What to do?

      Use the email_address endpoint and to pass SHA256 encrypted phone numbers as detailed in the Email / Phone Number Audiences article.


      Programmatic Guaranteed Deals Now Supported in the Traffic API

      July 31, 2025

      What happened?

      Programmatic Guaranteed Deals (PGD) are now supported via the Traffic API endpoint. This enables a more efficient way to create and manage PGD deals.

      What to do?

      To create and manage PGD deals, make requests to the agreements endpoint as detailed in the Programmatic Guaranteed Deals article.


      Retrieve All Creative Audit Statuses Now Supported through the Traffic API

      June 30, 2025

      What happened?

      Getting creative audit statuses for all creatives under a Seat, Advertiser, or campaign using a single batch call is now supported via the Traffic API endpoint. This enables an efficient way to check approval statuses for a large number of creatives.

      What to do?

      To retrieve all creative audit statuses, make requests to the creativestatus endpoint as detailed in the Creatives article.


      Third-Party Audio Creatives Now Supported in the Traffic API

      May 22, 2025

      What happened?

      Third-party audio creatives are now supported via the Traffic API endpoint. This enables serving audio from third-party ad servers in addition to hosted audio.

      What to do?

      To create a third-party audio creative, include AUDIO_THIRD_PARTY as a value in the creativeType object in any request as detailed in the Creatives article.



      Was this article helpful?

      What's Next