Build and troubleshoot sequences
Connect triggers, waits, conditions and emails into a reviewed follow-up journey.
Prepare templates and triggers
Create the email templates you need before assembling the sequence. Open Sequences, create a sequence and choose the trigger offered by the builder. Product, tag and list triggers require the corresponding item from this website. Do not assume creating a sequence automatically enrolls every historical contact.
Choose exit products when buying an offer should stop a promotional sequence. Review the buyer-email options carefully: post-purchase service messages and ordinary marketing do not have identical consent rules.
Assemble the steps
Add steps in the order you intend them to run. The builder supports email templates, waits, conditions, tag changes and manual-list changes. Set wait amounts and units explicitly. A condition's false path can skip or exit according to its setting; check the choice instead of assuming a visual branch means a second independent sequence.
List-changing steps operate on manual lists, not arbitrary external addresses or a smart list's computed membership. Select products, templates and tags from this website and resolve validation errors before activation.
Save, review and activate
Save the whole builder and reopen it to check trigger, ordered steps and exit conditions. Review the template subjects, links and signatures too. Activate only after the journey is ready; pausing is different from deleting.
Manual enrollment is available from a subscriber profile for an active sequence, subject to eligibility checks. Use a contact you control for an intentional test. Do not enroll real customers merely to verify a screen.
Diagnose a missing email
Inspect the contact's enrollment, the sequence's active state, wait step and current eligibility. A contact may have exited after an exit-product purchase or failed a condition. Marketing restrictions and provider delivery failures can prevent a send even if the builder looks complete.
Per-step statistics help locate where a journey stops; they do not prove the content reached the inbox. Compare email delivery state and connection health. Changes to a running automation deserve care: do not promise that editing a step rewinds emails already sent or restarts every old enrollment.
For review requests, create the review-request template and deliberately place it in the post-purchase flow; the Reviews screen does not send it automatically.