Skip to content

fix formatting #540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 22, 2020
Merged

fix formatting #540

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 11 additions & 19 deletions src/connections/destinations/destination-filters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,26 +7,21 @@ Destination Filters allow you to control the data flowing into each specific des

With Destination Filters, you can:

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

- Manage PII (personally identifiable information) by blocking fields from
reaching certain destinations.

- Increase the relevance of the data in your destinations by removing unused or unwanted data.

- Prevent test or internally-generated events from reaching your production tools.

> note ""
> **Note**: Destination Filters are currently available to Business Tier customers only.
> note ""
> **Note**: Destination Filters are currently available to Business Tier customers only.

### Destination Filtering Limitations

* Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported.

* You cannot apply Destination Filters to Warehouses or S3 destinations.

* Each filter can only apply to one source-destination pair.
- Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported.
- You cannot apply Destination Filters to Warehouses or S3 destinations.
- Each filter can only apply to one source-destination pair.

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

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

1. **drop_event**: Do not send matched event to the destination.

2. **sample_event**: Send only a percentage of events through to the
destination.

3. **whitelist_fields**: Only send whitelisted properties to destination.

4. **blacklist_fields**: Do not send blacklisted properties to destination.

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