Segment Protocols Blocking Events
Quick answer
Protocols can discard events that violate your tracking plan, and by default blocked events cannot be replayed; forward them to a quarantine source before enabling blocking.
Most likely fix: Review violations first
How to fix it
Try these in order — the most common fix is first.
1. Review violations first
- Open Protocols > Tracking Plans > Violations
- Fix event names and property types
Did this fix it?2. Forward blocked events
- In schema controls, forward blocked events to a separate quarantine source
Did this fix it?3. Switch to omit mode if needed
- Use omit or allow instead of block for non-critical properties
Did this fix it?4. Remember device-mode
- Device-mode destinations are not blocked, which can cause mismatches
Did this fix it?
Symptoms
Events vanish from all destinations after enabling schema controls.
Why it happens
- Blocking enabled on a source with violations
- Event or property names differ from the tracking plan
- Blocked events discarded by default
This guide also covers
- segment protocols blocked events
- segment tracking plan violations
- segment schema controls
Still not working?
If Segment keeps failing, you're not alone. See every Segment problem users report or the alternatives people switch to.
Done fighting Segment? Our small team builds your own Segment alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us