Marketing Automation26% of the exam
Journey settings, goals, exit criteria and versions
How a journey's settings and lifecycle behave: contact entry modes and what can change after activation, the default email address, goals versus exit criteria and when each is evaluated, data extension and API Event entry options, and what versions, Pause and Stop do to contacts.
Given a customer scenario, build the appropriate Journey Builder solution.
~7 min read · 14 practice questions ·
What the exam expects
- Choose a contact entry mode and know which mode is fixed after activation and which can't be tested.
- Set the default email address from Contacts or from the Entry Source.
- Combine goals and exit criteria, and predict when each is evaluated and counted.
- Configure a data extension entry source's processing option and hand a developer the API Event's key.
- Predict what a new version, Pause and Stop do to contacts already in a journey.
- Key terms: contact entry mode (when a contact may enter or re-enter); goal (a filter on contact data that measures success and can exit contacts); exit criteria (a filter that only removes contacts); current version (the activated version that admits new contacts); Event Definition Key (the identifier that connects an API to a journey's API Event).
Key facts
No re-entry
- Detail
- Applies to all versions; can't change after activation; unsupported in test mode
Long journey, changing address
- Detail
- Use email attribute from Contacts
Goal without Exit Option
- Detail
- Counted, not ejected
Exit criteria timing
- Detail
- When the contact's time in each wait expires
Goal and exit criteria both met
- Detail
- Goal processed first
Data Extension entry source
- Detail
- Sendable data extension; snapshot at activation
Append-only entry data
- Detail
- Evaluate new records only
API Event
- Detail
- Event Definition Key on the Summary tile; no period
New version
- Detail
- Becomes current; old version finishes its contacts
Pause
- Detail
- Up to 14 days; wait extension for Wait by Duration only
Sources for this section (8)
- Journey Settingshelp.salesforce.com (opens in a new tab)
- Goals in Journey Builderhelp.salesforce.com (opens in a new tab)
- Exit Criteriahelp.salesforce.com (opens in a new tab)
- Entry Sourceshelp.salesforce.com (opens in a new tab)
- Process Entry Source Datahelp.salesforce.com (opens in a new tab)
- Admit Contacts Via an APIhelp.salesforce.com (opens in a new tab)
- Journey Versionshelp.salesforce.com (opens in a new tab)
- Journey Pausehelp.salesforce.com (opens in a new tab)
- Why can't a Single Send journey be used when you need to measure a goal?
- When would you add a Wait by Duration before an exit path?
- Why does Use mobile number attribute from Contacts cope with a changed number?
- Which Pause option is unavailable when the Data Extension entry source uses Evaluate All Records?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Marketing Cloud Engagement Specialist pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Marketing Cloud Engagement Specialist guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both