From f0b4da45f09cd18efcfdde7b23ee888f505f2759 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Mon, 14 Oct 2024 16:17:00 -0400
Subject: [PATCH 1/3] linked events obs

---
 src/unify/data-graph/linked-events.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/src/unify/data-graph/linked-events.md b/src/unify/data-graph/linked-events.md
index 77b8a41968..b7a46805fb 100644
--- a/src/unify/data-graph/linked-events.md
+++ b/src/unify/data-graph/linked-events.md
@@ -178,13 +178,23 @@ In the Mappings tab, locate the **Select Mappings** section where you can enrich
 > warning ""
 > At this time, Linked Events doesn't support a preview of enriched payloads.
 
-### Save your Enrichments
+### Save your enrichments
 
 When you're satisfied with the mappings, click **Save**. Segment returns you to the Mappings table.
 
 > warning ""
 > At this time, when you select mappings or test events, you won’t see enrichment data. Enrichment data is only available with real events.
 
+## Enrichment observability
+
+To verify which of your events matched one or more enrichments:
+1. Navigate to [Delivery Overview](/docs/connections/delivery-overview/#actions-destinations) for your connected destination. 
+2. Select the **Successfully received** step in the pipeline view.
+3. Select the **Events enriched** tab. This table breaks down events into the following categories: 
+     - **Successfully enriched**: Events that were enriched by all entities
+     - **Partially enriched**: Events that were only enriched by only some of your entities
+     - **Unenriched events**: Events that did not match any entities
+
 ## FAQs
 
 #### What data warehouse permissions does Segment require? 

From b3e38221ca0ded57588bc92100bf94b30fb70305 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Mon, 14 Oct 2024 16:19:10 -0400
Subject: [PATCH 2/3] [netlify-build]

---
 src/unify/data-graph/linked-events.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/unify/data-graph/linked-events.md b/src/unify/data-graph/linked-events.md
index b7a46805fb..2e611f2e90 100644
--- a/src/unify/data-graph/linked-events.md
+++ b/src/unify/data-graph/linked-events.md
@@ -235,3 +235,4 @@ entity "account-entity" {
      enrichment_enabled = true
 }
 ```
+

From de5ed1fe26be80e12d9bedae2c80a8c47d2129f1 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Mon, 14 Oct 2024 16:50:47 -0400
Subject: [PATCH 3/3] add context re filtering to Actions DO

---
 src/connections/delivery-overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md
index 8bfde19626..6a1604016a 100644
--- a/src/connections/delivery-overview.md
+++ b/src/connections/delivery-overview.md
@@ -34,7 +34,7 @@ The pipeline view for classic destinations includes the following steps:
 
 #### Actions destinations
 The pipeline view for Actions destination includes the following steps: 
-- **Successfully received**: Events that Segment ingested from your source.
+- **Successfully received**: Events that Segment ingested from your source. You can filter these events by event type, event name, app version, and [enrichment status](/docs/unify/data-graph/linked-events/).
 - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules.
 - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans.
 - **Mapping dropdown**: Select a [mapping](/docs/connections/destinations/actions/#customize-mappings) to filter the events in the Filtered at destination, Failed delivery and Successful delivery pipeline steps.