To access Acoustic Exchange, you need to be a license user of a commerce solution or a commerce partner solution. In case you are the user of any of these solutions but do not have an Acoustic Exchange account, you can request one through Acoustic Support.
Enable account access for Acoustic Exchange
To enable Acoustic Exchange access to Acoustic Campaign, you need to establish application access for Acoustic Exchange. As a result, Acoustic Campaign becomes the Acoustic Exchange endpoint.
- Log in to Acoustic Campaign as an organization admin user, then go to Settings > Organization settings > Application account settings.
- Click Add account access.
- Select Acoustic Exchange from the Application drop-down menu.
- Select the Primary user account from the User account drop-down menu.
- Enter a description (optional).
- Click Add when done.
The primary account user will receive a refresh token in an email. You will need this fresh token to register Acoustic Campaign as an Acoustic Exchange endpoint.
After you are granted application access to Acoustic Exchange, register Acoustic Campaign as an endpoint in Acoustic Exchange.
Create a flexible database in Campaign
To receive data from Acoustic Exchange, you must create a flexible database in Acoustic Campaign that can accept the data.
Changes to the Lookup keys in databases
Any changes that are made to the Lookup key and/or the database schema in the Acoustic Campaign database, automatically reflects in the Acoustic Campaign endpoint.
For example, if you add or remove a lookup key in the database, then the same changes show up in identifiers in the endpoint. Also, if you add or remove a field in the database, then the same changes reflect the attributes in the endpoint.
Changing the database used by the Exchange endpoint
Business requirements can arise that make it necessary for you to set or change the marketing database that is associated with your Acoustic Campaign endpoint in Exchange.
As an organization administrator, you can change the marketing database used by Exchange. Note that only a shared database can be reassigned, as private databases are not meant for distribution.
Note: Assigning a different database to Exchange causes errors in existing inbound Universal Behavior mappings. You must contact support to update your existing inbound Universal Behavior mappings.
To reassign a database that is used by Exchange, use the following procedure.
- From the dashboard, navigate to Org settings > Integrations > Edit.
- Click Select.
- Choose a database to assign to Exchange from the list of available databases and click Select.
- Confirm that the selected database is the one that you want registered with Exchange and select OK.
- Select Save to finalize the change.
After the database is changed, navigate to the Audiences tab in Exchange and verify that scheduled audience shares are mapped to the new database.