New Name: Marketing Cloud Personalization
Interaction Studio (formerly Evergage) is now known as Marketing Cloud Personalization. The new name reflects our mission and vision for innovation in Salesforce Marketing Cloud. We wish we could snap our fingers to update the name everywhere, but you can expect to see the previous name in various places until we replace it.
Requirements and Schema
Data ingested via the External Email Campaign Events ETL gets stored in a third party campaign object and against the user profile. This data is subsequently available for segmentation and targeting purposes. The associated file format is detailed below.
For customers leveraging Interaction Studio’s multiple identities system, at least one identity attribute is required to be present in the ETL file. If you would like to send in multiple identity attributes for a single customer, this is supported by simply having multiple identity attribute columns in the file. Only unique identities can be included and updated through etl.
The correct ETL header format for identity attributes is attribute:value. Examples of the out-of-the box identity attributes with proper formatting is as follows:
userId is not referenced in ETL processing when the multiple identities system is enabled. For customers NOT leveraging Interaction Studio’s multiple identities system, userId will still be supported for profile merging.
File Name Format: externalEmailCampaign-YYYY-MM-DD_HH-MM-SS.csv
|Field Name||Minimum Requirements||Example Values||Max Length||Data Type|
userId OR an Identity Attribute
Required. The unique identifier for the external campaign.
|Any Valid Interaction Studio Data type|
Optional. The unique name for the campaign.
Required. The type of event. Currently supported values include send, click, open, unsubscribe.
Required. The date and time that the event occurred.
Required. Include the system that ran the campaign.
Salesforce Marketing Cloud
|source||Optional. The source of the campaign.||1023||String|
|medium||Optional. The medium the campaign.||1023||String|
Sample File Structure: Not Leveraging the IS Multiple Identity System
|jdoe||3823923||Send||Salesforce Marketing Cloud||2017-07-17T11:24:23Z|
Sample File Structure: Leveraging the IS Multiple Identity System
|email@example.com||123456||3823923||Send||Salesforce Marketing Cloud||2017-07-17T11:24:23Z|