destination filters [netlify-build]

Author: stayseesong

src/connections/destinations/destination-filters.md

@@ -3,30 +3,30 @@ title: Destination Filters
 rewrite: true
 ---
 
-Use Destination Filters to prevent certain data from flowing into a destination. With Destination Filters, you can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
+> info ""
+> Destination filters are only available to Business Tier customers.
+
+Use destination filters to prevent certain data from flowing into a destination. You can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
+
+You can configure destination filters on cloud-mode destinations as well as on mobile and web device-mode destinations.  With device-mode destinations, you can use the same user interface or API mechanism that you use for your cloud-mode destinations, and have those filters acted upon for device-mode destinations on web and mobile.
 
-Common use cases for Destination Filters include:
+Common use cases for destination filters include:
 - Managing PII (personally identifiable information) by blocking fields from reaching certain destinations
 - Controlling event volume by sampling or dropping unnecessary events for specific destinations
 - Increasing data relevance in your destinations by removing unused or unwanted data
 - Preventing test or internally-generated events from reaching your production tools
 
-> info ""
-> Destination Filters are only available to Business Tier customers.
-
 ### Limitations
 
 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.
-- Destination Filters can only be applied to cloud-mode (server-side) streaming destinations.
-- Device-mode destinations aren't supported.
 - You can't apply Destination Filters to Warehouses or S3 destinations.
 - Each filter can only apply to one source-destination pair.
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 
-## Create a Destination Filter
+## Create a destination filter
 
 To create a Destination Filter:
 1. Go to **Connections > Destinations** and select your destination.
@@ -38,7 +38,7 @@ To create a Destination Filter:
 7. Name your filter and click the toggle to enable it.
 8. Click **Save**.
 
-## Destination Filters API
+## Destination filters API
 
 The Destination Filters API provides more power than Segment's dashboard Destination Filters settings. With the API, you can create complex filters that are conditionally applied using Segment's [Filter Query Language (FQL)](/docs/api/config-api/fql/).
 

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

@@ -340,8 +340,26 @@ analytics.add(yourPlugin)
 ```
 
 ### Example projects using Analytics-Kotlin
-See how different platforms and languages use Analytics-Kotlin in different [example projects](https://github.com/segmentio/analytics-kotlin/tree/main/samples).
-The example projects contain sample [plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins) and [destination plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins) you can utilize.
+See how different platforms and languages use Analytics-Kotlin in different [example projects](https://github.com/segmentio/analytics-kotlin/tree/main/samples){:target="_blank"}.
+The example projects contain sample [plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins){:target="_blank"} and [destination plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins){:target="_blank"} you can utilize.
+
+## Destination filters
+> info ""
+> Destination filters are only available to Business Tier customers.
+
+You can set up [destination filters](docs/connections/destinations/destination-filters/) on your mobile device-mode destinations by using Analytics Kotlin (Android). 
+
+To get started with destination filters on mobile device-mode destinations using Kotlin:
+
+1. Download and install the dependency.
+  ```java
+    implementation 'com.segment.analytics.kotlin:destination-filters-kotlin:x.x.x'
+  ```
+
+2. Add the plugin.
+  ```java
+    analytics.add(DestinationFilters())
+  ```
 
 ## Utility methods
 The Analytics-Kotlin utility methods help you work with plugins from the analytics timeline. They include:

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

@@ -13,7 +13,7 @@ If you're migrating to Analytics-Swift from a different mobile library, you can
 > Analytics-Swift currently supports [these destinations](#supported-destinations) in device-mode, with more to follow. Cloud-mode destinations are also supported.
 
 
-## Getting Started
+## Getting started
 To get started with the Analytics-Swift mobile library:
 
 1. Create a Source in Segment.
@@ -62,7 +62,7 @@ To get started with the Analytics-Swift mobile library:
     > info ""
     > Configuration options such as IDFA collection and automatic screen tracking are found in Segment's [Plugin Examples repo](https://github.com/segmentio/analytics-example-plugins/tree/main/plugins/swift){:target="_blank"}.
 
-## Tracking Methods
+## Tracking methods
 Once you've installed the Analytics-Swift library, you can start collecting data through Segment's tracking methods:
 - [Identify](#identify)
 - [Track](#track)
@@ -204,7 +204,7 @@ analytics.alias(newId: "user-123")
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-## Plugin Architecture
+## Plugin architecture
 Segment's plugin architecture enables you to modify and augment how the analytics client works. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.
 
 Plugins are run through a timeline, which executes in order of insertion based on their entry types. Segment has these 5 entry types:
@@ -333,7 +333,26 @@ analytics.add(plugin: yourIntegration)
 
 Though you can add plugins anywhere in your code, it's best to implement your plugin when you configure the client.
 
-## Utility Methods
+## Destination filters
+> info ""
+> Destination filters are only available to Business Tier customers.
+
+You can set up [destination filters](docs/connections/destinations/destination-filters/) on your mobile device-mode destinations by using Analytics Swift.
+
+To get started with destination filters using Swift:
+1. Add the plugin dependency to your application by adding the Swift package `git@github.com:segmentio/DestinationFilters-Swift.git` as a dependency through either of these 2 options:
+    1. Your package.swift file
+    2. Xcode
+        1. Xcode 12: **File > Swift Packages > Add Package Dependency**
+        2. Xcode 13: **File > Add Packages...**
+
+    After installing the package, you can reference the Destination Filters plugin by importing the package with `import DestinationFilters_Swift`.
+2. Add the plugin.
+```swift
+analytics.add(DestinationFilters())
+```
+
+## Utility methods
 The Analytics Swift utility methods help you work with [plugins](#plugin-architecture) from the analytics timeline. They include:
 - [Add](#add)
 - [Find](#find)
@@ -419,7 +438,7 @@ let idfaPlugin = IDFACollection()
 analytics.add(plugin: idfaPlugin)
 ```
 
-## Supported Destinations
+## Supported destinations
 Segment supports these destinations for Analytics Swift, with more to come:
 * [Amplitude](https://github.com/segment-integrations/analytics-swift-amplitude)
 * [Appsflyer](https://github.com/segment-integrations/analytics-swift-appsflyer)