Data Extension Insert
Step 1
- Find the
external keyof your taget DE (example) - Enter the desired DE
external keyinto the input field below - Click the
Valid Key?button so that the activity can confirm that your external key is valid - Once clicked, wait while the activity does validation
check. Once the activity, has completed it's checks:
- if it's valid, the input will turn green and you can proceed
- if it's invalid, the input will turn red and you can proceed
Step 2
- The below input field represents the DE field and value you
would like to be inserted into your target DE. From left to right, you will notice:
- a field removal button
- a dropdown of available fields in the DE
- an input field for the value you want in the DE
- Below the input fields you will also notice a "+ DE Field" button. Clicking the plus button will allows you to add an additional field to the configuration of the DE Insert activity
- Select your desired field and the value which they should contain (note you will not be able to add more fields than what is in the DE)
- Once you have fully configured the activity, click
finishto save your configuration in SFMC
NOTE: Data Binding Expressions (values surrounded by {{ and
}}) are case-sensitive
Journey Data is a snapshot of a contact's data from the Entry Event's DE at the time of entry into the Journey. This data never changes and persists with a contact for the duration of a contact's existence through a journey.
To use Journey Data choose the field that you want to use in the DE Insert
Use the below in your field value:
{{Event.xxx."xxx"}}
NOTE: Data Binding Expressions (values surrounded by {{ and }})
are case-sensitive
Contact Data is point-in-time data related to a particular Contact. This data is configured within Contact Builder's Data Designer feature.
Eg: A DE named Master_DE is linked in an Attribute Group called
"Master Attribute Group". In this DE, the desired field for DE Insert into another Data
Extension is named FavoriteColor.
To use Contact Data your field value for DE Insert should be configured as such:
{{Contact.Attribute.Master_DE.FavoriteColor}}
If multiple paths exist to the DE within Data Designer, the shortest path will be chosen. If multiple shortest paths exist, the SFMC will arbitrarily choose one. A contact must exist in all linked data extensions in order for the attribute to be successfully retrieved. To simplify this process, only use data extensions linked directly to ContactKey. If no contact key can be found, the activity will update the field value with an empty string.
Data Extension: xxx