Skip to content

Commit cf9b4c6

Browse files
Merge pull request #7389 from segmentio/fix-5469
Add note to Protocols FAQ about mobile device mode destinations
2 parents f4c97dc + 9be3ba9 commit cf9b4c6

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

src/protocols/faq.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,9 +144,13 @@ The schema functionality is a _reactive_ way to clean up your data, where the Tr
144144

145145
That being said, there are plenty of scenarios where the reactive Schema functionality solves immediate needs for customers. Often times, customers will use both Schema Controls and Tracking Plan functionality across their Segment Sources. For smaller volume Sources with less important data, the Schema functionality often works perfectly.
146146

147-
### If I enable blocking, what happens to the blocked events? Are events just blocked from specific Destinations or the entire Segment pipeline?
147+
### If I enable blocking are events just blocked from specific Destinations or the entire Segment pipeline?
148148

149-
Blocked events are blocked from sending to all Segment Destinations, including warehouses and streaming Destinations. When an Event is blocked using a Tracking Plan, it does not count towards your MTU limit. They will, however, count toward your MTU limit if you enable [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) in your Source settings.
149+
Segment can block events from all Segment Destinations except for mobile device mode destinations.
150+
151+
Events that are delivered from a mobile source in device mode bypass the point in the Segment pipeline where Segment blocks events, so mobile events sent using device mode are not blocked and are delivered to your Destinations. If you are a Business Tier customer using Segment's [Swift](/docs/connections/sources/catalog/libraries/mobile/apple/) or [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/) SDKs, you can use [destination filters](/docs/connections/destinations/destination-filters/) to block events.
152+
153+
When an event is blocked using a Tracking Plan, it does not count towards your MTU limit. If you use [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/), blocked events forwarded to a new source will count toward your MTU limit.
150154

151155
### If I omit unplanned properties or properties that generate JSON schema violations, what happens to them?
152156

0 commit comments

Comments
 (0)