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/user-subscriptions/csv-upload.md
+1-15Lines changed: 1 addition & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ Use the Update History page to view CSV file uploads in your workspace over the
64
64
To view the Update History page:
65
65
66
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**.
67
+
2. From the **Subscriptions**section, click **View update history**.
68
68
3. From the **Upload history** table, click the file name link to download the [error reports](#error-reports).
69
69
70
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.
@@ -90,7 +90,6 @@ Engage uses the following error codes on the report:
90
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
91
| SYSTEM_ERROR | Something went wrong. Please try again. |
92
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
93
95
94
96
95
### Validation errors
@@ -132,19 +131,6 @@ Engage accepts both uppercase and lowercase subscription status values.
132
131
> success ""
133
132
> Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/user-subscriptions/subscription-states/) to learn more.
134
133
135
-
## Subscription group CSV upload limits
136
-
137
-
Please note the following limits as you upload CSV files to Twilio Engage:
138
-
- You can only upload .csv files.
139
-
- Files can't be empty and must have at least one header and one row.
140
-
- You can't have multiple columns with the same header.
141
-
- Upload CSV files with up to 1 million rows (plus one header row).
142
-
- You can only upload one file at a time.
143
-
- The CSV file size can't exceed 100 MB.
144
-
- 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.
Copy file name to clipboardExpand all lines: src/engage/user-subscriptions/subscription-groups.md
+53-1Lines changed: 53 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Follow these steps to create a subscription group:
35
35
4. (Optional:) Add subscribers to your group with a CSV file upload, then click **Next**.
36
36
5. Review your new subscription group, then click **Create Subscription Group**.
37
37
38
-
### Add group susbcribers
38
+
### Add group subscribers
39
39
40
40
In addition to adding group subscribers when you first create a subscription group, you can also add subscribers to existing groups with a CSV file upload with these steps:
41
41
@@ -44,6 +44,58 @@ In addition to adding group subscribers when you first create a subscription gro
44
44
3. Download the template CSV file, then fill it out by entering email addresses and subscription groups. The subscription group should follow the format `[group_name]_subscription_status`.
45
45
4. Upload the CSV file, then click **Add Subscribers**.
46
46
47
+
### Validation errors
48
+
49
+
The following table lists validation errors you may run into with your CSV upload:
| INVALID_EMAIL | The email address isn't formatted correctly. |
77
+
| INVALID_PHONE | The phone number is invalid. |
78
+
| INVALID_SUBSCRIPTION_STATUS | The subscription status is invalid. Check the status or leave it blank. |
79
+
| CONFIGURATION_ERROR | Your SendGrid settings are not configured correctly. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="_blank"} for help. |
80
+
| SYSTEM_ERROR | Something went wrong. Please try again. |
81
+
| 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. |
82
+
| GLOBAL_STATE_NOT_SUBSCRIBED | Global state isn't subscribed or set, so Segment can't update subscription states. |
83
+
84
+
85
+
#### Subscription group CSV upload limits
86
+
87
+
Please note the following limits as you upload CSV files to Twilio Engage:
88
+
- You can only upload .csv files.
89
+
- Files can't be empty and must have at least one header and one row.
90
+
- You can't have multiple columns with the same header.
91
+
- Upload CSV files with up to 1 million rows (plus one header row).
92
+
- You can only upload one file at a time.
93
+
- The CSV file size can't exceed 100 MB.
94
+
- 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.
95
+
- The `phone` and `email` identifiers must be valid phone numbers and email addresses, otherwise they'll process as errors.
96
+
- The subscription group CSV uploader only honors group subscriptions, so `sms_subscription_status`, `whatsapp_subscription_status`, and `email_subscription_status` aren't allowed.
97
+
- Other than `[group_name]_subscription_status`, you should set up all columns in your identity resolution configuration.
0 commit comments