From b7b9b9288cf5c6958393fd2f544f3c8385c23c59 Mon Sep 17 00:00:00 2001 From: Samantha Crespo <100810716+samkcrespo@users.noreply.github.com> Date: Tue, 9 Apr 2024 15:05:56 -0700 Subject: [PATCH 1/2] Update destination-filters.md --- src/connections/destinations/destination-filters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md index bbe91950f5..09dba21cd5 100644 --- a/src/connections/destinations/destination-filters.md +++ b/src/connections/destinations/destination-filters.md @@ -23,7 +23,7 @@ Common use cases for destination filters include: Keep the following limitations in mind when you use destination filters: - Destination Filters aren't applied to events sent through the Event Tester. -- Segment applies destination filters one at a time in the order that they appear in your workspace. +- Segment applies destination filters in the following order: Sample, Drop ('Only Sends' are Drops), Drop Properties, Allow Properties - You can't apply destination filters to Warehouses or S3 destinations. - Each filter can only apply to one source-destination pair. - *(For device-mode)* Destination filters don't apply to items that are added to the payload server-side such as IP addresses. From 4b291730acb8fa12cdaf23270c33d759905c2d80 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Tue, 20 Aug 2024 09:39:16 -0700 Subject: [PATCH 2/2] Update src/connections/destinations/destination-filters.md --- src/connections/destinations/destination-filters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md index 09dba21cd5..fedc86b6c4 100644 --- a/src/connections/destinations/destination-filters.md +++ b/src/connections/destinations/destination-filters.md @@ -23,7 +23,7 @@ Common use cases for destination filters include: Keep the following limitations in mind when you use destination filters: - Destination Filters aren't applied to events sent through the Event Tester. -- Segment applies destination filters in the following order: Sample, Drop ('Only Sends' are Drops), Drop Properties, Allow Properties +- Segment applies destination filters in the following order: Sample, Drop ('Only Sends' are Drops), Drop Properties, Allow Properties. - You can't apply destination filters to Warehouses or S3 destinations. - Each filter can only apply to one source-destination pair. - *(For device-mode)* Destination filters don't apply to items that are added to the payload server-side such as IP addresses.