Start a project
Work eventabee Guides Replay and backfill

Replay and backfill

Replay stored events to destinations after token rotation or consent upgrades.

Updated

Operational

Every event eventabee captures is written to an append-only store before anything else happens. That means you can replay events to destinations at any time — within the retention window (default 30 days).

When replay matters

1. Destination token rotation

You rotated a Meta access token mid-day. Some events failed to fan out during the gap. Once the new token is live, trigger a replay over the affected window.

A visitor rejected marketing consent, then a week later accepted. Their stored events (page views, cart activity, purchases) are now eligible for the Marketing-category destinations they just consented to. eventabee replays them automatically — tagged as backfill so your attribution doesn’t double-count.

3. New destination connection

You connect Pinterest CAPI for the first time. You want the last week’s purchases to flow through so Pinterest can learn from your existing audience. Trigger a replay from Destinations → Pinterest → Replay with a 7-day window.

How to replay

Events → Replay. Choose:

  • Window: time range (up to 30 days; retention limit).
  • Destinations: one or more, or all.
  • Event filter: optional — e.g., only purchase events.
  • Mode: live (fan out immediately) or test (dry run, shows what would be sent).

Replayed events are tagged with replay: true in the destination log so you can distinguish them from real-time events in audits.

Backfill tagging

Automatic backfill (from consent upgrades) passes an additional backfill: true flag and an original_timestamp so destinations that support it (Meta, Google) can credit the event to its original time. Destinations that don’t support custom timestamps receive the event as if it happened now — which is fine for lifecycle/personalization destinations but worth knowing.

Retention

Default retention is 30 days. Longer retention is available on request during beta — reach out.

Caveats

  • Replays are idempotent on event_id. Sending the same event twice won’t create duplicates if the destination dedupes.
  • Replay doesn’t re-trigger server-side Shopify webhooks. Only destination fan-out.
  • Destinations with strict rate limits (TikTok, Snapchat) may throttle a large replay. eventabee respects their per-endpoint limits automatically.