Repeater Destination

Repeater quick info

Repeater accepts Page, Alias, Group, Identify, and Track calls. If you reference it in the Integrations object, call it “Repeater”. Repeater is eligible for Replay.

Repeater accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.

This destination is maintained by Segment.

Getting Started

The Repeater destination forwards events from a source back into another source, as though that event occurred 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 destinations.


Add the Repeater as a destination for the source that you want to replicate events from.

Find the source that you want events to flow to, and copy the writeKey from that source.

Go back to the Repeater destination’s settings, and add this writeKey to the write keys list for Repeater.

You can do this for as many sources as you need.

Repeater sends all events it receives to the sources you specified, identified by the write key(s) you added.


You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Supported Sources and Connection Modes

Before you start, make sure Repeater supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode

Segment offers an optional Device-based Connection Mode for Mobile data going to Repeater, so that you can use Repeater features that collect data directly from the mobile device. To do this, you must package the Segment-Repeater mobile SDK with the Segment mobile library.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Setting Description
Identify message
boolean, defaults to FALSE .

If checked, the repeater will add the original message ID in context.repeaterMessageId for debugging.
Write Keys
array, defaults to .

This is the array of source write keys you want to repeat data into.
Write Key Allowed boolean, defaults to TRUE .

True always for this integration

This page was last modified: 28 Oct 2020

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account