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:
Get details¶
Salesforce Sales Cloud requires the following configuration details:
|
The username and password. |
|
|
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.) |
|
|
The scheme and host for a custom Salesforce Sales Cloud URL, if used by customer. |
|
|
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¶
Configure Amperity to send customer data directly to Salesforce Sales Cloud.
To add a destination
|
Open the Destinations tab to configure a destination for Salesforce Sales Cloud. Click the Add Destination button to open the Destination dialog box. 
Enter a name for the destination and provide a description. For example: “Salesforce Sales Cloud” and “This sends customer data to Salesforce Sales Cloud”. From the Plugin drop-down, start typing “sales” to filter the list, and then select Salesforce Sales Cloud. |
||||||||
|
Credentials allow Amperity to connect to Salesforce Sales Cloud. The credential type is set automatically. You may use an existing credential or you may add a new one. 
Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. 
Enter the name for the credential, and then add a description. Salesforce Sales Cloud has the following settings:
When finished, click Save. |
||||||||
|
Each destination has settings that define how Amperity will deliver data to Salesforce Sales Cloud. These settings are listed under the Settings section of the Destination dialog box. 
The following settings are specific to Salesforce Sales Cloud:
|
||||||||
|
Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? 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. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: 
|
||||||||
|
Review all settings, and then click Save. 
Important You must configure a data template for this destination before you can send data to Salesforce Sales Cloud. |
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
|
|
From the Destinations tab, open the menu for a destination that is configured for Salesforce Sales Cloud, and then select Add data template. This opens the Add Data Template dialog box. 
Enter the name of the data template and a description. For example: “Salesforce Sales Cloud” and “Send customer data to Salesforce Sales Cloud.”. |
|
|
Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. 
If business user access was not configured as part of the destination, you may configure access from the data template. |
|
|
Verify all configuration settings. 
Note When the settings required by Salesforce Sales Cloud were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns. |
|
|
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 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.. |
|
|
Review all settings, and then click Save.
|