Expectations of the audience marketplace and a typical configuration payload we pass:
Typically an SSP will have a Third-party audience library, usually known as a marketplace
The marketplace is used during deal curation to select IDless audiences as the targeting criteria packaged with selected inventory
Anonymised synchronises active IDless audiences with such marketplaces using either:
SSP API
Automated file upload (S3 etc)
An example of an automated file upload is shown opposite, although an API is more preferable
seat_id
segment_name
segment_id
segment_price
395883
ANON-001-10292
18112
0.88
Where:
seat_id is the account ID for the relevant curator. Anonymised can run a managed service but would prefer 3rd party curators as long as the SSP can manage the revenue-clearing
segment_name is the anonymised name for the segment, as it appears in the Anonymised audience builder
segment_id is the segment value passed in the bid request that is matched by the SSP to identify the deal to include on the request
segment price is the CPM to be charged at the agreed billing currency
