Send data to Salesforce Sales Cloud

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 .

This topic describes the steps that are required to send customer data to Salesforce Sales Cloud from Amperity:

1. Get details

2. Add destination

3. Add data template

Get details

The Salesforce Sales Cloud destination requires the following configuration details:

1. The Salesforce Sales Cloud username.

2. The Salesforce Sales Cloud password.

3. The Salesforce Sales Cloud security token that belongs to username. (The security token is not required if IP range policies are configured from the Salesforce admin console.)

4. The scheme and host for a custom Salesforce Sales Cloud URL, if used by customer.

5. If Amperity will send data to a sandbox instance.

How do I find Salesforce Sales Cloud account information?

You can find all of this information by logging into your Salesforce Sales Cloud admin console and by viewing the URL for your instance of Salesforce Sales Cloud.

Build query

You will need to build a query that outputs fields that can be mapped to Salesforce Sales Cloud.

Add destination

Salesforce Sales Cloud is a destination that may be configured directly from Amperity.

To add a destination

1. From the Destinations tab, click Add Destination. This opens the Add Destination dialog box.

2. Enter the name of the destination and a description. For example: “Salesforce Sales Cloud” and “This sends query results to Salesforce Sales Cloud”.

3. From the Plugin drop-down, select Salesforce Sales Cloud.

4. The “salesforce” credential type is selected automatically.

5. From the Credential drop-down, select Create a new credential. This opens the Create New Credential dialog box.

6. Enter a name for the credential and the username, password, and the security token that is associated with username. (The security token is not required if IP range policies are configured from the Salesforce admin console.) Click Save.

7. Under Salesforce Sales Cloud Settings, indicate if the destination is a sandbox instance, enter the custom URL for Salesforce logins (if used), and enter the name of the object in Salesforce to which Amperity will send data.

   The custom URL for Salesforce logins requires only the scheme (http:// or https://) and hostname parts of the URL. For example: https://<hostname> or http://<hostname>. The rest of the path is added automatically by Amperity.

   Note

   A sandbox instance is ignored when a custom URL for Salesforce logins is used.

8. Select Allow customers to use this data template.

9. Select Allow orchestrations from users with limited PII access.

10. Click Save.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

To add a data template

1. From the Destinations tab, open the menu for a Salesforce Sales Cloud destination, and then select Add data template. This opens the Add Data Template dialog box.

2. Enter the name of the data template and a description. For example: “Salesforce Sales Cloud” and “This template maps to an object in Salesforce Sales Cloud.”

3. Under Template Settings, indicate if the destination is a sandbox instance, enter the custom URL for Salesforce logins (if used), the name of the object in Salesforce to which Amperity will send data, the type of operation to perform, the external ID field (which acts as the primary key in the Salesforce object and is used by Amperity to identify which objects require updates for “Upsert” operations), if data should be loaded in parallel, and if NULL values should be used when fields are empty.

   The custom URL for Salesforce logins requires only the scheme (http:// or https://) and hostname parts of the URL. For example: “https://<hostname>” or “http://<hostname>”. The rest of the path is added automatically by Amperity.

   Note

   A sandbox instance is ignored when a custom URL for Salesforce logins is used.

   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 (and not both).

   The external ID should be set to Amperity_ID__c. (The __c identifies the field as a custom field in the Salesforce object.)

   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.

   Caution

   Enabling parallelism may cause Salesforce to process batches in parallel. This may improve performance, but comes with the risk of introduce failures due to locking. It’s possible for more than one batch to attempt to obtain a lock on the same row, causing one (or both) batches to fail.

4. Click Save.