Skip to content

Commit 1bc114d

Browse files
committed
More DOC-434 updates
1 parent b363c90 commit 1bc114d

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

src/connections/destinations/destination-filters.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,8 @@ Using Destination Filters, you can conditionally filter out event properties, tr
99

1010
Common use cases for Destination Filters include the following:
1111

12-
- Managing PII (personally identifiable information) by blocking fields from
13-
reaching certain destinations
14-
- Controlling event volume by sampling or dropping unnecessary events for
15-
specific destinations
12+
- Managing PII (personally identifiable information) by blocking fields from reaching certain destinations
13+
- Controlling event volume by sampling or dropping unnecessary events for specific destinations
1614
- Increasing data relevance in your destinations by removing unused or unwanted data
1715
- Preventing test or internally-generated events from reaching your production tools
1816

@@ -116,7 +114,7 @@ Errors aren't exposed in your Destination's Event Deliverability tab. For help d
116114

117115
## FAQ
118116

119-
**How do destination filters work with array properties?**
117+
**How do Destination Filters work with array properties?**
120118

121119
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.
122120

0 commit comments

Comments
 (0)