Acoustic Exchange requires that source and destination endpoints publish and receive event and audience data through an authenticated connection.
Source and destination endpoints establish an authenticated connection with Acoustic Exchange by presenting an authentication key.
Acoustic Exchange establishes authenticated connection with endpoints through methods that are defined by the endpoint. Each endpoint must provide Acoustic Exchange with the required connection and authentication information. You can specify the authentication requirements in the Acoustic Exchange Integration Manager or through calls to Acoustic Exchange APIs. Acoustic Exchange adds the required authentication information in request headers so that it can communicate automatically with endpoint providers.
Acoustic Exchange also supports securing identity and attribute data through hashing. Acoustic Exchange supports industry standard hashing methods, to secure personal data that endpoints share through Acoustic Exchange.