Skip to content

Commit 40ffd95

Browse files
Add link to schema limits FAQ
1 parent 4b02f23 commit 40ffd95

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/connections/destination-data-control.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ Once you have enabled Destinations for a given Source, all of the [data](/docs/c
66

77
But what happens when you want to send all of your data to a warehouse, and only two specific events to an analytics tool? And once you're satisfied with your spec, how do you make sure rogue events are blocked from all of your warehouses and end tools? Segment gives you the power to control exactly what data is allowed into your Destinations, so you can protect the integrity of your data, and the decisions you make with it.
88

9+
910
## How do I filter specific events from being sent to specific Destinations?
1011

1112
An `integrations object` may be passed in the `options` of  `group`, `identify`, `page` and `track` methods, allowing selective Destination filtering. By default all Destinations are enabled.
@@ -74,3 +75,7 @@ The Identify & Group CSV file contains the following columns:
7475

7576
> note ""
7677
> Export Schema doesn't include any actual values (for example, personal data) for the events, properties, and traits you are tracking for a specific source.
78+
79+
80+
81+
For more information on how to manage the Source Schema page, please visit [this page](https://segment.com/docs/connections/schema-unique-limits/)

0 commit comments

Comments
 (0)