segmentio · stayseesong · Oct 4, 2022 · Sep 7, 2022 · Sep 22, 2022 · Sep 22, 2022
@@ -6,8 +6,8 @@ sections:
     title: Connections
   - path: "https://segment.com/product/protocols/"
     title: Protocols
-  - path: "https://segment.com/product/personas/"
-    title: Personas
+  - path: "https://segment.com/product/twilio-engage/"
+    title: Twilio Engage
   - path: "https://segment.com/catalog/"
     title: Integrations Catalog
   - path: "https://segment.com/pricing/"

@@ -246,7 +246,7 @@ sections:
   - path: /profiles
     title: Profiles Overview
   - path: /profiles/quickstart
-    title: Quickstart Guide
+    title: Profiles Onboarding
   # - section_title: User Subscriptions
   #   slug: profiles/user-subscriptions
   #   section:
@@ -288,9 +288,9 @@ sections:
   - path: '/engage'
     title: Introduction
   - path: '/engage/quickstart'
-    title: Quickstart Guide
+    title: Foundations Onboarding
   - path: '/engage/onboarding'
-    title: Onboarding Steps
+    title: Premier Onboarding
   - path: '/engage/use-cases'
     title: Use Cases
   - section_title: User Subscriptions

@@ -65,7 +65,7 @@ Include additional information that you think will be useful to the user here. F
 ### Default Mapping
 
 > warning "Do not change the preset values"
-> We already provide preset values to all mappings and hence no changes are required in the Identify User Actions, and Track Event Actions.
+> Moengage provides preset values to all mappings and hence no changes are required in the Identify User Actions, and Track Event Actions.
 
 <!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
 

@@ -4,6 +4,7 @@ hide-boilerplate: true
 hide-dossier: true
 id: 62e17e6f687e4a3d32d0f875
 private: true
+hidden: true
 ---
 
 <!-- This template is meant for Actions-based destinations that do not have an existing Classic or non-Actions-based version. For Actions Destinations that are a new version of a classic destination, see the doc-template-update.md template. -->

