Campaign Execution and Automation
Domain 5 tests smart campaign mechanics: triggers versus batch, qualification rules, flow steps, choices, waits, limits, and request campaigns. This is the execution engine, so questions often ask why a campaign did or did not run.
Smart lists and schedules
Trigger campaigns run when a trigger event occurs, such as a form fill or email click, and do not process existing leads. Batch campaigns run on a schedule and process every lead in the smart list. Qualification rules control repeat runs, including Every time, Once, and Once per interval. Campaign limits cap qualified people or flow steps.
Flow steps
Order matters. Wait steps pause a person; choices branch on filters or triggers. Request campaign steps invoke another campaign and can pass tokens. Webhooks call external services. Remove from flow stops processing.
Testing
Use a small test list, run once, inspect results and logs, and check communication limits and channel statuses.
Worked example: A trigger campaign sends a welcome email after form fill. Set qualification to Once, add a one-day wait, then send. Reasoning: without Once, repeated form fills resend the email; without the wait, the email may arrive before CRM sync completes.
Traps: expecting a trigger campaign to process existing leads; using Every time for onboarding; placing a wait after the send; forgetting campaign limits; assuming batch campaigns respond to triggers.