Encore Logic Update: Avoid Double-Pulling the Same Registrants
You’ll usually spot this when a later event in your multi-event campaign has far fewer registrants than expected, or none at all. If you’re using multi-event campaigns in AEvent, whether for challenges, workshops, or back-to-back offers, it helps to understand how encore logic works so you don’t confuse your audience or break your automations.
The one rule to remember
Correct: chain your events in sequence
Event #1 → Event #2 → Event #3. Each event fills from the stage before it, so every registrant keeps moving forward.
Incorrect: pull the same event twice
Event #1 feeds Event #2 and Event #1 also feeds Event #3. Event #3 arrives empty, because those registrants were already used by Event #2.
What you can’t do
You can’t encore registrants from the same event into more than one future event.
Example of an incorrect setup:
Event #1 → Event #2 (encore for non-attendees)
Event #1 → Event #3 (a second encore or follow-up from the same source)
In this setup, Event #3 stays empty, because the registrants from Event #1 were already used by Event #2.
What to do instead
Each registrant can only be encored once from any given event. To structure your campaign correctly:
Chain your events logically: Event #1 → Event #2 → Event #3.
Pull from the previous stage, using the non-attendees or partial attendees from Event #2 to populate Event #3.
Treat each encore as a new stage, not a repeat pull from the original event.
Why it works this way
Encore logic is built to prevent duplicate messaging and over-saturation. Once registrants have been pulled into a follow-up event, they’re considered used from that source, so they won’t qualify for another pull from the same point.
Chaining your events stage by stage keeps every registrant moving forward without ever getting messaged twice for the same reason.