Setting up email campaigns: a guide to common scenarios and key considerations

This comprehensive guide covers the most common behavioral scenarios, execution logic paths, and configuration thresholds you will encounter when engineering complex automated email campaign sequences inside SystemeScale.

1. Master email sending order

The order in which emails process inside a campaign strictly follows a linear top-to-bottom logic layout. The email physically located at the very top of the list array is designated as the first transmission block sent.

When you create and attach a brand new email layer to a campaign, the system will temporarily stack it at the very top of the list view. It will display a gray indicator dot because it is inactive. Since the system has not yet been assigned a specific "send after" condition instruction for this new draft, the engine isolates it and does not integrate it into the chronological campaign workflow.

2. Adding a new email to an active sequence

If you insert a new active email block into the beginning or directly into the middle of a live running sequence, the system will only deliver it to contacts who have not yet reached that specific pipeline step.

Contacts who have already passed that exact point in the sequence journey will not receive the new email retroactively.

3. Appending an email to the final step of a campaign

When you add an email as the very last terminal step in an array, the system will automatically send it to all contacts who are currently still subscribed to the master campaign sequence.

Note: Even after a contact successfully receives the final email inside a sequence layout, their database profile remains permanently "subscribed" to that parent campaign unless they are explicitly removed via an automation rule or tag filter. Therefore, appending a new final step milestone will immediately trigger a delivery enrollment loop for those resting existing contacts.

4. How delay logic processes newly added emails

When appending an email to the middle or end of an active sequence array, you must understand exactly how the engine calculates the time delays between delivery nodes.

Example timeline breakdown:

• Your campaign currently holds 2 emails: Email 1 is sent 5 minutes after subscription, and Email 2 is sent 24 hours after the first email completes.
• A user profile subscribes on 01/01/2025 at 10:00 AM.
• They receive Email 1 at 10:05 AM.
• They subsequently receive Email 2 on 01/02/2025 at 10:05 AM.
• Weeks later, on 01/15/2025, you decide to add an Email 3, set to send exactly 24 hours after the previous email milestone completes.

In this exact instance, because the 24-hour delay parameter is calculated from the date the last email was received (January 2nd) and not from the date you published the new draft (January 15th), the required condition is met instantly. Email 3 will be dispatched to those contacts immediately.

5. Email sending conditions and precise scheduling

All specifically configured conditions must resolve and be fully met before the engine dispatches a campaign email. If a delivery condition is not met immediately, the email payload queue will simply hold and be delayed until the next available target window aligns.

You can enforce up to three distinct scheduling parameters:

• Set a absolute Delay: Choose the hard time interval gap between emails in the sequence matrix (Days, Hours, or Minutes).
• Select a Specific Time: Specify the exact designated hour of the day the email payload should be released.
• Choose Sending Days: Select strictly which specific days of the calendar week the email is permitted to go out.

6. Modifying conditions inside an active campaign

It is vital to recognize how altering settings behaves for contacts who are actively flowing inside a live sequence track. When you apply a modification to the sending conditions for future emails in a sequence, the new condition logic only applies to net-new contacts who subscribe to the campaign array after the changes have been saved to the server.

Existing contacts already enrolled in the sequence pipeline will simply continue to receive their emails based entirely on the legacy, original conditions that were locked in place at the exact moment they first subscribed.

If you suddenly change Email 3 from Friday to Saturday at 3:00 PM, the 200 legacy contacts already in the campaign logic will completely ignore this update. They will still successfully receive Email 3 on Friday at 3:00 PM. Any fresh contacts who subscribe after the configuration update will correctly route to receive Email 3 on Saturday at 3:00 PM.

7. Deactivating and reactivating legacy emails

To safely avoid mass sending duplicate emails (which can swiftly damage your sender reputation pool status and trigger hard spam complaints), we strictly recommend engineering an entirely new campaign sequence layout instead of arbitrarily reactivating dormant emails for existing legacy contacts. Only deactivate an email block if you are absolutely certain it should permanently never be sent again.

8. Managing contacts who are unsubscribed but still enrolled

When a specific contact profile manually unsubscribes from marketing emails or their address becomes unreachable due to a hard bounce, SystemeScale does not automatically purge or remove them from the campaign sequence framework.

Instead, the contact securely remains enrolled in the campaign layer. They physically continue to progress and tick through the background sequence steps according to the set delays and intervals, but they simply do not receive the actual email payloads while their system status remains locked as "Unsubscribed" or "Bounced".

If the contact's status ever changes back to "Subscribed" in the future, they will immediately resume receiving emails starting at whatever precise delayed step they have currently reached in the timeline. A campaign sequence never pauses its logic flow, even if the contact profile is temporarily unable to receive the transmission payloads.