Merge branch 'develop' into catalog-refactor-2

Author: forstisabella

src/_data/catalog/slugs.yml

@@ -188,4 +188,6 @@ destinations:
   - original: "regal-io"
     override: "regal"
   - original: "rehook"
-    override: "actions-rehook"
+    override: "actions-rehook"
+  - original: "bucket-web-actions"
+    override: "bucket-web"

src/_data/sidenav/main.yml

@@ -577,6 +577,8 @@ sections:
       title: Audit Trail
     - path: /segment-app/iam/sso
       title: Single Sign On
+    - path: /segment-app/iam/scim
+      title: System for Cross-domain Identity Management (SCIM) Configuration Guide
     - path: /segment-app/iam/mfa
       title: Multi-Factor Authentication (MFA)
   - path: /segment-app/iam/secure-password

src/connections/sources/catalog/cloud-apps/onesignal/index.md

@@ -47,40 +47,46 @@ OneSignal doesn't send user email address or phone number details to Segment.
 
 The following table lists the events that OneSignal sends to Segment. These events appear as tables in your warehouse and as regular events in other destinations. 
 
-| Event Kind                    | Event Description                                    |
+| MessageEvent Kind             | Event Description                                    |
 | ----------------------------- | ---------------------------------------------------- |
 | Push Sent                     | Push notification successfully sent                  |
 | Push Received                 | Push notification successfully received              |
 | Push Clicked                  | Push notification touched on device                  |
-| In-App Message Displayed      | In-App Message successfully displayed on device      |
+| In-App Message Impression     | In-App Message successfully displayed on device      |
 | In-App Message Clicked        | In-App Message clicked on device                     |
 | In-App Message Page Displayed | In-App Message page is displayed                     |
 | Email Sent                    | Email successfully sent                              |
+| Email Received                | Email received by recipient                          |
 | Email Opened                  | Email opened by recipient                            |
+| Email Link Clicked            | Email contained link, link clicked                   |
 | Email Unsubscribed            | Email unsubscribed by recipient                      |
-| Email Received                | Email received by recipient                          |
 | Email Reported As Spam        | Email reported as spam by recipient                  |
-| Email Hardbounced             | Email returned to sender due to permanent error      |
-| Email Failed                  | Could not deliver the email to the recipient's inbox |
+| Email Bounced                 | Email returned to sender due to permanent error      |
+| Email Failed                  | Could not deliver the email to the recipient’s inbox |
+| Email Suppressed              | Email is suppressed for a subscription               |
 | SMS Sent                      | SMS sent to recipient                                |
-| SMS Delivered                 | SMS successfully delivered                           |
 | SMS Failed                    | SMS failed to send                                   |
+| SMS Delivered                 | SMS successfully delivered                           |
+| SMS Undelivered               | SMS undelivered for a subscription                   |
 
 ## Event properties
 
 The following table lists the properties included in the events from the Events table.
 
-| Property Name       | Description                                        |
-| ------------------- | -------------------------------------------------- |
-| `messageId`         | The identifier of the discrete message             |
-| `campaign_id`       | The identifier of the message campaign             |
-| `message_name`      | The message name                                   |
-| `message_title`     | The message title                                  |
-| `message_contents`  | The message contents                               |
-| `message_type`      | The type of message sent, push, in-app, email, SMS |
-| `subscription_type` | The channel the message was sent through           |
-| `template_id`       | The message template used                          |
-| `onesignal_id`      | The OneSignal set user identifier                  |
+| Property Name              | Description                                                                           |
+| -------------------------- | ------------------------------------------------------------------------------------- |
+| `userId`                   | The `external_id` associated with the message                                           |
+| `anonymousId `             | The `subscription_id` associated with the message (only sent if there is no `external_id`) |
+| `messageId`                | The identifier of the discrete message                                                |
+| `campaign_id`              | The identifier of the message campaign                                                |
+| `message_name`             | The message name                                                                      |
+| `message_title`            | The message title only for push and email                                             |
+| `message_contents`         | The message contents only for push and sms                                            |
+| `template_id`              | The message template used                                                             |
+| `subscription_id`         | The OneSignal set device/email/sms identifier                                         |
+| `subscription_device_type` | The device type that received the message                                             |
+| `language`                 | The two character language code of the device                                         |
+| `message_type`             | The type of message sent (push, in-app, email, or SMS)                                    |
 
 
 

