[netlify-build]

Author: stayseesong

src/connections/destinations/destination-filters.md

@@ -28,6 +28,8 @@ Keep the following limitations in mind when you use Destination Filters:
 - Segment applies Destination Filters one at a time in the order that they appear in your workspace.
 - 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.
+- *(For device-mode)* Destination filters don't filter on native events that the destination SDK collects. Instead, you can use the load option to conditionally load relevant bundled JavaScript on the page. See the docs for [load options](/docs/connections/sources/catalog/libraries/website/javascript/#load-options).
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 

src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md

@@ -352,7 +352,8 @@ The example projects contain sample [plugins](https://github.com/segmentio/analy
 Use Analytics Kotlin (Android) to configure [destination filters](docs/connections/destinations/destination-filters/) on your mobile device-mode destinations.
 
 > warning ""
-> When you use destination filters in mobile device-mode, certain fields that are added to the payload server-side such as an IP address, aren't supported. Segment ignores these filters.
+> Keep [these limitations](/docs/connections/destinations/destination-filters/#limitations) in mind when using destination filters.
+
 
 To get started with destination filters on mobile device-mode destinations using Kotlin:
 

src/connections/sources/catalog/libraries/mobile/swift-ios/index.md

@@ -342,7 +342,7 @@ Though you can add plugins anywhere in your code, it's best to implement your pl
 Use Analytics Swift to set up [destination filters](docs/connections/destinations/destination-filters/) on your mobile device-mode destinations.
 
 > warning ""
-> When you use destination filters in mobile device-mode, certain fields that are added to the payload server-side such as an IP address, aren't supported. Segment ignores these filters.
+> Keep [these limitations](/docs/connections/destinations/destination-filters/#limitations) in mind when using destination filters.
 
 To get started with destination filters using Swift:
 1. Add the Swift package `git@github.com:segmentio/DestinationFilters-Swift.git` as a dependency through either of these 2 options:

src/guides/filtering-data.md

@@ -45,7 +45,7 @@ Your data is sent to your warehouse (if you have one) and into the Segment backe
 
 ## Destination filters
 
-[Destination filters](https://segment.com/docs/connections/destinations/destination-filters/) allow you to control the data flowing into each specific destination, by examining event payloads, and conditionally preventing data from being sent to destinations. You can filter out entire events, or just specific fields in the properties, in the traits, or in the context of your events. Destination filters support cloud-based (server-side), actions-based, and mobile and web device-mode destinations.  Destination filters aren't available for, and don't prevent data from reaching your warehouse(s) or S3 destinations.
+[Destination filters](https://segment.com/docs/connections/destinations/destination-filters/) allow you to control the data flowing into each specific destination, by examining event payloads, and conditionally preventing data from being sent to destinations. You can filter out entire events, or just specific fields in the properties, in the traits, or in the context of your events. Destination filters support cloud-based (server-side), actions-based, and mobile and web device-mode destinations.  Destination filters aren't available for, and don't prevent data from reaching your warehouse(s) or S3 destinations. Keep [these limitations](/docs/connections/destinations/destination-filters/#limitations) in mind when using destination filters.
 
 > info ""
 > Destination filters are only available in workspaces that are on a Business Tier plan.