Programmatic Languages35% of the exam
RaiseError, exclusion lists and domain exclusion
What RaiseError() does to a subscriber, a job, a journey, data extension writes and billing, why it is error handling rather than exclusion, and how exclusion lists built from data views and Domain Exclusion data extensions on triggered sends keep people out instead.
Given a customer scenario, determine how to programmatically exclude a subscriber at email send time.
~6 min read · 8 practice questions ·
What the exam expects
- Choose RaiseError() parameters that skip one subscriber or stop the whole job, and predict the effect in a journey.
- State how RaiseError() skips affect billing, tracking and data written before the error.
- Reject RaiseError() as a segmentation or suppression method, and pick exclusion lists, suppression lists or query-built exclusion data extensions instead.
- Configure a Domain Exclusion data extension on a triggered send and confirm what it excluded.
- Key terms: RaiseError() (an AMPscript function that stops processing for a subscriber or a job); boolSkipCurrentOnly (the parameter that limits the stop to the current subscriber); exclusion list (an audience whose members aren't sent the email); Domain Exclusion data extension (a data extension from the DomainExclusion template that blocks domains on a triggered send); NotSent extract (the tracking extract that lists unsent subscribers with a reason).
Key facts
boolSkipCurrentOnly default
- Detail
false: stops the entire email job
RaiseError() in journeys
- Detail
- Removes the subscriber from one send only
Billing
- Detail
- Skipped sends aren't counted as email usage
Tracking
- Detail
- Metrics include emails not sent because of RaiseError()
boolPreserveDataExt
true- Detail
- Keeps AMPscript data extension writes made before the error
RaiseError() purpose
- Detail
- Error handling, never exclusion or suppression
Resend exclusion
- Detail
_Sentfor the JobID into a sendable exclusion data extension
Domain Exclusion data extension
- Detail
- DomainExclusion template; predefined Domain field
Domain check
- Detail
- Uses the API call's EmailAddress
Confirm an exclusion
- Detail
- NotSent extract, not the send log
- When an exclusion or suppression list keeps subscribers out of a job, where does the excluded count appear?
- Which query does the resend article give for excluding only recipients who didn't bounce?
- When does an InsertDE() log row written before a RaiseError() skip survive?
- What field does a data extension created from the DomainExclusion template come with?
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 Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Marketing Cloud Engagement Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (8 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