Name: IForevents
Author: IForevents

Every event IForevents accepted is kept for the plan's retention, so a destination can be fed the past: Settings → Destinations → Replay…, pick the window, start.

The replay reads the project's events for the window from storage and sends them through the destination exactly like live traffic, batched, logged and retried. Progress and the total are listed under Replays.
The window is bounded by the plan's replay days (7 on Pro, 30 on Growth, 90 on Scale). Free has no replay.
Deliveries made by a replay count toward the month, like any first attempt; retries of failed deliveries never count.
Tools that de-duplicate on the event id (Mixpanel, Amplitude) ignore events they already have, so replaying a window twice is safe there.

Every event IForevents accepted is kept for the plan's retention, so a destination can be fed the past: Settings → Destinations → Replay…, pick the window, start.

The replay reads the project's events for the window from storage and sends them through the destination exactly like live traffic, batched, logged and retried. Progress and the total are listed under Replays.
The window is bounded by the plan's replay days (7 on Pro, 30 on Growth, 90 on Scale). Free has no replay.
Deliveries made by a replay count toward the month, like any first attempt; retries of failed deliveries never count.
Tools that de-duplicate on the event id (Mixpanel, Amplitude) ignore events they already have, so replaying a window twice is safe there.