Some Engage updates

Author: pwseg

src/connections/sources/catalog/cloud-apps/engage-events/index.md

@@ -14,7 +14,7 @@ Use the Engage Events Source to sync Engage subscription states and messaging ev
 
 With Twilio Engage, you can [set and update user subscription states](/docs/engage/user-subscriptions/set-user-subscriptions/) with a [CSV file upload](/docs/engage/profiles/csv-upload/) or, programmatically, [using Segment APIs](/docs/engage/user-subscriptions/set-user-subscriptions/#manage-user-subscriptions-with-segment-apis).
 
-As part of Engage, Segment creates an Engage Events Source that lets you sync subscription states and marketing analytics events [to connected Destinations](/docs/connections/destinations/). When a subscription state changes, Segment sends an update to the Destination. As a result, the subscription states stored in your Destination(s) can serve as a single source of truth for managing user consent in other tools that you may have connected to the Destination.
+As part of Engage, Segment creates an Engage Events Source that lets you sync subscription states and marketing analytics events to [connected Destinations](/docs/connections/destinations/). When a subscription state changes, Segment sends an update to the Destination. As a result, the subscription states stored in your Destination(s) can serve as a single source of truth for managing user consent in other tools that you may have connected to the Destination.
 
 ## Working with Engage Events Sources
 
@@ -108,4 +108,13 @@ SendGrid powers Engage email delivery. For more information, view [SendGrid's Ev
 | Group Subscription Updated   | A user updated their subscription to a specific group. |
 
 {% endfaqitem %}
+
+{% faqitem Journeys and Broadcast events %}
+
+| Event            | Definition                        |
+| ---------------- | --------------------------------- |
+| Audience Entered | A user entered an Engage audience |
+
+{% endfaqitem %}
+
 {% endfaq %}

src/engage/settings.md

@@ -14,14 +14,20 @@ If you see no credentials listed under the Channels tab, it means you've not yet
 
 ## Destinations settings
 
-The **Destinations** tab lists the downstream tools receiving your Engage data. Selecting a Destination from the list gives you a detailed view of the Audiences, Computed Traits, and Journeys that Segment sends to the Destination.
+The **Destinations** tab lists the downstream tools receiving your Engage data. Selecting a destination from the list gives you a detailed view of the audiences, computed traits, and journeys that Segment sends to the destination.
 
-To add a Destination, select the **+ Add destination** button, or navigate to **Connections > Destinations** within your Segment workspace. To learn more about sending Engage information to Segment Destinations, view the [Using Engage Data](/docs/engage/using-engage-data/) documentation.
+To add a destination, select the **+ Add destination** button, or navigate to **Connections > Destinations** within your Segment workspace. To learn more about sending Engage information to Segment destinations, view the [Using Engage Data](/docs/engage/using-engage-data/) documentation.
 
-You can delete a Destination from the Destinations tab in the Engage settings (**Engage > Engage settings > Destinations**). 
+You can delete a destination from the Destinations tab in the Engage settings (**Engage > Engage settings > Destinations**). 
 
 ## Warehouse sources
 
 By connecting your existing warehouses to Engage, you can import customer or account data and use it to build SQL traits. The Warehouse sources tab displays the warehouses sending data to Engage.
 
 To add a new data warehouse, select the **+ Add warehouse source** button. For more information on working with your imported warehouse data in Engage, read the [Engage SQL traits](/docs/engage/audiences/sql-traits/) guide.
+
+## Engage Events source
+
+The Engage Events source lets you sync subscription states, messaging events, and marketing analytics to downstream destinations. To find your Engage Events source in your Segment workspace, navigate to **Connections > Sources** and select **Engage Events**.
+
+For more information, view the [Engage Events Source documentation](/docs/connections/sources/catalog/cloud-apps/engage-events/).

src/engage/warehouses.md

@@ -148,5 +148,8 @@ Yes. You can use [Warehouses Selective Sync](/docs/connections/storage/warehouse
 
 ### Why are there multiple schemas prefixed with `engage_` in my warehouse when I only have one space?
 
-Segment currently can only connect a source to one instance of each destination, for example, one source cannot send to two different Amplitude instances. To get around this restriction, Engage creates multiple sources to send events to the destinations connected to your space.
+Segment can only connect a source to one instance of each destination. For example, one source cannot send to two different Amplitude instances. As a workaround, Engage creates multiple sources to send events to the destinations connected to your space.
+
 For example, if you have three webhook destinations in your space, Engage creates three different sources to send events to them. This creates three different warehouse schemas, and is usually the reason you have more schemas than spaces.
+
+This approach doesn't apply to messaging destinations, however. Messaging destinations connected from journeys and broadcasts don't generate multiple background sources.