src/connections/sources/catalog/cloud-apps/white-label-loyalty/index.md

@@ -0,0 +1,44 @@
+---
+title: White Label Loyalty Source
+id: xeZMgSrtAQ
+beta: true
+---
+
+[White Label Loyalty](https://whitelabel-loyalty.com/){:target="_blank”} is an event-powered loyalty solution to drive customer retention.
+
+This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) that can not only export data into your Segment warehouse but also federate the exported data into your other Segment-enabled destinations.
+
+White Label Loyalty maintains this source. For any issues with the source, [contact their support team](mailto:[email protected]).
+
+## Getting started
+
+1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”}, click **Add Source**.
+2. Search for "White Label Loyalty" in the Sources Catalog, select White Label Loyalty, and click **Add Source**.
+3. On the next screen, give the source a name and configure any other settings.
+
+   - The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommend using something that reflects the source itself and distinguishes amongst your environments (for example, `WhiteLabel_Prod`, `WhiteLabel_Staging`, `WhiteLabel_Dev`).
+
+4. Click **Add Source** to save your settings.
+5. Copy the write key from the Segment UI.
+6. In the White Label Loyalty Console, navigate to **Settings > Integrations > Extensions** and click **Create**. Alternatively, you can edit an existing Segment integration.
+7. Paste the write key in when prompted.
+8. (Optional:) Specify a JSON path to use for the users ID (defaults to `authIdentifier`).
+9. Click **Save**.
+
+## Stream
+
+White Label Loyalty uses Segment's stream source component to send Segment event data. The source uses server-side Track and Identify methods to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.
+
+By default, White Label Loyalty passes the `authIdentifier` associated with the user as the `userId`. You can specify a custom JSONPath in the White Label Loyalty Console to change the source of the `userId`.
+
+## Events
+
+White Label Loyalty will send all custom and intrinsic event types created in the White Label Loyalty Console, as per the schema provided when you set it up. White Label Loyalty will send all events reported against a user and include the `userId`.
+
+## Adding destinations
+
+Now that your source is set up, you can connect it with Destinations.
+
+Log in to your downstream tools and verify that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the [Event Delivery](/docs/connections/event-delivery/) tool, and refer to the destination docs for each tool for troubleshooting.
+
+If you experience any issues with how events are arriving to Segment, [contact the White Label Loyalty support team](mailto:[email protected]).

src/engage/campaigns/mobile-push/index.md

@@ -354,6 +354,9 @@ Follow these steps to set up mobile push in Twilio Engage.
 12. Click **Verify**, then select the messaging services you want to use in your space.
 13. Click **Save Twilio Account.**
 
+> info "Removing messaging services"
+> To remove a messaging service, navigate to Engage > Engage settings > Channels and click the pencil icon under **Twilio messaging service**. Enter the account credentials by either using the API key secret or creating a new API key. Once you've selected the desired services, they will override the existing ones, effectively removing the ones you no longer need.
+
 ### 5b. Create a new push service
 
 Complete mobile push onboarding by creating a new push service:

src/segment-app/iam/scim.md

@@ -11,7 +11,7 @@ Most IdPs offer SCIM, and it complements SAML. You can think of SAML as a way fo
 
 Before you start, remember that SSO is only available to Business Tier customers, and that only workspace owners may configure SSO connections.
 
