- 1 Minute to read
- Print
- DarkLight
Basics
- 1 Minute to read
- Print
- DarkLight
This page explains how blacklists work in Mapp Engage — including what types of data can be blacklisted, how entries are managed (manually, via import or automation), and what happens when blacklisted contacts are involved in messaging or import processes.
1. What can be blacklisted?
You can blacklist the following data types:
Email addresses
Mobile phone numbers
Domains
Domains can be blacklisted to prevent messages from reaching entire organizations or specific address ranges — for example, internal test addresses or domains restricted by policy.
Entries can be added:
Manually via the interface
Through file imports
Using the API
As part of automated workflows (e.g., after opt-out events)
Blacklisting is a manual decision. Unlike deactivation, it is not triggered automatically.
2. Import file formats
Mapp Engage supports the following formats for blacklist imports:
Text files
Entries can be separated by commas
someone@example.com, example.com, 1234567890
Line-by-line:
someone@example.com
example.com
1234567890
XML files
Each entry must be wrapped in the appropriate tag:
<blacklist>
<email>someone@example.com</email>
<domain>test.com</domain>
<phone-number>212121212</phone-number>
</blacklist>
MD5 hashed files
Only hashed email addresses are supported
Other formats will be ignored
3. Group vs. System Blacklist
Feature / Behavior | Group Blacklist | System Blacklist |
---|---|---|
Scope | Affects one specific group | Affects all groups and the entire system |
Data deleted | Only group-related data | All profile, message, and subscription data |
Contact removed from group(s) | From the selected group only | From all groups |
Re-subscription possible | Not to the same group | Not to any group |
Blocked during import | Only in the same group | In all imports |
Receives forwarded messages | No | No |
Profile remains in system | Yes | No |
4. Using automation to manage blacklists
You can also add contacts to blacklists via automation workflows. For example:
After an unsubscribe event
Based on profile changes or behavior
Using event-based workflows for opt-out handling
Automation activities:
5. What happens when blacklisted contacts are targeted?
Mapp Engage automatically blocks any communication or list entry involving blacklisted contacts:
Subscription requests via API, email, or SMS are ignored
Landing page subscription attempts return an error
UI-based group additions trigger an error
Imports skip the contact and log an error
Messages forwarded by other recipients are not delivered
These safeguards ensure that blacklisted contacts are permanently excluded — even unintentionally.