You are here:
User ETL Data Feed
Use the User ETL data feed to update Unified Custom Profiles, and Unified Account Profiles if you have B2B Detect. Personalization stores user profiles for each anonymous and known user in the system.
About Ingesting User Data
User ETL data feeds are unique in that Personalization often receives user data from multiple sources that are all canonical. For this reason, a blank value in the User ETL file doesn’t impact the existing value like it does in other ETL files.
The User ETL data feed also supports updating any user profile attributes you’ve created.
Requirements
- ETL files must be in a CSV file format that adheres to the schema for the data feed. Files that don’t follow the file naming conventions or the appropriate schema result in errors and fail to process.
- Field names that begin with
attribute:must match the custom attribute names on the User Attributes tab of the Settings > Attributes page.
Filename Format
user-YYYY-MM-DD_HH-MM-SS.csv
Schema
| Field Name | Description | Example Values | Maximum Length | Data Type |
|---|---|---|---|---|
|
Required. Only unique identities can be included and updated through an ETL feed. This field has a four-character minimum requirement. If you aren’t using Personalization's multiple identities system, a user ID must be included. This ID must be one that is tracked within the system so that the events can be tied to the specific user profile. If you're using Personalization's multiple identities system, The correct header format for identity attributes is |
jdoe john.doe@example.com C2e384084c8ac233 attribute:emailAddress attribute:sfmcContactKey attribute:customerId attribute:sfcrmContactId attribute:sfcrmLeadId |
120 |
String |
attribute:
|
The custom attributes for the user. Column headers begin with |
attribute:isLoggedIn true attribute:userLevel 5 |
1024 |
Any valid data type |
attribute:name
|
The display name for the user. |
Santa Claus Easter Bunny |
120 |
String |
attribute:accountId
|
Represents the unique identifier for an account, and its value must match an account ID in the system. Account IDs must be all lowercase with no spaces. Note: This field is available only if you have B2B Detect enabled. |
salesforce 6413150145 |
120 |
String |
Sample File Structure: Not using the multiple identities system
| userId | attribute:name | attribute:emailAddress | attribute:accountId | attribute:isLoggedIn | attribute:visitNumber | attribute:firstVisitDate |
jdoe |
John Doe |
johndoe@example.com |
TRUE |
40 |
2017-07-17 |
|
tester@test.com |
Tester |
tester@test.com |
testaccount |
TRUE |
15 |
2009-10-19T08:42:58Z |
user103925 |
FALSE |
1 |
2020-07-07 |
|||
a30bkcqfo941afc |
Jane Smith |
example@example.com |
example |
TRUE |
3 |
2020-04-01 |
personalizationuser |
Personalization User |
testing@test.com |
personalization |
TRUE |
6130 |
2010-01-01 |
Sample File Structure: Using the multiple identities system
| attribute:emailAddress | attribute:customerId | attribute:name | attribute:accountId | attribute:isLoggedIn | attribute:visitNumber | attribute:firstVisitDate |
johndoe@example.com |
3910vi2msp38g4 |
John Doe |
TRUE |
40 |
2017-07-17 |
|
tester@test.com |
8491505268e12f |
Tester |
testaccount |
TRUE |
15 |
2009-10-19T08:42:58Z |
8f138t9fd128d1v |
FALSE |
1 |
2020-07-07 |
|||
example@example.com |
19218sdfee31sav |
Jane Smith |
example |
TRUE |
3 |
2020-04-01 |
testing@test.com |
9851ar4vbt450em |
Personalization User |
personalization |
TRUE |
6130 |
2010-01-01 |
