Send customer profiles to Salesforce Sales Cloud

Note

This topic contains information about configuring a destination that sends query results to Salesforce Sales Cloud using orchestrations. To configure a destination that sends audiences to Salesforce Sales Cloud using campaigns see this topic .

Salesforce Sales Cloud brings customer information together into an integrated platform, and then provides access to thousands of applications through the AppExchange.

Note

This destination uses the Salesforce Sales Cloud SOAP API .

Get details

Review the following details before configuring credentials for Salesforce Sales Cloud and before configuring Amperity to send customer profiles to Salesforce Sales Cloud.

Credential settings Username and password Required The username and password of a Salesforce account configured for API access. Security token The Salesforce security token associated with the username. This setting is not required when IP range policies are configured from the Salesforce admin console.

Configure credentials

Configure credentials for Salesforce Sales Cloud before adding a destination.

An individual with access to Salesforce Sales Cloud should use SnapPass to securely share “username”, “password”, and “security token” details with the individual who will configure Amperity.

To configure credentials for Salesforce Sales Cloud

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Salesforce Sales Cloud. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential are determined by the credential type. For the “salesforce” credential type, configure settings, and then click Save. Username and password Required The username and password of a Salesforce account configured for API access. Security token The Salesforce security token associated with the username. This setting is not required when IP range policies are configured from the Salesforce admin console.

Add destination

Use a sandbox to configure a destination for Salesforce Sales Cloud. Before promoting your changes, send a test audience, and then verify the the results in Salesforce Sales Cloud. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Salesforce Sales Cloud

	Open the Destinations page, and then click the Add destination button. To configure a destination for Salesforce Sales Cloud, do one of the following: Click the row in which Salesforce Sales Cloud is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Salesforce Sales Cloud. Start typing “sales”. The list will filter to show only matching destinations. Select “Salesforce Sales Cloud”.
	Select the credential for Salesforce Sales Cloud from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Salesforce Sales Cloud.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
	Configure the following settings, and then click “Save”. Connect to sandbox instance? Optional. Select this option if the destination is a sandbox instance (and not a production instance). A sandbox instance is ignored when a custom URL for Salesforce Sales Cloud logins is used. Custom Salesforce login URL Optional. The custom URL for Salesforce Sales Cloud logins requires only the scheme (http:// or https://) and hostname parts of the URL. For example: http://<hostname> or https://<hostname>. The rest of the path is added automatically by Amperity. Salesforce object The name of the object in Salesforce Sales Cloud to which Amperity will send data. Operation The operation may be one of the following: “Insert”, “Upsert” (recommended), “Update”, or “Delete”. Upsert operations will insert a new record or update an existing record, whereas insert and update operations insert or update (but not both). External ID field The external ID should be set to “Amperity_ID__c”. (The “__c” identifies the field as a custom field in the Salesforce object.) Load data in parallel? When enabled, NULL values in data sent from Amperity will be ignored during “Upsert” operations. If a field from Amperity is NULL and there is a value in the corresponding Salesforce object, the value in the Salesforce object will be preserved. Enabling parallelism may cause Salesforce to process batches in parallel. This may improve performance, but comes with the risk of introducing failures due to locking. It is possible for more than one batch to attempt to obtain a lock on the same row, causing one (or both) batches to fail. Use NULL for empty fields? Enable to use NULL values when fields are empty.
	After this destination is configured, users may configure Amperity to use orchestrations to send query results Salesforce Sales Cloud.