Marketing automation is a category, so you do not create one record called a marketing automation. You stand up an automated program inside a specific product. The most common first build is an automated nurture in Engagement Studio (Account Engagement) or a multi-step journey in Journey Builder. The high-level path below applies to either. Confirm you have the product license and the right user permissions before you start.
- Pick the product and define the goal
Decide whether the program belongs in Account Engagement (B2B nurture toward a sales hand-off) or Marketing Cloud Engagement (high-volume or multichannel journey). Write down the single outcome the program should drive before you touch the canvas.
- Build the audience and entry
In Account Engagement, define the list or rule that adds prospects. In Marketing Cloud Engagement, pick an entry source such as a Data Extension, event, or API call. This decides who enters and when.
- Lay out steps with waits and branches
Add the messages, then the wait steps that set cadence, then the rules or decision splits that send different people down different paths based on their data or engagement.
- Add suppression and exit logic
Attach suppression or exclusion lists so the wrong contacts never receive a send, and define how a contact leaves the program when the goal is met.
- Test, then activate
Run a test send to a seed audience, verify the branching with sample prospects, then start the program and watch the first cohort move through before scaling volume.
What adds a contact to the program: a list or scoring threshold in Account Engagement, or a Data Extension, event, or API call in Journey Builder.
A pause that holds a contact for a set duration or until a date, used to control how fast messages go out.
A branch point that evaluates contact data or engagement and routes each person down the matching path.
An exclusion set that prevents specific contacts from receiving sends even if they otherwise qualify.
- Engagement Studio and Journey Builder are different tools in different products. A program built in one does not run in the other.
- Audiences live in different stores. Account Engagement uses prospects and lists, while Marketing Cloud Engagement uses Data Extensions, so plan the data flow before building.
- Without suppression rules, an automated program will happily message people you meant to exclude. Set exclusions before activating, not after.
- Test branches with real sample data. A decision split that looks correct on the canvas can still route contacts the wrong way if the underlying field is empty.