Segment makes it easy to send your data to Repeater (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Repeater in the format they understand. Learn more about how to use Repeater with Segment.
This destination is maintained by Segment.
The Repeater destination forwards events from a source back into another source, as though that event occured in the second source.
Events are not cached in the Repeater, so it only handles real-time events. You can specify multiple sources as Repeater destinatons.
Segment does not double count MTUs for Repeater events.
Add the Repeater as a destination for the source that you would like to replicate events from.
Find the source that you would like events to flow to, and copy the write key from that source.
Go back to the Repeater destination and add this write key to the write keys list for Repeater.
You can do this for as many sources as you need.
Repeater will replay all events it gets to the sources you specified using the write key(s) you specified.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
To learn more about about Connection Modes and what dictates which we support, see here.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
This is the array of source write keys you want to repeat data into.