Skip to content

Commit c679e97

Browse files
author
irinasayshi
authored
Update forward-violations.md
1 parent 9085af8 commit c679e97

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/protocols/validate/forward-violations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: Forward Violations
55
{% include content/plan-grid.md name="protocols" %}
66

77

8-
You can forward Violations (data that does not conform to your Protocols tracking plan) to a Segment Source to enable custom notifications, dashboards and further analysis in any Segment destination that accepts cloud-mode data. To set up forwarding, visit your Source settings tab and select which Source you want to forward events to from the dropdown. Similar to [Blocked Event forwarding](/docs/protocols/enforce/forward-blocked-events/), we recommend that you create a new Source for violations.
8+
You can forward Violations (data that does not conform to your Protocols tracking plan) to a Segment Source to enable custom notifications, dashboards and further analysis in any Segment destination that accepts cloud-mode data. To set up forwarding, visit your Source settings tab, then the Schema Configuration setting. Select which source you want to forward events to from the Forwarding Settings Violations dropdown. Similar to [Blocked Event forwarding](/docs/protocols/enforce/forward-blocked-events/), we recommend that you create a new Source for violations.
99

1010
![](../images/violation_forwarding.png)
1111

0 commit comments

Comments
 (0)