Scenario
This applies to Push, Email, and SMS event-triggered campaigns, the only channels where Campaign Versioning is supported for this delivery type. An event-triggered campaign uses With Delay to send a message a set time before or after a trigger event, using either a fixed time value or an event attribute (for example, a flight_time attribute). While users have already triggered the event and are queued waiting for the delay condition to be met, the campaign’s content is edited and published.Behavior
- Editing and publishing a live event-triggered campaign creates a new campaign version — a new campaign ID, with the previous version retired.
- Users who triggered the event before the edit are queued against the retired version, not the new one.
- When the delay condition matures for these queued users, they are dropped. They do not receive the retired version’s content or the newly published content.
- Only users who trigger the event after the new version is published are eligible to receive the updated content.
- This applies only to Push, Email, and SMS event-triggered campaigns. It doesn’t apply to campaigns set to trigger Immediately.
To avoid dropping queued users, publish content changes to a live event-triggered campaign that uses With Delay only after existing delay windows have closed.