Merge pull request #6153 from segmentio/csv-upload-updates

Subscription Group CSV Upload updates
segmentio · Feb 29, 2024 · aba34c4 · aba34c4
2 parents a90b818 + 7b71359
commit aba34c4
Show file tree

Hide file tree

Showing 2 changed files with 34 additions and 14 deletions.
diff --git a/src/engage/user-subscriptions/csv-upload.md b/src/engage/user-subscriptions/csv-upload.md
@@ -63,11 +63,11 @@ Use the Update History page to view CSV file uploads in your workspace over the
 
 To view the Update History page:
 
-1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**.
-2. Click **Manage subscription statuses**.
-3. Select **View update history**.
+1. Navigate to **Unify > Profile explorer** or **Engage > Engage settings > Subscriptions**.
+2. From the **Subscription groups** table, click the three dots icon, then click **View update history**.
+3. From the **Upload history** table, click the file name link to download the [error reports](#error-reports).
 
-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.
+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.  
 
 ### Error reports
 
@@ -82,14 +82,31 @@ From the Update History page:
 
 Engage uses the following error codes on the report:
 
-|Error code                        | Description                                         |
-|----------------------------------|-----------------------------------------------------|
-|INVALID_EMAIL                 | The email address isn't formatted correctly.        |
-|INVALID_PHONE                 | The phone number is invalid.                        |
-|INVALID_SUBSCRIPTION_STATUS   | The subscription status is invalid. Check the status or leave it blank.   |
-|CONFIGURATION_ERROR          | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help. |
-|SYSTEM_ERROR                  | Something went wrong. Please try again.             |
-|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.                             |
+| Error code                  | Description                                                                                                                                                  |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| INVALID_EMAIL               | The email address isn't formatted correctly.                                                                                                                 |
+| INVALID_PHONE               | The phone number is invalid.                                                                                                                                 |
+| INVALID_SUBSCRIPTION_STATUS | The subscription status is invalid. Check the status or leave it blank.                                                                                      |
+| CONFIGURATION_ERROR         | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help.     |
+| SYSTEM_ERROR                | Something went wrong. Please try again.                                                                                                                      |
+| 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. |
+| GLOBAL_STATE_NOT_SUBSCRIBED | Global state isn't subscribed or set, so Segment can't update subscription states.                                                                           |
+
+
+### Validation errors
+
+The following table lists validation errors you may run into with your CSV upload:
+
+| Error                                | Error Message                                                                                      |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------- |
+| Invalid file types                   | You can upload only .csv files. Change your file format, then try again.                           |
+| Empty files                          | This file contains no data. Add data to your CSV, then try again.                                  |
+| CSV parsing error                    | We encountered an issue while parsing your CSV file. Validate the CSV file and try again.          |
+| Unexpected/fallback                  | Something went wrong. Try again later.                                                             |
+| Empty header row                     | This file contains empty header(s). Remove the empty header(s), then try again.                    |
+| File exceeds one million rows        | Too many rows. You can upload up to 1000000 rows.                                                  |
+| File exceeds 100 MB                  | Files can be up to 100 MB.                                                                         |
+| Extraneous columns/column name typos | This file has columns that do not match the identifiers in your identity resolution configuration. |
 
 
 ## Set user subscriptions
@@ -115,7 +132,7 @@ Engage accepts both uppercase and lowercase subscription status values.
 > success ""
 > Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
 
-## CSV upload limits
+## Subscription group CSV upload limits
 
 Please note the following limits as you upload CSV files to Twilio Engage:
 - You can only upload .csv files.
@@ -125,6 +142,9 @@ Please note the following limits as you upload CSV files to Twilio Engage:
 - You can only upload one file at a time.
 - The CSV file size can't exceed 100 MB.
 - 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.
+- The `phone` and `email` identifiers must be valid phone numbers and email addresses, otherwise they'll process as errors.
+- The subscription group CSV upload only honors group subscriptions, so `sms_subscription_status`, `whatsapp_subscription_status`, and `email_subscription_status` aren't allowed.
+- Other than `[group_name]_subscription_status`, you should set up all columns in your identity resolution configuration.
 
 ## Message consent
 

diff --git a/src/engage/user-subscriptions/subscription-groups.md b/src/engage/user-subscriptions/subscription-groups.md
@@ -3,7 +3,7 @@ title: Subscription Groups
 plan: engage-premier
 ---
 
-Subscription groups let your users choose the emails they want to recieve from you. This page introduces subscription groups and explains how you can use them with [Engage email campaigns](/docs/engage/campaigns/email-campaigns/).
+Subscription groups let your users choose the emails they want to receive from you. This page introduces subscription groups and explains how you can use them with [Engage email campaigns](/docs/engage/campaigns/email-campaigns/).
 
 ## About subscription groups