some more rearranging [netlify-build]

Author: pwseg

src/engage/event-mapping-configuration.md

@@ -3,36 +3,26 @@ title: Engage Event Mapping
 plan: engage-foundations
 ---
 
-This guide explains how to configure mappings for Engage events in Actions Destinations, 
+This guide explains how to configure mappings for Engage events in [Actions Destinations](/docs/connections/destinations/actions/).
 
 ## Overview
 
-Engage Mappings let you transform and send user data to downstream destinations. Engage events sent to destinations may need to be formatted or adjusted, though, to match the destination’s expected data structure. Without mapping, critical user information like audience membership or enriched traits may not sync correctly.
+Engage mappings let you transform and send user data to downstream destinations. Engage events sent to destinations may need to be formatted or adjusted, though, to match the destination’s expected data structure. Without mapping, critical user information like audience membership or enriched traits may not sync correctly.
 
 This guide covers:
 
 - The differences between [Identify](/docs/connections/spec/identify/) and [Track](/docs/connections/spec/track/) events.
 - How to extract and map data from Engage event payloads.
 - A step-by-step walkthrough of mapping configurations.
-- Advanced features like Trait Enrichment that you can use to pass additional profile data.
+- Advanced features like trait enrichment that you can use to pass additional profile data.
 
 ## About Engage events
 
 Before you create a mapping, you need to understand how Segment structures Engage events. Where the data lives in each event affects how you map it.
 
-Engage sends two types of events: Identify and Track. These two event types use different parts of the event payload to store user data. If you're mapping an email address, an audience membership, or a trait like `first_name`, you need to know where to look for that value in each event type.
+This section lists the important Engage event fields, breaks down the difference between Identify and Track events, shows you what each payload looks like, and explains where to find data you'll typically want to map so you can configure mappings correctly and avoid pitfalls.
 
-If you map from the wrong part of the payload, your data might not reach the destination at all, or it might show up incorrectly. 
-
-This section breaks down the difference between Identify and Track events, shows you what each payload looks like, and explains where to find data you'll typically want to map so you can configure mappings correctly and avoid pitfalls.
-
-<!-- Engage events carry critical information, including:
-
-- User identifiers (like `userId` and `anonymousId`)
-- Audience membership status
-- Other user traits, if you've enabled enrichment 
-
-## Key Engage event fields
+### Key Engage event fields
 
 The following properties appear in Engage event payloads:
 
@@ -44,7 +34,7 @@ The following properties appear in Engage event payloads:
 | `context.traits` | Object | In Track events, this object stores user attributes like `email`. |
 | `properties`     | Object | Stores event-related data, including audience membership.         | 
 
-Understanding these fields will help you correctly set up mappings and send Engage data to external destinations. -->                                                   
+Understanding these fields will help you correctly set up mappings and send Engage data to external destinations.                                                 
 
 ### Engage event types and structure
 
@@ -55,6 +45,27 @@ Engage uses two event types to deliver data to downstream destinations:
 
 These events structure data differently, which directly affects how you should configure mappings.
 
+### Understanding the difference between Identify and Track in Engage
+
+Engage sends both Identify and Track events when a user enters or exits an audience. While these events can contain similar information, they serve different purposes.
+
+Identify events answer the question, "Who is this user right now?" They update the user’s profile with traits like email, name, and audience membership. For example: “Jane’s email is `[email protected]`. She’s in the `browse_abandoners` audience. Her first name is `jane`.”
+
+Track events capture a specific moment in time, like when a user joins or leaves an audience. For example: “Jane just entered the `browse_abandoners` audience.”
+
+Engage sends both types of events because different destinations rely on different types of data. Identify events are used to keep user profiles up to date, whereas Track events are useful for triggering time-sensitive actions based on audience entry or exit.
+
+For example, you might use an Identify event to sync the current list of users in an audience to your CRM. But if you want an ad platform to show an ad the moment someone enters an audience, you'd use a Track event.
+
+The following table summarizes the differences between Identify and Track events in Engage:
+
+| Attribute              | Identify                                  | Track                                                 |
+| ---------------------- | ----------------------------------------- | ----------------------------------------------------- |
+| What it describes      | The user’s current traits and attributes  | A specific moment or action (like audience entry)     |
+| When to use it         | To update a user profile in a destination | To trigger an action based on something that happened |
+| Audience data location | `traits`                                  | `properties`                                          |
+| Email location         | `traits.email`                            | `context.traits.email`                                |
+
 #### Identify events: updating user traits
 
 Identify events represent who the user is. These events usually update or enrich profiles in destinations like CRMs and email tools.
