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/connections/destinations/catalog/repeater/index.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,14 @@ You can do this for as many sources as you need.
26
26
27
27
Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.
28
28
29
+
## Replays with a Repeater destination
30
+
31
+
Running a Replay on a Repeater destination might count toward your MTUs, especially if you are replaying historical data from the source that flows data into your Repeater destination.
32
+
33
+
Because the API plans count by events sent through the pipeline and the Repeater destination resends an event through the entire pipeline, one event might flow through your source twice which increases the throughput count.
34
+
35
+
Segment recommends that you notify your team before initiating a Replay if you’re using a Repeater destination.
36
+
29
37
## Repeater FAQ
30
38
31
39
##### What is the `context.repeatChain` field that I can see on my repeated events?
0 commit comments