Skip to contentSkip to navigationSkip to topbar
Twilio Segment Docs
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Forward Blocked Events

FREE x
TEAM x
BUSINESS ✓
ADDON ✓

If you're concerned about permanently discarding blocked events, you can enable blocked event forwarding on a Segment Source. To set up forwarding, navigate to the settings tab of the Source, then Schema Configuration.

Select the source to forward events to from the Blocked Events and Traits dropdown. Segment recommends that you create a new Source for forwarded events to avoid contaminating production data and enable blocking only when you are confident about the quality of your data.

Since forwarding happens server to server, Segment recommends creating a HTTP Tracking API source, though any server-side source will work.

A screenshot of the blocked events and traits section on the Schema Configuration settings page.
(information)

Blocked events and MTUs

Only blocked events are forwarded to the source, and count toward your MTU limits. Events with omitted traits are not forwarded, and do not contribute to your MTU counts. Instead, Segment inserts a context.protocols object into the event payload which contains the omitted properties or traits.