Please take a few moments to review the following requirements and best practices before you begin the integration configuration between Salesforce and Acoustic Campaign.

Supported configuration

The supported configuration is one Salesforce organization to one flexible contact database.

Note: Do not use an existing pre-populated contact database. Start with a new flexible contact database which allows the integration to create the initial population of contacts or significant duplication error might occur. See Use an existing flexible database for CRMi for more information.

Salesforce sandbox support

You can connect your Acoustic Campaign organization to EITHER a production or sandbox Salesforce org. This selection cannot be reversed. Do not connect your production Acoustic Campaign organization to a Salesforce sandbox. Please request a second Acoustic Campaign organization in the event you need to configure the integration with a Salesforce sandbox.

Backups

Export Salesforce prior to activating your integration. Consult with your Salesforce administrator for procedures.

Salesforce Integration Use

A Salesforce username, password, and security token are needed to access the Salesforce API. A dedicated Salesforce integration user is ideal but not required.

Note: If Security Tokens are disabled in your Salesforce organization, you can whitelist the Acoustic Campaign integration server before the integration can access the Salesforce APIs. See Are there any Salesforce IP restrictions for more information.

This Salesforce integration user must have Marketing User checked in User Details and API Enabled on their Profile.

Person Accounts

Person accounts require an additional package installation and configuration. See Managing Salesforce person accounts for more information.