Skip to content

Commit 84147fd

Browse files
pwsegpwseg
committed
Update CSV upload tables
1 parent 34aa6b2 commit 84147fd

File tree

1 file changed

+33
-13
lines changed

1 file changed

+33
-13
lines changed

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

Lines changed: 33 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,11 @@ Use the Update History page to view CSV file uploads in your workspace over the
6363

6464
To view the Update History page:
6565

66-
1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**.
67-
2. Click **Manage subscription statuses**.
68-
3. Select **View update history**.
66+
1. Navigate to **Unify > Profile explorer** or **Engage > Engage settings > Subscriptions**.
67+
2. From the **Subscription groups** table, click the three dots icon, then click **View update history**.
68+
3. From the **Upload history** table, click the file name link to download the [error reports](#error-reports).
6969

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.
70+
View the status of the file upload and the custom trait name added to user profiles in the CSV upload. The error report only shows rows that Segment couldn't successfully process.
7171

7272
### Error reports
7373

@@ -82,14 +82,31 @@ From the Update History page:
8282

8383
Engage uses the following error codes on the report:
8484

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. |
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+
| GLOBAL_STATE_NOT_SUBSCRIBED | Global state isn't subscribed or set, so Segment can't update subscription states. |
94+
95+
96+
### Validation errors
97+
98+
The following table lists validation errors you may run into with your CSV upload:
99+
100+
| Error | Error Message |
101+
| ------------------------------------ | -------------------------------------------------------------------------------------------------- |
102+
| Invalid file types | You can upload only .csv files. Change your file format, then try again. |
103+
| Empty files | This file contains no data. Add data to your CSV, then try again. |
104+
| CSV parsing error | We encountered an issue while parsing your CSV file. Validate the CSV file and try again. |
105+
| Unexpected/fallback | Something went wrong. Try again later. |
106+
| Empty header row | This file contains empty header(s). Remove the empty header(s), then try again. |
107+
| File exceeds one million rows | Too many rows. You can upload up to 1000000 rows. |
108+
| File exceeds 100 MB | Files can be up to 100 MB. |
109+
| Extraneous columns/column name typos | This file has columns that do not match the identifiers in your identity resolution configuration. |
93110

94111

95112
## Set user subscriptions
@@ -115,7 +132,7 @@ Engage accepts both uppercase and lowercase subscription status values.
115132
> success ""
116133
> Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
117134
118-
## CSV upload limits
135+
## Subscription group CSV upload limits
119136

120137
Please note the following limits as you upload CSV files to Twilio Engage:
121138
- You can only upload .csv files.
@@ -125,6 +142,9 @@ Please note the following limits as you upload CSV files to Twilio Engage:
125142
- You can only upload one file at a time.
126143
- The CSV file size can't exceed 100 MB.
127144
- 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.
145+
- The `phone` and `email` identifiers must be valid phone numbers and email addresses, otherwise they'll process as errors.
146+
- The subscription group CSV upload only honors group subscriptions, so `sms_subscription_status`, `whatsapp_subscription_status`, and `email_subscription_status` aren't allowed.
147+
- Other than `[group_name]_subscription_status`, you should set up all columns in your identity resolution configuration.
128148

129149
## Message consent
130150

0 commit comments

Comments
 (0)