IBM Repeater Destination

Segment makes it easy to send your data to IBM 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 IBM Repeater in the format they understand. Learn more about how to use IBM Repeater with Segment.


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

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 false.

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

📱 Device-based
☁️ Cloud-based

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.


Write key for the source that high eps events will be sent to

Suppressed Events Write Key

Write key for the source that you want events that would have been suppressed to be written to

Segment Source Write Key

Write key for source that non-filtered events will be written to

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!