Products that integrate with Acoustic Exchange as an audience destination configure their data store to accept audience data from Acoustic Exchange. The destination product makes it possible to create an audience that can accept the incoming data from Acoustic Exchange.
The destination receives audience data from Acoustic Exchange through a series of API (application programming interface) calls. The connection method between Acoustic Exchange and the destination is implemented in advance during the integration with Acoustic Exchange. As part of the integration process, the destination indicates the identifiers and attributes that it supports and how it allows the incoming data to be added to its databases. The options that the destination endpoint specifies determine the options that Acoustic Exchange provides during audience sharing.
The destination audience accepts the following types of data, which match those that are provided by the source audience.
- Audience name
- Source endpoint and endpoint provider
- Audience type
- Audience ID
- Audience identifiers
- Audience attributes and attribute types
- Records for each member of the audience
The destination audience must accommodate the incoming records from the source audience. However the field names in the destination might differ from those specified in the source audience. Acoustic Exchange provides you with a way to map identifiers and attributes in the source to corresponding fields in the destination.
Obligations as an audience destination
Acoustic Exchange endpoints that consume audience data are referred to as audience destinations.
When you register an audience destination endpoint on behalf of an Acoustic Exchange user account, you must indicate that the endpoint consumes audience data. You specify the identifiers and attributes that the destination audience contains.
The identifiers and attributes appear in the Acoustic Exchange interface so that users can map the names between the source audience and the destination audience.