You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/destination-filters.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Common use cases for destination filters include:
22
22
23
23
Keep the following limitations in mind when you use destination filters:
24
24
25
+
- Destination Filters aren't applied to events sent through the Event Tester.
25
26
- Segment applies destination filters one at a time in the order that they appear in your workspace.
26
27
- You can't apply destination filters to Warehouses or S3 destinations.
27
28
- Each filter can only apply to one source-destination pair.
@@ -31,8 +32,6 @@ Keep the following limitations in mind when you use destination filters:
31
32
-*(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to**Settings > Analytics.js** and turn the toggle on for**Destination Filters**.
32
33
-*(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source.
33
34
-*(For mobile device-mode)* Destination filters for mobile device-mode doesn't support iOS and Android libraries.
34
-
- Destination Filters don't apply to events that send through the destination Event Tester.
35
-
36
35
37
36
[Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.