@@ -83,7 +94,7 @@ Here's an example of an Engage Identify event payload:
 
 In this example, a user just entered the `browse_abandoners` audience. If the value for the audience were `false`, it would mean the user just **exited** the audience.
 
-### Track events: logging user actions
+#### Track events: logging user actions
 
 Track events, on the other hand, represent something the user did. These events capture user actions and log events and behaviors.
 
@@ -117,28 +128,7 @@ Here's an example of an Engage Track event payload:
 
 In this example, a user just entered the `browse_abandoners` audience. The audience flag and traits are nested in `properties`, and the email address is in `context.traits.email`.
 
-### Understanding the difference between Identify and Track in Engage
-
-Engage sends both Identify and Track events when a user enters or exits an audience. While these events can contain similar information, these events serve different purposes.
-
-Identify events answer the question, "Who is this user right now?" They update the user’s profile with traits like email, name, and audience membership. For example: “Jane’s email is `[email protected]`. She’s in the `browse_abandoners` audience. Her first name is `jane`.”
-
-Track events capture a specific moment in time, like when a user joins or leaves an audience. For example: “Jane just entered the `browse_abandoners` audience.”
-
-Engage sends both types of events because different destinations rely on different types of data. Identify events are used to keep user profiles up to date, whereas Track events are useful for triggering time-sensitive actions based on audience entry or exit.
-
-For example, you might use an Identify event to sync the current list of users in an audience to your CRM. But if you want an ad platform to show an ad the moment someone enters an audience, you'd use a Track event.
-
-The following table summarizes the differences between Identify and Track events in Engage:
-
-| Attribute              | Identify                                  | Track                                                 |
-| ---------------------- | ----------------------------------------- | ----------------------------------------------------- |
-| What it describes      | The user’s current traits and attributes  | A specific moment or action (like audience entry)     |
-| When to use it         | To update a user profile in a destination | To trigger an action based on something that happened |
-| Audience data location | `traits`                                  | `properties`                                          |
-| Email location         | `traits.email`                            | `context.traits.email`                                |
-
-<!-- PW: maybe add a transition here -->
+Now that you understand the different purposes each event type serves, you're ready to configure a mapping.
 
 ## Configure mappings
 
@@ -150,8 +140,8 @@ The following sections walk through each event type and show how to configure a
 
 Before you begin, make sure you've done the following:
 
-- Created an audience in Engage
-- Connected an Actions destination
+- Created [an audience in Engage](/docs/engage/audiences/)
+- Connected an [Actions destination](/docs/connections/destinations/actions/#available-actions-based-destinations)
 - Confirmed whether the destination expects Identify or Track events
 - Located your audience key (you'll use it to configure the trigger)
 
@@ -160,7 +150,7 @@ Before you begin, make sure you've done the following:
 To create a mapping, follow these steps:
 
 1. In your Segment workspace, go to **Connections > Destinations**.
-2. Select the destination where you want to send Engage data.
+2. Select the (Actions) destination you want to send Engage data to.
 3. On the destination overview page, click **Mappings > + New mapping**.
 4. Choose the event type you want to use: Identify or Track.
 
@@ -170,8 +160,6 @@ After you select the event type, you'll configure a trigger to determine when th
 
 Before mapping fields, you’ll define a trigger that determines when the mapping executes. For Engage events, triggers typically use the audience key's boolean value. 
 
-So to trigger the mapping when a user enters or exits an audience, you'd use the audience key and its boolean value:
-
 When a user enters the audience, configure the trigger like this:
 
 - Trigger type: `Event Trait`
@@ -190,7 +178,7 @@ This tells Segment to execute the mapping only when the value of the audience ke
 
 The fields you map depend on whether you selected Identify or Track. 
 
-#### Map an Identify event 
+#### 3a. Map an Identify event 
 
 Since Identify events send data in the `traits` object, you'll use `traits` in your mappings, like in this example:
 
@@ -220,7 +208,7 @@ Here’s how you might configure your mapping for this Identify event:
 
 <!-- Maybe add screenshot-->
 
-#### Map a Track event
+#### 3b. Map a Track event
 
 Track events send data in the `properties` object, like in this example:
 
@@ -264,7 +252,7 @@ Once you've decided whether to map a Track or Identify event, finish by followin
 
 ## Trait enrichment
 
-Trait Enrichment lets you pull Segment profile traits into mappings when syncing audiences or journeys to destinations and [Destination functions](/docs/connections/functions/destination-functions/).
+Trait enrichment lets you pull Segment profile traits into mappings when syncing audiences or journeys to destinations and [Destination functions](/docs/connections/functions/destination-functions/).
 
 To enable trait enrichment: