Skip to content

Commit b8246dd

Browse files
authored
fix formatting (#540)
1 parent 6439cf9 commit b8246dd

File tree

1 file changed

+11
-19
lines changed

1 file changed

+11
-19
lines changed

src/connections/destinations/destination-filters.md

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,26 +7,21 @@ Destination Filters allow you to control the data flowing into each specific des
77

88
With Destination Filters, you can:
99

10-
- Control your event volume by sampling or dropping unnecessary events for
11-
specific destinations.
10+
- Control your event volume by sampling or dropping unnecessary events for
11+
specific destinations.
12+
- Manage PII (personally identifiable information) by blocking fields from
13+
reaching certain destinations.
14+
- Increase the relevance of the data in your destinations by removing unused or unwanted data.
15+
- Prevent test or internally-generated events from reaching your production tools.
1216

13-
- Manage PII (personally identifiable information) by blocking fields from
14-
reaching certain destinations.
15-
16-
- Increase the relevance of the data in your destinations by removing unused or unwanted data.
17-
18-
- Prevent test or internally-generated events from reaching your production tools.
19-
20-
> note ""
21-
> **Note**: Destination Filters are currently available to Business Tier customers only.
17+
> note ""
18+
> **Note**: Destination Filters are currently available to Business Tier customers only.
2219
2320
### Destination Filtering Limitations
2421

25-
* Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported.
26-
27-
* You cannot apply Destination Filters to Warehouses or S3 destinations.
28-
29-
* Each filter can only apply to one source-destination pair.
22+
- Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported.
23+
- You cannot apply Destination Filters to Warehouses or S3 destinations.
24+
- Each filter can only apply to one source-destination pair.
3025

3126
If you have a compelling use case for these unsupported options, [contact us](https://segment.com/help/contact/).
3227

@@ -39,12 +34,9 @@ that are conditionally applied using Segment's "Filter Query Language" (FQL).
3934
The Destination Filters API offers four different types of filters:
4035

4136
1. **drop_event**: Do not send matched event to the destination.
42-
4337
2. **sample_event**: Send only a percentage of events through to the
4438
destination.
45-
4639
3. **whitelist_fields**: Only send whitelisted properties to destination.
47-
4840
4. **blacklist_fields**: Do not send blacklisted properties to destination.
4941

5042
Read more in the [Destination Filters API docs](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5).

0 commit comments

Comments
 (0)