Skip to content

Commit e91abae

Browse files
committed
fix notes, remove 'we' [netlify-ignore]
1 parent addd30e commit e91abae

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

src/protocols/enforce/forward-blocked-events.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,14 @@ title: Forward blocked events
44
{% include content/plan-grid.md name="protocols" %}
55

66

7-
If you're concerned about permanently discarding blocked events, you can enable blocked event forwarding to a Segment Source. 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 Blocked Events and Traits dropdown. We recommend creating a new Source for forwarded events to avoid contaminating production data. We recommend only enabling blocking when you feel confident about the quality of your data.
7+
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.
8+
9+
Select the source you'll 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.
810

911
![](../images/blocked_event_forwarding.png)
1012

11-
**Note: Only blocked events are forwarded to the source. Events with omitted traits are not forwarded. Instead, Segment inserts a `context.protocols` object into the event payload which contains the omitted properties or traits.**
13+
> note ""
14+
> Only blocked events are forwarded to the source. Events with omitted traits are not forwarded. Instead, Segment inserts a `context.protocols` object into the event payload which contains the omitted properties or traits.**
1215
13-
**Billing Note: Events forwarded to another Source count towards to your MTU counts. Blocking and discarding events does not contribute to your MTU counts.**
16+
> note ""
17+
> Billing Note: Events forwarded to another Source count towards to your MTU counts. Blocking and discarding events does not contribute to your MTU counts.**

0 commit comments

Comments
 (0)