Skip to contentSkip to navigationSkip to topbar
Twilio Segment Docs
On this page
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.

Protocols Overview

FREE x
TEAM x
BUSINESS ✓
ADDON ✓
(information)

Info

Protocols is only available for event stream (website, mobile, and server sources) and Engage sources.

Segment helps customers collect and integrate customer data across a wide range of business tools. To do so reliably, the data Segment receives must be clean, consistent and adhere to a clear, consistent tracking plan.

Protocols was built to automate and scale the data quality best practices developed over years of helping customers implement Segment. Investing in data quality improves trust in your data, reduces time spent by your engineering and business teams navigating and validating data, and ultimately, allows your business to grow faster.

(information)

Protocols is a premium add-on feature available to Business Tier customers

If your plan includes Protocols, you can access it from the protocols path in your workspace(link takes you to an external page). If your plan doesn't include Protocols, contact your Segment account executive.

There are four steps to using Protocols

there-are-four-steps-to-using-protocols page anchor

There are four steps to using Protocols:

  1. Align teams with a Tracking Plan: Good data quality starts with a well thought out Tracking Plan. With Protocols, you can define your events and corresponding properties in a Tracking Plan. This tracking plan becomes a central source of truth for product, engineering, analytics, and business teams.
  2. Validate data quality with violations: With your tracking plan living in Segment, you can apply it to one or more data sources. Any event or property that does not match the tracking plan will generate a violation. Violations are displayed in aggregated form to spot trends, and detailed form to help you quickly find and resolve discrepancies.
  3. Enforce data standards with controls: To maintain a high degree of quality over time, we offer strict controls to block non-conforming events. Blocked events can be forwarded to a separate quarantined Segment source for analysis and review.
  4. Resolve data issues with transformations: Even the most exacting data collection processes are subject to human error and organizational complexity. Apply Transformations within Protocols to change event and property names without touching code.

Learn more

learn-more page anchor
  • Best practices: Learn more about tracking plans and why you need them.
  • Tracking Plan: Create a Tracking Plan to standardize your collected data.
  • FAQ: Get answers to frequent Protocols questions.