Data Modeling14% of the exam
Contact Delete suppression, scope and requests
The Contact Delete stages and suppression period, enablement and scope by tenant type, REST delete requests and their status, best practices for large deletions, and what deletion does in MobileConnect, MobilePush, Journey Builder and synchronized data sources.
Explain the Contact Delete process.
~7 min read · 13 practice questions ·
What the exam expects
- Describe the Contact Delete stages, what happens to a contact during the suppression period, and how to change that period.
- Explain where Contact Delete is enabled and how far a deletion reaches in Enterprise 2.0 and other tenant types.
- Build and monitor a REST delete request by contact key or contact ID.
- Apply the best practices for large or sensitive deletions: identifiers, batching, backups and performance.
- Predict what deletion does to MobileConnect opt-outs, MobilePush registrations, journeys and synchronized data.
- Key terms: Contact Delete (the Contact Builder feature that permanently removes contact information); suppression period (the window, 2 days by default, when data stays but can't be viewed or sent to); final deletion (removal from lists and sendable data extensions); OperationID (the identifier a REST delete returns for status checks).
Key facts
Suppression period
- Detail
- 2 days by default, changeable; 0 makes requests immediately eligible
Final deletion scope
- Detail
- Lists and sendable data extensions, not non-sendable ones outside a population
Enterprise 2.0
- Detail
- Enabled at the parent; requests originate there; deletion spans the enterprise
Child-created records
- Detail
- Delete with the child business unit MID in the request
DeleteOperationType
- Detail
- Required; ContactAndAttributes, since AttributesOnly isn't used
Queue
- Detail
- One deletion call at a time; each can take several hours
Batching
- Detail
- At least six requests 5 minutes apart; up to one million records
Journey re-entry
- Detail
- A deleted contact can rejoin even if re-entry was Never
Contacts Analytics
- Detail
- Top-level account; app and REST requests by day, week, month
- Why can't a warehouse treat a deleted contact's subscriberID as a permanent identifier?
- When you set SuppressionRestoreUntilDays through the REST API, which value means zero days?
- Why does a deleted SMS contact who texts STOP afterwards keep the same subscription status?
- How far back can Contact Analytics show deletions, including API ones?
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 (13 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