In Acoustic Exchange, the database definition specifies identifiers and attributes that are expected in the audience and event data that you exchange through Acoustic Exchange.
When users share audiences, they can map identifier and attribute names between source and destination endpoints. In the Specify database definition section of the Integration Manager, you define the identifiers and attributes that Acoustic Exchange users see when they share an audience.
The identifiers and attributes that you define in the Specify database definition section display on the Source to destination mapping screen of the Share audience wizard in Acoustic Exchange. Users must map an identifier that is defined in the source audience to a corresponding identifier in the destination audience. For example, emailAddress in the source might map to email in the destination.
Acoustic Exchange users have the option to map one or more audience attributes in the source audience to corresponding attributes in the destination audience. For example, zip code in the source might map to postal code in the destination.
Using the Integration Manager to define the marketing database for your endpoints enables you to save time and to maintain consistency across endpoints. However, if you need to vary the definition for the different endpoints that you create, you can use the following Acoustic Exchange APIs, to set the definitions individually.
Please sign in to leave a comment.