Skip to content

Commit 7c8f33e

Browse files
pwsegpwseg
committed
Restore CSV Upload page and update sidenav
1 parent e577296 commit 7c8f33e

File tree

2 files changed

+135
-1
lines changed

2 files changed

+135
-1
lines changed

‎src/_data/sidenav/main.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -381,11 +381,13 @@ sections:
381381
title: Subscription Groups
382382
- path: /engage/user-subscriptions/subscription-sql
383383
title: Subscriptions with SQL Traits
384+
- path: /engage/user-subscriptions/csv-upload
385+
title: Update Audiences with a CSV
384386
- section_title: Profiles
385387
description: "See how to create audiences based on data."
386388
section:
387389
- path: '/engage/profiles/csv-upload'
388-
title: CSV Uploader
390+
title: Use Profiles and Traits with a CSV file
389391
- section_title: Audiences
390392
description: "See how to create audiences based on data."
391393
section:

‎src/engage/user-subscriptions/csv-upload.md

Lines changed: 132 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,132 @@
1+
---
2+
title: Update Audiences with a CSV
3+
plan: engage-premier
4+
---
5+
Use the CSV Uploader to add or update user profiles and set subscription states.
6+
7+
When you upload a CSV file, Engage adds new profiles and updates existing user profiles. Each CSV row corresponds to a user profile and columns to an identifier in your [identity resolution configuration](/docs/unify/identity-resolution/identity-resolution-settings/).
8+
9+
You can also [set subscription states](#set-user-subscriptions) for each email and phone number that you upload in the CSV. Subscription states help you track which email addresses and numbers you have permission to market to.
10+
11+
> warning ""
12+
> Uploading a CSV creates new profiles and updates existing profiles. These profile updates may lead to users entering existing audiences or message campaigns.
13+
14+
> info ""
15+
> Using the CSV Uploader to upload user profiles to Engage will **not** increase your MTUs count. [Learn more](/docs/guides/usage-and-billing/mtus-and-throughput/#mtus-and-engage) about MTUs and Engage.
16+
17+
18+
## Upload a CSV file
19+
20+
Use the **Upload CSV** page to upload a CSV file in your Segment space:
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**.
24+
25+
### 1. Download your CSV template
26+
27+
Click **Download Template** to download a CSV template with identifier columns from your identity resolution configuration. Engage adds subscription columns next to email and SMS identifiers, where you can update subscription states for email addresses and phone numbers.
28+
29+
> info ""
30+
> CSV files can only have a single **email** and **phone** identifier column. Include any additional email addresses or phone numbers for a user profile as a separate row.
31+
32+
Navigate to **Unify > Unify settings** and select the **Identity resolution** tab to view or add identifiers in your Segment workspace.
33+
34+
### 2. Fill out your CSV file
35+
36+
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+
A few best practices to keep in mind as you fill out your CSV:
39+
40+
- Leave any unknown values blank to avoid bad data. Engage can create a user profile from a single identifier in your CSV.
41+
- 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 `+##########`.
42+
43+
44+
### 3. Upload your CSV file
45+
46+
Upload a CSV file to Twilio Engage in two ways:
47+
- Drag and drop the CSV file in the dropzone.
48+
- Click **Browse** to locate the CSV file.
49+
50+
Engage processes CSV rows sequentially. Column values, except for a blank subscription status, override previous values for a user profile.
51+
52+
A blank subscription status in the CSV doesn't overwrite current **email** or **phone** [subscription states](/docs/engage/user-subscriptions/subscription-states/) in your Segment space.
53+
54+
### 4. Name your custom trait
55+
56+
Every time you upload a file, you have the option to add a custom trait to user profiles in the CSV. Use custom traits to help you [create audiences](/docs/engage/audiences/#building-an-audience) or send messages to a specific group of users. You can also add an existing custom trait name from your Segment workspace to the list of users in the CSV file.
57+
58+
[Custom traits](/docs/unify/traits/custom-traits/) display in the Custom Traits tab of a user profile in the Profile explorer.
59+
60+
## View Update History
61+
62+
Use the Update History page to view CSV file uploads in your workspace over the last 30 days.
63+
64+
To view the Update History page:
65+
66+
1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**.
67+
2. Click **Manage subscription statuses**.
68+
3. Select **View update history**.
69+
70+
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+
72+
### Error reports
73+
74+
Use error reports to fix invalid rows and quickly re-upload data.
75+
76+
From the Update History page:
77+
78+
1. Select the link in the **Report** column to download an error report CSV. All rows not present in the error report were processed successfully.
79+
2. Correct data in the invalid rows.
80+
3. Remove any extra columns such as `row_number`, `error_message`, and `error_code`.
81+
3. Click **Update subscription statuses**, and select **Upload a CSV** to re-upload the file.
82+
83+
Engage uses the following error codes on the report:
84+
85+
|Error code | Description |
86+
|----------------------------------|-----------------------------------------------------|
87+
|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. |
93+
94+
95+
## Set user subscriptions
96+
97+
Use the CSV Uploader to set subscription states for user email addresses and phone numbers.
98+
99+
> info ""
100+
> Each user profile in a Segment workspace can have multiple email addresses and phone numbers, all with different subscription states.
101+
102+
For each CSV file, Engage adds:
103+
- An `email_subscription_status` column next to the **Email** column.
104+
- `whatsapp_subscription_status` and `sms_subscription_status` columns next to the **Phone** column.
105+
106+
In the `email_subscription_status`, `sms_subscription_status`, and `whatsapp_subscription_status` columns, set subscription states for email and phone numbers with the following values:
107+
108+
- `subscribed`: The user has actively subscribed.
109+
- `unsubscribed`: The user has actively unsubscribed.
110+
- `did-not-subscribe`: The user has provided their contact information but didn't actively subscribe or unsubscribe.
111+
- **No subscription status (blank value)**: The user's profile exists in Segment, but they haven't explicitly provided their contact information, and no subscription information is available.
112+
113+
Engage accepts both uppercase and lowercase subscription status values.
114+
115+
> success ""
116+
> Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
117+
118+
## CSV upload limits
119+
120+
Please note the following limits as you upload CSV files to Twilio Engage:
121+
- You can only upload .csv files.
122+
- Files can't be empty and must have at least one header and one row.
123+
- You can't have multiple columns with the same header.
124+
- CSV files can't contain extraneous column headers.
125+
- Upload CSV files with up to 1 million rows (plus one header row).
126+
- You can only upload one file at a time.
127+
- The CSV file size can't exceed 15 MB.
128+
- 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+
130+
## Message consent
131+
132+
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

Comments
 (0)