Merge pull request #538 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/engage/profiles/csv-upload.md

@@ -85,6 +85,8 @@ In the `email_subscription_status` and `sms_subscription_status` columns, set su
 - `did-not-subscribe`: The user has provided their contact information but didn't actively subscribe or unsubscribe.
 - **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.
 
+Engage accepts both uppercase and lowercase subscription status values.
+
 > success ""
 > Only contact users that subscribe to your communications. View [User Subscription States](/docs/engage/profiles/user-subscriptions/subscription-states/) to learn more.
 

src/engage/profiles/user-subscriptions/set-user-subscriptions.md

@@ -30,6 +30,9 @@ These columns take the following values:
 - `did-not-subscribe`; for users who have neither subscribed nor unsubscribed from your marketing campaigns
 - Blank; for email addresses or phone numbers that Segment collected without the user explicitly providing them
 
+> success ""
+> Engage accepts both uppercase and lowercase subscription status values.
+
 Refer to the [User Subscription States documentation](/docs/engage/profiles/user-subscriptions/subscription-states/) for detailed explanations of each subscription state.
 
 <!--
@@ -61,7 +64,7 @@ When you update user subscriptions with Segment's Public API, however, you'll ge
 
 ### Format the Identify call payload
 
-For Segment to process the subscription status request, your Identify call payload must include at least one object that contains an email address or phone number, its subscription type, and its subscription status.
+For Segment to process the subscription status request, your Identify call payload must include at least one object that contains an email address or phone number, its subscription type, and its subscription status. Engage accepts both uppercase and lowercase subscription statuses in Identify calls.
 
 The following example payload shows an Identify call with a `context` object, which you'll add to the Identify call to update user subscriptions. The `context` object contains a `messaging_subscriptions` array with two objects that update both SMS and email subscription statuses: