Skip to content

Commit b534c4d

Browse files
authored
Merge pull request #3061 from segmentio/csv-uploader-edits
CSV Uploader Update
2 parents 24c7a44 + 2bcb9cb commit b534c4d

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

src/engage/profiles/csv-upload.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,8 @@ Use the CSV Uploader to set subscription states for user email addresses and pho
7272
> Each user profile in a Segment workspace can have multiple email addresses and phone numbers, all with different subscription states.
7373
7474
For each CSV file, Engage adds:
75-
- An `email_subscription_status` column next to **Email** columns.
76-
- An `sms_subscription_status` column next to **SMS** columns.
75+
- An `email_subscription_status` column next to the **Email** column.
76+
- An `sms_subscription_status` column next to the **Phone** column.
7777

7878
In the `email_subscription_status` and `sms_subscription_status` columns, set subscription states for email and phone numbers with the following values:
7979

@@ -95,11 +95,7 @@ Please note the following limits as you upload CSV files to Twilio Engage:
9595
- Upload CSV files with up to 1 million rows (plus one header row).
9696
- You can only upload one file at a time.
9797
- The CSV file size can't exceed 15 MB.
98-
99-
> warning ""
100-
> At this time, the following beta limitations apply:
101-
> - Email addresses and phone numbers that unsubscribe from your campaigns can't be re-subscribed.
102-
> - If you upload the same email or phone number with different subscription states in a CSV file, the resulting subscription status isn't guaranteed.
98+
- If you upload the same email or phone number with different subscription states in a CSV file, Engage doesn't guarantee the subscription status result.
10399

104100
## Message consent
105101

0 commit comments

Comments
 (0)