Synchronize data extensions
Overview
In this destination service, DinMo will synchronise your data with an existing data extension or create a new one if it does not exist.
To create such an activation, you will need to go through these three steps:
If your data extension does not already exist,
Click on Create a new data extension on the destination creation page.
Enter the following information:
The Data Extension name
The Data folder used by your data extension
The field used as primary key and its type
If your data extension already exists:
Create a Salesforce Marketing Cloud destination targeting this data extension. Refer to the corresponding section for more info.
Create a segment or a model composed of all the rows that will populate the Salesforce data extension. The data extension's primary key must be one of the model's fields.
Activate the model or segment to the Salesforce destination to start sending data. Refer to the corresponding section for more info.
Each time the activation will be running:
If you ticked the insert mode option, all new records in the model will be inserted in the data extension
All attributes values that have changed since the last activation will be updated in the data extension
If you chose not to insert new records, only records of the model with a primary key already present in the data extension will be updated.
Destination setup
To start synchronizing objects, you are first required to create a Salesforce Marketing Cloud destination with the corresponding destination service.
In this process, you must specify:
How data will be transferred:
Either using an FTP user. In this case, you must indicate the file transfer location (by default,
ExactTarget Enhanced FTP)Either through Amazon S3. In this case, you must again indicate the file transfer location.
Which existing data extension will be updated in this destination. If you wish to update different data extensions, please create one distinct destination for each of these objects
Configuring Amazon S3 Access
Amazon S3 Access requires you to input an AWS role ARN to give DinMo write access to your S3 bucket at the file transfer location.
In order to do so, you must add this role arn to the role's trust policy : arn:aws:iam::724998534403:role/DinmoS3AccessorRole-dinmo-prod
Here is an example of a trust policy with that role :
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::724998534403:role/DinmoS3AccessorRole-dinmo-prod"
},
"Action": "sts:AssumeRole"
}
]
}Here is a minimal policy granting s3 access to a role
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket"
],
"Resource": "arn:aws:s3:::example-bucket"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::example-bucket/*"
}
]
}
Important note: The data extension must have a primary key configured on Salesforce's side.
Activation configuration
Once the destination has been setup, and your DinMo model (or segment) created, you can create an activation to start sending data to Salesforce right away.
Activation core parameters
Within the core parameters, you have a number of options to consider when sending data to your Salesforce data extension. These are:
Insert data extension records - when toggled on, any new object in the segment or model you have chosen in DinMo will be inserted during the data extension sync as well as updating all other mapped attributes.
Clear data extension records - when toggled on, this will clear all objects within a data extension on only the first sync, before syncing all objects as new objects in the model or segment, and then maintaining these objects and their mapped attributes in the data extension thereafter.
Clear data extension records at every run - when toggled on, this will clear all objects within a data extension before every sync, which enables you to sync only the deltas of each run with the data extension i.e. any new objects created since the last run will be inserted into the data extension.
Mirror the segment and the data extension - when toggled on, this mode allows you to overwrite the entire data extension with your model or segment results during every synchronisation. Mirror cannot insert new objects, so to mirror a segment or model which may contain new objects, you should also toggle insert mode.
When Clear Mode is enabled, DinMo prompts you to run a full historical sync to repopulate the whole segment and not just the delta objects since the last run. We recommend proceeding with this.
Fields mapping
In the Fields mapping section, you are asked to specify the field contained in your DinMo model corresponding to the primary key of the target data extension. This field will be used to link the model's records to existing records in Salesforce.
You can then map any other attribute existing in Salesforce. These attributes will then be updated by DinMo during each activation.
Custom Attributes
In this section, any field you select will be automatically created and exported as a new column in your Salesforce data extension. The associated field will have the same name in Salesforce and DinMo.
The values of the attributes selected here will then also be updated at each activation.
Last updated