@@ -8,10 +8,10 @@ hide-personas-partial: true
 [MoEngage](https://www.moengage.com/){:target="_blank"} is an Intelligent Customer Engagement Platform. MoEngage allows brands to personalize every customer interaction and drive better engagement, retention, loyalty and lifetime value.
 
 The MoEngage and Segment integration allows you to send 
-the users you have tracked on Segment, along with their route data, to MoEngage for further targetting and campaigning. This Destination enables you to:
+the users you have tracked on Segment, along with their route data, to MoEngage for further targeting and campaigning. This Destination enables you to:
 
-- **Import data from Segment to MoEngage**: We offer a side-by-side (device mode) SDK integration for your Android, iOS, and web applications and a server-to-server integration for your backend services.
-- **Sync [Segment Personas](https://segment.com/product/personas){:target="_blank"} (cohorts)**: Send Segment Cohorts to MoEngage for use in MoEngage Segments and campaigns. 
+- **Import data from Segment to MoEngage**: Moengage offers a side-by-side (device mode) SDK integration for your Android, iOS, and web applications and a server-to-server integration for your backend services.
+- **Sync [Twilio Engage](https://segment.com/product/twilio-engage){:target="_blank"} (cohorts)**: Send Segment Cohorts to MoEngage for use in MoEngage Segments and campaigns. 
 
 The MoEngage Destination source code is open-sourced and freely available on GitHub for anyone to view:
 
@@ -554,11 +554,11 @@ For more information, refer to [Configure and Integrate On-site Messaging](https
 
 Web Personalization is used to personalize the website experience for each user. A few popular use cases for Web Personalization include the home page banner personalization basis user behavior, localizing the website content basis user geography, testing the performance of new page layouts for improved performance, modifying the content shown on any webpage as per the user behavior.
 
-For more information, refer to [Configure and Integrate Web Personlization](https://developers.moengage.com/hc/en-us/articles/360062008891-Configure-and-Integrate-Web-Personlization){:target="_blank"}.
+For more information, refer to [Configure and Integrate Web Personalization](https://developers.moengage.com/hc/en-us/articles/360062008891-Configure-and-Integrate-Web-Personlization){:target="_blank"}.
 
-## Use Segment Personas with MoEngage
+## Use Twilio Engage with MoEngage
 
-[Computed traits](https://segment.com/docs/personas/computed-traits/) and [audiences](https://segment.com/docs/personas/audiences/) can be sent to MoEngage as custom attributes or custom events.
+You can send [Computed traits](/docs/engage/audiences/computed-traits/) and [Audiences](/docs/audiences/audiences/) to MoEngage as custom attributes or custom events.
 
 * Traits and audiences sent using the `identify` call will appear in MoEngage as _Tracked Custom Attributes_ with value as _True_.
 * Traits and audiences sent using the `track` call will appear in MoEngage as _Tracked User Events_.  
@@ -567,17 +567,16 @@ When connecting the calculated trait/audience to the MoEngage destination, you m
 
 ### Sync Time
 
-The default integration for MoEngage <> Segment Personas connection is **Real Time.** But there are some filters that will disqualify the persona from syncing in real-time, including some time-based filters which restrict your audience’s size at the time of message send.
+The default integration for MoEngage <> Twilio Engage connection is **Real Time.** But there are some filters that will disqualify the persona from syncing in real-time, including some time-based filters which restrict your audience’s size at the time of message send.
 
 ### Computed Traits using Identify calls
 
-To generate custom attributes in MoEngage, you may provide Computed Traits defined in Personas as `Identify` calls. The Computed Trait's value is used to set the custom attribute.
+To generate custom attributes in MoEngage, you may provide Computed Traits defined in Engage as `Identify` calls. The Computed Trait's value is used to set the custom attribute.
 
 ### Create a Segment Computed Trait
 
-1.  In Segment, navigate to the _Computed Traits_ in _Personas._
+1.  In Segment, navigate to the _Computed Traits_ in _Engage._
 2.  Click _New Computed Trait_.
-  ![segment_new_trait_button.png](images/segment_new_trait_button.png)
 3.  Create your computed trait. A lightning bolt in the top corner of the page will indicate if the computation updates in real-time.  
     ![segment_new_trait.png](images/segment_new_trait.png)
 4.  Next, select _MoEngage_ as your destination.  
@@ -589,9 +588,8 @@ To generate custom attributes in MoEngage, you may provide Computed Traits defin
 
 ### Create a Segment Audience
 
-1.  In Segment, navigate to the _Audience_ in _Personas._
+1.  In Segment, navigate to the _Audience_ in _Engage_
 2.  Click _New_.
-    ![segment_audience_1.png](images/segment_audience_1.png)
 3.  Create your audience. A lightning bolt in the top corner of the page will indicate if the computation updates in real-time.  
     ![segment_audience_2.png](images/segment_audience_2.png)
 4.  Next, select _MoEngage_ as your destination.  
@@ -602,12 +600,12 @@ To generate custom attributes in MoEngage, you may provide Computed Traits defin
 6.  In the computed trait or audience settings, adjust the connection settings based on how you would like your data sent to MoEngage.
     ![segment_audience_5.png](images/segment_audience_5.png)
 
-## Connect Segment Personas to MoEngage
+## Connect Twilio Engage to MoEngage
 
-You must first link MoEngage to your Segment Personas in order to send Computed Traits or Audiences. The first time you generate new Computed Trait or Audience, you may choose MoEngage as the destination for Personas data.
+First, link MoEngage to Twilio Engage to send Computed Traits or Audiences. The first time you generate new Computed Trait or Audience, you can choose MoEngage as the destination for the Engage data.
 
-1. Go to the Destinations tab in your Personas space.
-2. Search for MoEngage and add the MoEngage Destination to your Personas space.
+1. Go to the Destinations tab in your space.
+2. Search for MoEngage and add the MoEngage Destination to your Space.
 3. On the set up screen, enter your `App Id`, `App Key`, and your `Endpoint Region`.
 
 ## Segment users in MoEngage

@@ -8,16 +8,21 @@ versions:
   - name: Sprig (Actions)
     link: /docs/connections/destinations/catalog/sprig-web
 ---
-[Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segment_2021-10-20&utm_medium=int&utm_campaign=integration) is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real time, through microsurveys, concept tests, and video questions.
 
-Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment) or contact [[email protected]](mailto:[email protected]).
+[Sprig](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through In-Product Surveys, Concept and Usability tests.
 
-## Getting Started
+Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment){:target="_blank"} or contact [[email protected]](mailto:[email protected]).
+
+Segment placed the Classic destination framework in maintenance mode. Sprig encourages all customers to move to the [Sprig Actions](/docs/connections/destinations/catalog/sprig-web/) destination framework when convenient. 
+
+## Getting Started with Classic
 
 {% include content/connection-modes.md %}
 
-1. From the Destinations catalog page in the Segment App, click **Add Destination**.
-2. Search for "Sprig Cloud" in the Destinations Catalog, and select the Sprig Cloud destination.
-3. Choose which Source should send data to the Sprig Cloud destination.
-4. Go to the [Sprig Connect page](https://app.sprig.com/connect), and find and copy the Segment **API key**. Use the Development key for a testing environment, and the Production key for your live environment.
-5. Enter the API Key that you copied in the Sprig Cloud destination settings in Segment.
+1. In the Segment web app, navigate to **Catalog > Destinations**.
+2. Type *Sprig* in the **Filter Destinations** field.
+3. Click **Sprig**, then click **Configure Sprig**.
+4. Select an existing JavaScript website source to connect to Sprig and click **Next**.
+5. Enter a **Destination name**, select **Classic**, and click **Save**.
+6. Type in the Environment ID and click Save Changes. You your Environment ID can be found in [Connect > JavaScript](https://app.sprig.com/connect){:target="_blank". For for information, click [here](https://docs.sprig.com/docs/products-and-environments#environments){:target="_blank"}.
+7. Select **Enable Destinations** and click **Save Changes**.
@@ -1,5 +1,5 @@
 ---
-title: 'Sprig (Actions) Destination'
+title: 'Sprig Actions'
 hidden: false
 hide-boilerplate: true
 hide-dossier: true
@@ -15,36 +15,37 @@ versions:
 
 {% include content/plan-grid.md name="actions" %}
 
-[Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through microsurveys, concept tests, and video questions.
+[Sprig](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through In-Product Surveys, Concept and Usability tests.
 
-Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment-web) or contact [[email protected]](mailto:[email protected]).
+Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment){:target="_blank"} or contact [[email protected]](mailto:[email protected]).
 
 
-## Benefits of Sprig (Actions) vs Sprig Classic
+## Benefits of Sprig Actions versus Sprig Classic
 
-Sprig (Actions) provides the following benefits over the classic Sprig destination:
+Sprig Actions provides the following benefits over the Sprig Classic destination:
 
-- **Trigger microsurveys**. Because Sprig (Actions) hooks into your browser-based, JavaScript Segment source, it can be used to trigger Sprig microsurveys.
-- **Code-free Sprig installation**. The Sprig (Actions) destination can install the Sprig SDK onto your website, without you having to update any code.
+- **Trigger studies**. Sprig Actions integrate into your browser-based Analytics.js source, so you can use them to trigger Sprig studies.
+- **Code-free Sprig installation**. You can intall Sprig Actions on your website, without you having to update any code. 
 
 <!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
 
-## Getting started
+## Getting started 
 
-1. From the Segment web app, click **Catalog**, then click **Destinations**.
-2. Use the navigation on the left to locate and select Sprig (Actions).
-3. Click **Configure Sprig (Actions)**.
-4. Select an existing JavaScript website source to connect to Sprig (Actions).
-5. Find your Environment ID on [Sprig Dashboard > Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. Use the Development Environment ID for a testing environment, and the Production Environment ID for your live website environment. When you configure the destination, input the appropriate Environment ID.  
-6. Select **Quick Setup** to start with pre-populated subscriptions, or **Customized Setup** to configure each action from scratch. Click **Configure Actions** to complete setup.
+1. In the Segment web app, click **Catalog**, then click **Destinations**.
+2. Type Sprig in the **Filter Destinations** field.
+3. Click **Sprig**, then click **Configure Sprig**.
+4. Select an existing JavaScript website source to connect to Sprig and click **Next**.
+5. Type in a **Destination name**, Select **Actions**, and click **Save**.
+6. Type in the Environment ID and click Save Changes. Your Environment ID can be found in [Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. For for information, click [here](https://docs.sprig.com/docs/products-and-environments#environments){:target="_blank"}.
+7. Select **Enable Destinations** and click **Save Changes**.
 
 <!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
 
 {% include components/actions-fields.html %}
 <!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
 
-## Migration from the classic Sprig destination
+## Migration from Sprig Classic
 
-To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
+Segment placed the Classic destination framework in maintenance mode. Sprig encourages all customers to move to the Actions destination framework. To prevent the generation of duplicate events in Sprig, don't enable the Sprig Web destination and the Sprig Cloud destination on the same source. 
 
 
@@ -75,7 +75,7 @@ In order to track these `click` events simply add a trigger with a `selector`, w
     "vars": {
       "writeKey": "WRITE_KEY",
       "name": "My Page Name"
-    }
+    },
     "triggers": {
       "click": {
         "on": "click",

@@ -5,7 +5,7 @@ redirect_from:
   - '/personas/'
 ---
 
-Powered by real-time data, Engage is a customizable personalization platform with which you can build, enrich, and activate Audiences.
+Powered by real-time data, Twilio Engage (formerly known as Personas) is a customizable personalization platform with which you can build, enrich, and activate Audiences.
 
 Engage Channels builds on top of these Audiences, helping you connect with and market to your customers through email and SMS campaigns.
 

@@ -1,16 +1,19 @@
 ---
-title: Onboard to Twilio Engage
-plan: engage-foundations
+title: Twilio Engage Premier Onboarding Guide
+plan: engage-premier
 redirect_from:
   - '/engage/overview/onboarding'
 ---
 
-Twilio Engage brings Segment, Twilio, and SendGrid together to help you create and send email and SMS campaigns to your customers.
+Twilio Engage (formerly known as Personas) brings Segment, Twilio, and SendGrid together to help you create and send email and SMS campaigns to your customers.
 
 Before sending your first Engage campaign, though, you’ll need to configure and connect accounts with all three platforms.
 
 This guide lists all required onboarding steps and walks you through Engage setup. By the end of the onboarding process, you’ll be ready to send your first campaign.
 
+> info ""
+> The steps in this guide are only required if you plan to send email and SMS messages with Engage. Visit the [Engage Foundations Onboarding Guide](/docs/engage/quickstart) for general onboarding steps to set up your Engage space, connect sources, create audiences, and more.
+
 ## Before you begin: overview and task checklist
 
 You’ll set up Twilio Engage in three stages:

@@ -1,5 +1,5 @@
 ---
-title: Engage Quickstart Guide
+title: Twilio Engage Foundations Onboarding Guide
 plan: engage-foundations
 redirect_from:
   - "/personas/quickstart"
@@ -8,7 +8,7 @@ redirect_from:
 This guide walks you through the set up process for a simple Engage space, which you can use if your Segment implementation is simple. If your implementation is complex, you can use this to demonstrate and test Engage before working on a more complex configuration.
 
 > success ""
-> The first four steps in this guide also apply to Profiles set up. To learn more, visit the [Profiles Quickstart Guide](/docs/profiles/quickstart).
+> The first four steps in this guide also apply to Profiles set up. To learn more, visit the [Profiles Onboarding Guide](/docs/profiles/quickstart).
 
 ## Engage configuration requirements
 > info ""
@@ -46,7 +46,7 @@ To learn more, visit [Connect production sources](/docs/profiles/quickstart/#ste
 
 ## Step 4: Check your profile data
 
-Once the replay finishes, you can see the data replayed into Engage using the Profile Explorer. Visit the [Profiles Quickstart Guide](/docs/profiles/quickstart/#step-4-check-your-profile-data) for more info.
+Once the replay finishes, you can see the data replayed into Engage using the Profile Explorer. Visit the [Profiles Onboarding Guide](/docs/profiles/quickstart/#step-4-check-your-profile-data) for more info.
 
 ## Step 5: Create an Audience
 

@@ -15,7 +15,7 @@ You can then use this interaction data with customer engagement tools, such as E
 > Profiles is an add-on to Segment Connections Business Tier. It's also a required add-on for Twilio Engage.
 > To use [Computed Traits](/docs/engage/audiences/computed-traits/) and [Audiences](/docs/engage/audiences/) with profiles, you must have access to Engage.
 
-To set up and get data flowing through Profiles, visit Segment's [Quickstart Guide](/docs/profiles/quickstart).
+To set up and get data flowing through Profiles, visit Segment's [Onboarding Guide](/docs/profiles/quickstart).
 
 ## Identity Resolution