Salesforce Marketing Cloud - Data Extension Upsert Row
Salesforce is a cloud-based software company providing customer relationship management (CRM) software and applications focused on sales, customer service, marketing automation, analytics, and application development. Using this destination and your segments you can create or update (upsert) a row in a data extension using Salesforce Marketing Cloud Engagement synchronous REST API upsertRowsetByKey and enable a multitude of data activation flows like the abandoned cart.
Key features
The Salesforce Marketing Cloud - Data Extension Upsert Row destination provides the following key features:
Data activation: upserting data extensions can be used to enable various data activation flows based on the user behaviour.
Support batch mode: you can freely activate batch mode in Configuration. See section Batch mode for more details.
Easy setup: select your data variables, in segments, from a drop-down menu.
Destination setup
Configuration
Credentials
Required
Your credentials with Salesforce Marketing Cloud as set directly in your destination or, in the left menu, following: Administration ➜ Connector Credentials ➜ Add connector credentials ➜ Salesforce Marketinng .
Data Extension Id
Required
The unique identifier for the data extension.
Primary Key Mapping
Required
Select the Data variable holding the primary key value to be looked up to find the record to update/insert and input the Salesforce column representing the primary key column name. One entry is required.
Record Field Mapping
Required
Select the Data variable holding the value to update/insert and input the Salesforce column representing the related field name. One entry is required.
Activate batch mode
When checked, multiple records are sent to your data extension with a single request instead of one at a time. See section Batch mode for more details.
Field mappings
Created data extension records include the following properties:
Salesforce column [1]
Data variable [1]
Batch mode
Having batch mode activated has its benefits and drawbacks. See the following table for more details:
Not checked
• Real-time requests. • Better error management.
• More susceptible to Salesforce API limits.
Checked
• Less susceptible to Salesforce API limits.
• Slightly postponed requests. • On error, all records in a single request are discarded. [1]
Salesforce API limits
Salesforce protects their services by placing limits on API usage, resulting in the following soft limits for this destination:
Maximum API request volume. The limit depends on your edition:
Pro: 2 million requests per year.
Corporate: 6 million requests per year.
Enterprise: 200 million requests per year.
Maximum request rate for synchronous API requests: 2500 requests per minute across all endpoints.
Maximum number of concurrent connections: 100 connections.
Maximum batch size for synchronous API requests: 50 objects.
Last updated
Was this helpful?