You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/engage/profiles/csv-upload.md
+61-18Lines changed: 61 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Update Audiences with a CSV
2
+
title: Use Profiles and Traits with a CSV file
3
3
plan: engage-premier
4
4
---
5
5
Use the CSV Uploader to add or update user profiles and set subscription states.
@@ -19,8 +19,9 @@ You can also [set subscription states](#set-user-subscriptions) for each email a
19
19
20
20
Use the **Upload CSV** page to upload a CSV file in your Segment space:
21
21
1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**.
22
-
2. Click **Manage subscription statuses**, then select **Update subscription statuses**.
23
-
3. Select **Upload a CSV**, then click **Configure**.
22
+
2. Click **+Add Profiles**.
23
+
3. Download and fill out the CSV template.
24
+
4. Upload your CSV file.
24
25
25
26
### 1. Download your CSV template
26
27
@@ -35,10 +36,14 @@ Navigate to **Unify > Unify settings** and select the **Identity resolution** ta
35
36
36
37
Enter values for the identifiers in your CSV file. You can also [set email, phone, and WhatsApp subscriptions](#set-user-subscriptions) using the `email_subscription_status`, `sms_subscription_status`, and `whatsapp_subscription_status` columns.
37
38
38
-
A few best practices to keep in mind as you fill out your CSV:
39
+
A few guidelines to keep in mind as you fill out your CSV:
39
40
40
41
- Leave any unknown values blank to avoid bad data. Engage can create a user profile from a single identifier in your CSV.
41
42
- Enter phone numbers in your CSV in a format that's consistent with your Segment space. For example, if existing profiles in your workspace are in E.164 format `+15555550123`, enter numbers in your CSV using the same format `+##########`.
43
+
- The template won't include duplicate custom traits, traits with trailing, leading, or multiple consecutive spaces between characters, or [unallowed characters](#allowed-csv-file-characters).
44
+
- Custom traits column headers are case-sensitive. For example, `first Name`, `FIRST Name`, and `First Name` would all be different traits in the template.
45
+
- Trailing, leading, or multiple consecutive spaces between characters are not allowed.
46
+
- Make sure you've added an identifier column or `anonymous_id` in your identity resolution configuration.
42
47
43
48
44
49
### 3. Upload your CSV file
@@ -57,18 +62,36 @@ Every time you upload a file, you have the option to add a custom trait to user
57
62
58
63
[Custom traits](/docs/unify/traits/custom-traits/) display in the Custom Traits tab of a user profile in the Profile explorer.
59
64
65
+
## Work with the CSV template
66
+
67
+
Keep the following in mind as you fill out your CSV template.
68
+
69
+
### Allowed CSV file characters
70
+
71
+
You can use these characters in your CSV file:
72
+
73
+
- Alphabetic English characters in both upper and lower case
74
+
- The numerals 0-9
75
+
- These special characters: ```!@#$%^&*()_+-=[]{}:\\|.`~<>\/?```
Use the Update History page to view CSV file uploads in your workspace over the last 30 days.
63
86
64
87
To view the Update History page:
65
88
66
89
1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**.
67
-
2. Click **Manage subscription statuses**.
68
-
3. Select **View update history**.
90
+
2. Click **View update history**.
69
91
70
92
Select links to view CSV files and any associated [error reports](#error-reports). View the status of the file upload and the custom trait name added to user profiles in the CSV upload.
71
93
94
+
72
95
### Error reports
73
96
74
97
Use error reports to fix invalid rows and quickly re-upload data.
@@ -82,14 +105,33 @@ From the Update History page:
82
105
83
106
Engage uses the following error codes on the report:
|INVALID_EMAIL | The email address isn't formatted correctly. |
88
-
|INVALID_PHONE | The phone number is invalid. |
89
-
|INVALID_SUBSCRIPTION_STATUS | The subscription status is invalid. Check the status or leave it blank. |
90
-
|CONFIGURATION_ERROR | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help. |
91
-
|SYSTEM_ERROR | Something went wrong. Please try again. |
92
-
|UNABLE_TO_SUBSCRIBE | You can't update the subscription status for this phone number because the user unsubscribed by replying `STOP`. The user must reply `START` to resubscribe. |
| INVALID_EMAIL | The email address isn't formatted correctly. |
111
+
| INVALID_PHONE | The phone number is invalid. |
112
+
| INVALID_SUBSCRIPTION_STATUS | The subscription status is invalid. Check the status or leave it blank. |
113
+
| CONFIGURATION_ERROR | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help. |
114
+
| SYSTEM_ERROR | Something went wrong. Please try again. |
115
+
| UNABLE_TO_SUBSCRIBE | You can't update the subscription status for this phone number because the user unsubscribed by replying `STOP`. The user must reply `START` to resubscribe. |
116
+
117
+
You may also encounter the following validation errors:
| Invalid file types | You can upload only .csv files. Change your file format, then try again. |
122
+
| Empty files | This file contains no data. Add data to your CSV, then try again. |
123
+
| CSV parsing error | We encountered an issue while parsing your CSV file. Validate the CSV file and try again. |
124
+
| Unexpected/fallback | Something went wrong. Try again later. |
125
+
| Empty header row | This file contains empty header(s). Remove the empty header(s), then try again. |
126
+
| File exceeds one million rows | Too many rows. You can upload up to 1000000 rows. |
127
+
| File exceeds 1000 columns | Your CSV file is exceeding the limit of 1000 columns. |
128
+
| File exceeds 100 MB | Files can be up to 100 MB. |
129
+
| File contains a header with unallowed spaces | This file contains leading, trailing or consecutive spaces. Remove leading, trailing or consecutive spaces, then try again. |
130
+
| File contains duplicate headers | This file contains duplicate header(s). Remove duplicate header(s), then try again. |
131
+
| File contains invalid characters | This file contains invalid character(s). Remove invalid character(s), then try again. |
132
+
| Unconfigured `anonymous_id` or missing Identifier column | This file is missing an identifier column and does not have `anonymous_id` configured. Add an identifier column or add `anonymous_id` in your identity resolution configuration, then try again. |
133
+
134
+
93
135
94
136
95
137
## Set user subscriptions
@@ -115,18 +157,19 @@ Engage accepts both uppercase and lowercase subscription status values.
115
157
> success ""
116
158
> Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
117
159
118
-
## CSV upload limits
160
+
## CSV upload guidelines
119
161
120
162
Please note the following limits as you upload CSV files to Twilio Engage:
121
-
- You can only upload .csv files.
163
+
- You can only upload `.csv` files.
122
164
- Files can't be empty and must have at least one header and one row.
123
165
- You can't have multiple columns with the same header.
-Upload CSV files with up to 1 million rows (plus one header row).
167
+
- CSV files cannot exceed 1 million rows (plus one header row), 1000 columns, or 100 MB in file size.
126
168
- You can only upload one file at a time.
127
-
- The CSV file size can't exceed 15 MB.
128
169
- If you upload the same email or phone number with different subscription states in a single CSV file, Engage doesn't guarantee the subscription status result.
129
170
171
+
- Add an identifier column or `anonymous_id` in your identity resolution configuration.
172
+
130
173
## Message consent
131
174
132
175
Segment recommends sending to subscribed users. If a recipient deletes or flags an unwanted message as spam, inbox providers might start to filter your messages straight to spam folders. View more SendGrid delivery [Best Practices](https://sendgrid.com/blog/why-are-my-emails-going-to-spam/){:target="_blank"} to prevent email from going to spam.
0 commit comments