You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/_data/protocols.yml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ sections:
6
6
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."
7
7
path: /protocols/tracking-plan/best-practices/
8
8
- name: 2. Validate data quality with violations
9
-
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."
9
+
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."
10
10
path: /protocols/validate/connect-sources/
11
11
- name: 3. Enforce data standards with controls
12
12
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."
13
13
path: /protocols/enforce/schema-configuration/
14
14
- name: 4. Resolve data issues with transformations
15
-
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."
15
+
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."
16
16
path: /protocols/transform/
17
17
18
18
- section_title: Learn more
@@ -25,5 +25,5 @@ sections:
25
25
description: "Create a Tracking Plan to standardize your collected data."
26
26
path: /protocols/tracking-plan/create/
27
27
- name: FAQ
28
-
description: "Get answers to Protocols questions that come up the most."
28
+
description: "Get answers to frequent Protocols questions."
0 commit comments