Replay takes an archived copy of your Segment data, and re-sends it to new or existing tools.
On the surface this doesn’t sound like much, but this can grant huge benefits to mature data systems: By archiving and replaying data, you can avoid vendor lock-in, and protect your system against data loss.
Replays for tooling changes
With replays, you can send your existing data to new tools. This means you can send a limited sample of your data to a new tool to test it out, and run similar tools in parallel to verify the data format or accuracy of the output. Finally, when you’re ready to switch to a new tool, you can replay a full set of your data to the new tool to backfill it with data that extends before you set up the tool - no warm-up time or operational gap to disrupt your work.
Note: Any destinations which accept cloud-mode data (meaning data from Segment, and not directly from users’ devices) can use replay, however they must also process timestamps on the data for replay to be useful.
Replays for resilience
With replays, you’re protected from outages and errors. If a destination which you rely on experiences an outage, or isn’t able to accept incoming data, you can use Replays to re-send data to that tool once the service recovers. You can also use replays to recover from errors caused by misconfigurations in your Segment systems - sending data in the wrong format, or want to apply destination filters? Change your mapping, clear out the bad data, and replay it from the source. You can also use this to update the schema in your data warehouse when it changes.
Replays are currently only available for Business Tier customers, and due to their complex nature are not self-serve. Contact us to learn more, or to request a replay for your workspace. When requesting a replay, include the workspace, the source to replay from, the destination tool or tools, and the time period.
Replays can process an unlimited amount of data, however they are rate limited to respect the limitations in downstream partner tools. The replay time depends on the tool we’re replaying to, and the amount of data included in the replay.
Replays do not affect your MTU count, unless you are using a Repeater destination. Notify your team before initiating a Replay if you’re using a Repeater destination.
Replays are available for any destinations which accept cloud-mode data (meaning data routed through Segment) and which also process timestamps. Destinations that are only available in device-mode (meaning where data is sent directly from the users’ devices to the destination tool) cannot receive Replays.
Not all destinations support data deduplication, so you may need to delete, archive, or otherwise remove any old versions of the data before initiating a replay.