Choosing the Right List Type
Both blacklists and Robinson lists in Mapp Engage prevent messages from being sent to specific contacts. They serve similar goals but differ in how they handle data, when they apply, and what level of control they offer. Use this comparison to decide which method best fits your compliance and communication needs.
Which method is right for your use case?
To decide between a blacklist and a Robinson list, consider what should happen with the contact data and how strictly you want to block communication.
Use a Blacklist when:
You need to remove the contact from the system entirely, for example:
A user requests permanent data deletion (e.g., GDPR “right to be forgotten”)
A contact has abused your system (e.g., spam complaints or legal issues)
You want to prevent re-imports or re-subscriptions
You need a hard block — no messages, no data, no trace
Use a Robinson List when:
You want to keep the contact and their data, but still block sendouts
The contact opted out temporarily but may return later
You manage multiple systems or brands and need shared exclusions
You want faster imports, without real-time blacklist checks
In short:
Blacklist = hard block + data removal
Robinson List = soft block + data retention
Comparison at a Glance
Feature / Behavior | Blacklist | Robinson List |
|---|---|---|
Purpose | Block and remove contacts | Block messages without removing data |
Scope | System-wide or group-specific | System-wide, can apply across multiple systems |
How it works | Contact is removed and blocked | Contact is kept and blocked at sendout time |
Data deleted | Yes (fully or group-specific) | No – all contact data is retained |
Can be re-imported | No – imports are blocked | Yes – imports succeed, but sendouts are blocked |
List management | Managed directly in Mapp Engage | Managed externally, often shared |
Sendout blocking | By removing contact from groups/system | By filtering contacts at sendout |
Reporting impact | Skipped contacts may appear in stats | Skips appear in stats |