Late webinar registrations can disrupt scheduled sends in your event program. Using Delay and Date split nodes helps contacts move through the program at the right time, prevents skipped or outdated emails, and avoids sending multiple messages at once.
Use Case
Imagine you have an event program for webinar registrants, and the program sends emails on specific dates. Sometimes contacts register at the last minute, after your scheduled send dates or between decision-node dates. In these cases, you want to make sure contacts
do not get stuck in the program,
miss important emails,
receive multiple emails at once, or
receive out‑of‑date reminders.
By combining program nodes, you can easily manage these contacts and the communication they receive.
Solution overview
To manage last‑minute registrations effectively, use the Delay and Date split nodes in Dotdigital Program builder. These nodes ensure that contacts progress through the program as intended, no matter when they register. This helps you keep communications timely and prevents contacts from receiving too many emails at once.
Step-by-step guide to limiting last-minute webinar sign-ups in event programs
Step 1: Build a program
Build a simple program that manages event sign-ups.
Step 2: Add the Date split node
Add a Date split node before the Send node to control which contacts should receive each email.
Configure the Date split node to skip emails that should not be sent after a specific date.
An example of a program is provided below the steps.
Step 3: Add the Delay node
Add a Delay node to control when contacts receive each email.
Contacts who enter the program after that date skip the Delay automatically.
An example of a program is provided below the steps.
Step 4: Manage last-minute registrations
Ensure that last-minute move to the correct part of the program based on the current date.
Add any extra logic you need to manage late registrations or special cases.
An example of a program is provided below the steps.
Step 5: Adjust the program logic according to your needs
Adjust the logic to match your pre‑event plan, and test the program to confirm it behaves as expected.
Example
This example program sends email campaigns to contacts who sign up for an event on different dates.
Event forms are sent on March 5.
The program sends an event reminder every five days.
Contacts who sign up after the program starts receive a ‘Thanks for signing up‘ email and subsequent reminder emails based on the date conditions.
Contacts who sign up late, for example, the day before the event, receive both the ‘Thanks for signing up‘ and ‘Event tomorrow‘ emails.
And here an example of more advanced program for a Management event.
Limitations
Timing sensitivity - the effectiveness of the Delay and Date split nodes depends on accurate timing. Ensure that your program's timing aligns with your event schedule.
Complex logic - for more complex scenarios, you may need additional logic to handle specific requirements. Test your program thoroughly to confirm it works as intended.