Multiple Only Send Filters

Author: rchinn1

src/connections/destinations/destination-filters.md

@@ -25,7 +25,7 @@ Keep the following limitations in mind when you use Destination Filters:
 - 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/) if these limitations impact your use case.
+[Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 
 ## Create a Destination Filter
 
@@ -53,7 +53,7 @@ The Destination Filters API offers four different filter types:
 | `whitelist_fields` | Only send whitelisted properties to the destination.         |
 | `blocklist_fields` | Don't send blocklisted properties to the destination.        |
 
-To learn more, read Segment's [Destination Filters API docs](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5).
+To learn more, read Segment's [Destination Filters API docs](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5){:target="_blank"}.
 
 ## Examples
 
@@ -66,37 +66,37 @@ Example: Remove email addresses from `context` and `properties`:
 Property-level allowlisting is available with Segment's API. Using Destination Filters, you can configure a rule that removes email addresses from `context` and `properties`. As a result, Segment only sends traits without PII to the destination.
 
 
-![](images/destination-filters/pii_example.png)
+![PII management example](images/destination-filters/pii_example.png)
 
 ### Control Event Volume
 
 This example shows a filter that controls event volume by only sending `User Signed Up` and `Demo Requested` events.
 
-![](images/destination-filters/drop_example.png)
+![Example of a filter that controls event volume](images/destination-filters/drop_example.png)
 
 ### Cleaner Data
 
 This example shows a rule that only sends track calls to Google Analytics.
 
-![](images/destination-filters/clean_example.png)
+![Example of a filter that only sends track calls to Google Analytics](images/destination-filters/clean_example.png)
 
 ### Remove Internal and Test Events From Production Tools
 
 This rule targets email addresses with internal domains to stop test events from reaching Destinations.
 
-![](images/destination-filters/internal_example.png)
+![Example of a filter that removes internal and test events from production tools](images/destination-filters/internal_example.png)
 
 This rule prevents an event from sending if `Order Completed` and `properties.email` contain an internal `@segment.com` email address.
 
-![](images/destination-filters/internal_example2.png)
+![Internal domain filter example](images/destination-filters/internal_example2.png)
 
 ### Sample a Percentage of Events
 
-Using the [Destination Filters API](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5), you can create a rule to randomly sample video heartbeat events.
+Using the [Destination Filters API](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
 
 ### Drop Events
 
-[Watch this Destination Filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco) to learn how to use event names to filter events sent to destinations.
+[Watch this Destination Filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco){:target="_blank"} to learn how to use event names to filter events sent to destinations.
 
 ## Important Notes
 
@@ -108,27 +108,31 @@ In the example in the video above, if you have a Destination Filter that filters
 
 **Error handling**
 
-Segment makes effort to ensure that destination filters handle unexpected situations. For example, if you use the `contains()` FQL function on `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
+Segment makes effort to ensure that Destination Filters handle unexpected situations. For example, if you use the `contains()` FQL function on `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
 
-Errors aren't exposed in your Destination's Event Deliverability tab. For help diagnosing missing destination filter events, [contact Segment](https://segment.com/help/contact/).
+Errors aren't exposed in your Destination's Event Deliverability tab. For help diagnosing missing destination filter events, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
 ## FAQ
 
 **How do Destination Filters work with array properties?**
 
-Destination filters can filter properties out of objects nested in an array. For example, you can filter out the `price` property of every object in an array at `properties.products`. You can also filter out an entire array from the payload. However, you can't drop nested objects in an array or filter properties out of a single object in an array.
+Destination Filters can filter properties out of objects nested in an array. For example, you can filter out the `price` property of every object in an array at `properties.products`. You can also filter out an entire array from the payload. However, you can't drop nested objects in an array or filter properties out of a single object in an array.
 
 To block a specific property from all of the objects within a properties array, set the filter using the following the format: `<propertyType>.<arrayName>.<arrayElementLabel>​`.
 
 For example, the `properties.products.newElement` filter blocks all `newElement` property fields from each `products` object of an array within the `properties` object of a Track event.
 
-![](images/destination-filters/filter-array-properties.png)
+![Filter array properties](images/destination-filters/filter-array-properties.png)
 
 To block the Identify event trait `products.newElement`, select the option under the **User Traits** list instead. To block a context object field `products.newElement`, select it from the **Context Fields** list.
 
 **How many filters can I create?**
 
-Segment supports 10 filters per destination. If you need help consolidating filters or would like to discuss your use case, [contact Segment](https://segment.com/help/contact/).
+Segment supports 10 filters per destination. If you need help consolidating filters or would like to discuss your use case, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
+
+**Can I set multiple `Only Send` Destination Filters?**
+
+Segment evaluates multiple `Only Send` filters against each other and resolves Destination Filters in order. If multiple `Only Send` filters conflict with each other, Segment won't send information downstream.
 
 **How many properties can I view in the filter dropdown?**