2020-06-24 Release

New Audience Management REST API endpoints to complement the Pulse Audience Management functionality and support for OpenRTB SupplyChain object.

Batch upload endpoints

A new set of endpoints, called the Batch upload endpoints, are available to interact with INVIDI Pulse. These endpoints are part of the Audience Management API and complement the Pulse Audience Management functionality by allowing you to populate the Pulse session store with audience data for your viewers.

You do this by uploading an audience data batch file, which refers to a collection of audience data rows. Each audience data row represents a viewer, who is tied to a unique Persistent identifier (PID), and specifies the audience segmentations and audience segments the viewer belongs to so Pulse can target them accordingly. The body of the requests should be encoded using UTF-8 and provided in pipe-delimited text file format.

The audience data batch files are uploaded to and stored in your region's session store. This also means you must prefix the base URL with your region, either eu or asia.

The Batch upload endpoints enable you to:
  • Assign viewers to existing segmentations and segments
  • Update segmentations and segments assigned to viewers
  • Remove audience data for viewers from the session store
  • Cancel an upload of an audience data batch file
  • Retrieve batch progress information and details related to any issues with the provided segmentations and segments

Limitations

  • You can upload only one audience data batch file per audience provider per day.
  • The audience data batch file can contain a maximum of 10 million rows.

Support for OpenRTB SupplyChain object

Pulse now supports sending the OpenRTB SupplyChain object in bid requests to Demand Side Platforms (DSPs). SupplyChain object is a technical specification from the Interactive Advertising Bureau (IAB), and it provides a mechanism to identify all intermediaries involved in selling or reselling of a bid request (an impression), showing the full chain of payment all the way back to the publisher. It is aimed to increase transparency into the origins, paths, and legitimacy of ad inventory.

The SupplyChain object contains a set of nodes where each node represents a specific entity that participated in the selling or reselling of a bid request and was involved in the direct flow of payment for inventory. This object represents the links in the supply chain and is an indicator whether or not the supply chain is complete.

Documentation releases

This release includes the following documentation updates: