Skip to content

Warehouse Schema and Protocols Overview review #7938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Warehouse Schema and Protocols Overview review #7938

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fc2c042
Warehouse Schema review
forstisabella Sep 11, 2025
81fd21d
protocols overview review
forstisabella Sep 12, 2025
ccc6012
signposts
forstisabella Sep 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/_data/protocols.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ sections:
description: "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."
path: /protocols/tracking-plan/best-practices/
- name: 2. Validate data quality with violations
description: "With your tracking plan living in Segment, you can apply it to 1 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."
description: "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."
path: /protocols/validate/connect-sources/
- name: 3. Enforce data standards with controls
description: "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."
path: /protocols/enforce/schema-configuration/
- name: 4. Resolve data issues with transformations
description: "Even the most exacting data collection processes are subject to human error and organizational complexity. Transformations can be applied from within Protocols to change event and property names without touching code."
description: "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."
path: /protocols/transform/

- section_title: Learn more
Expand All @@ -25,5 +25,5 @@ sections:
description: "Create a Tracking Plan to standardize your collected data."
path: /protocols/tracking-plan/create/
- name: FAQ
description: "Get answers to Protocols questions that come up the most."
description: "Get answers to frequent Protocols questions."
path: /protocols/faq/
Loading