-To set up SCIM, you must first create an SSO connection. Once you [create your SSO connection](https://segment.com/docs/segment-app/iam/sso/), log back in to Segment using SSO.
+To set up SCIM, you must first create an SSO connection. Once you [create your SSO connection](/docs/segment-app/iam/sso/), log back in to Segment using SSO.
 
 ## Configuration Instructions
 
@@ -27,15 +27,15 @@ Your IdP needs to know where to send SCIM requests. The Segment base URL is: htt
 
 The other value you need is an API key (sometimes referred to as an Authorization Header). To generate one, go to **Settings > Advanced Settings** in the Segment app, and find the **SSO Sync** section. Click **Generate SSO Token** and copy the generated token. Use this token for the API key or Authorization Header in your IdP.
 
-This page is located as part of the settings sidebar: https://app.segment.com/CUSTOMER_WORKSPACE_SLUG/settings/advanced
+You can find this page in the [settings sidebar of your Segment app](https://app.segment.com/goto-my-workspace/settings/advanced){:target="_blank”}.
 
 ![Screenshot of the Segment settings sidebar, with Advanced Settings selected.](images/asset_generate_scim_token.png)
 
 ## Features
 
 It's important to remember that Segment has a multi-tenant user/workspace relationship, meaning that users can be part of more than one workspaces. In most cases these workspaces are all related to a single customer (for example, a single company might have individual workspaces for different brands or subsidiaries). However, some users can be members of workspaces for different Segment customers, such as with contractors or consultants.
 
-Because of this, Segment must balance the autonomy of our users with the desired level of control of a workspace owner.
+Because of this, Segment must balance the autonomy of users with the desired level of control of a Workspace Owner.
 
 ## Creating Users
 
@@ -69,7 +69,7 @@ Your IdP can create new groups in Segment using SCIM. All groups created using S
 
 ## Updating Groups
 
-Your IdP can add or remove workspace members from existing groups via SCIM. Your IdP can also update Segment group names.
+Your IdP can add or remove workspace members from existing groups using SCIM. Your IdP can also update Segment group names.
 
 ## Deleting Groups
 
@@ -87,7 +87,7 @@ For example, you might map `{firstName} {lastName}` from your IdP to `displayNam
 
 ## Okta Set up Guide
 
-1. [Complete the Okta Set up Guide for SSO](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Segment.html?baseAdminUrl=https://segment-admin.oktapreview.com&app=segment&instanceId=0oata15py1n3kQUo50h7)
+1. [Complete the Okta Set up Guide for SSO](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Segment.html?baseAdminUrl=https://segment-admin.oktapreview.com&app=segment&instanceId=0oata15py1n3kQUo50h7){:target="_blank”}
 2. Click **Provisioning**, then click **Configure API Integration** and select **Enable API Integration**.
 3. [Generate an API key](#api-key), then copy and paste this value into the **API Token** field in Okta, and click **Save**.
 
@@ -113,14 +113,14 @@ For example, you might map `{firstName} {lastName}` from your IdP to `displayNam
 
 Instructions for configuring Azure AD can be found on the Microsoft Docs website.
 
-1. [Complete the Azure AD Set up Guide for SSO](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/segment-tutorial)
+1. [Complete the Azure AD Set up Guide for SSO](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/segment-tutorial){:target="_blank”}.
 
-2. [Complete the Azure AD Set up Guide for SCIM](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/segment-provisioning-tutorial)
+2. [Complete the Azure AD Set up Guide for SCIM](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/segment-provisioning-tutorial){:target="_blank”}.
 
 ## OneLogin Set up Guide
 
 Instructions for configuring OneLogin can be found on the OneLogin Docs website.
 
-1. Add and configure the Segment SSO integration from within the OneLogin application
+1. Add and configure the Segment SSO integration from within the OneLogin application.
 
-2. [Complete the OneLogin Set up Guide for SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=a7833cd7db3a30501c167e77f4961923)
+2. [Complete the OneLogin Set up Guide for SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=a7833cd7db3a30501c167e77f4961923){:target="_blank”}.

vale-styles/Vocab/Docs/accept.txt

@@ -97,3 +97,4 @@ waitlist
 WebKit
 Wootric
 Zendesk
+Okta