From 0666f036abeb4787bd294bfb543ae5efa65a05bb Mon Sep 17 00:00:00 2001
From: bobbyatsegment <93934274+bobbyatsegment@users.noreply.github.com>
Date: Fri, 17 Nov 2023 10:18:15 -0500
Subject: [PATCH 1/2] Add note on using transformations with filters

---
 src/connections/destinations/destination-filters.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md
index 034ff61f6b..ad4e59ddac 100644
--- a/src/connections/destinations/destination-filters.md
+++ b/src/connections/destinations/destination-filters.md
@@ -229,7 +229,6 @@ Use the destination filter tester during setup to verify that you're filtering o
 
 Destination Filters can't target properties or traits with spaces in the field name. As an alternative, use [Insert Functions](/docs/connections/functions/insert-functions/), which let you write code to take care of such filtering.
 
-
 #### Can I use destination filters to drop events unsupported by a destination?
 
 The check for unsupported events types happens before any destination filter checks. As a result, Destination Filters can't prevent unsupported event type errors. To filter these events, use the [Integrations Object](/docs/guides/filtering-data/#filtering-with-the-integrations-object).
@@ -239,3 +238,7 @@ The check for unsupported events types happens before any destination filter che
 Destination filters only filter events sent after filter setup. If you just added a destination filter but still see some events going through, you're likely seeing retries from failed events that occurred before you set up the filter.
 
 When Segment sends an event to a destination but encounters a timeout error, it attempts to send the event again. As a result, if you add a destination filter while Segment is trying to send a failed event, these retries could filter through, since they reflect events that occurred before filter setup.
+
+#### How are Protocols Transformations handled by destination filters?
+
+Events are first processed by a destination filter when a destination-specific Transformation is enabled. In contrast, for source-level Transformations, the transformation is applied to the events _before_ they reach the destination filter.

From 5598cc531d89c94c91484a805bbb4abfd10dd636 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Mon, 20 Nov 2023 17:56:50 -0500
Subject: [PATCH 2/2] Update
 src/connections/destinations/destination-filters.md

---
 src/connections/destinations/destination-filters.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md
index ad4e59ddac..3098d69610 100644
--- a/src/connections/destinations/destination-filters.md
+++ b/src/connections/destinations/destination-filters.md
@@ -239,6 +239,6 @@ Destination filters only filter events sent after filter setup. If you just adde
 
 When Segment sends an event to a destination but encounters a timeout error, it attempts to send the event again. As a result, if you add a destination filter while Segment is trying to send a failed event, these retries could filter through, since they reflect events that occurred before filter setup.
 
-#### How are Protocols Transformations handled by destination filters?
+#### How do destination filters handle Protocols Transformations?
 
-Events are first processed by a destination filter when a destination-specific Transformation is enabled. In contrast, for source-level Transformations, the transformation is applied to the events _before_ they reach the destination filter.
+When you enable a destination-specific Transformation, Segment processes your events with a destination filter. Segment processes source-level Transformations before the events reach the destination filter.