Scope
This guide covers setup & configuration for Consent, DND & Suppressions. Availability depends on your tenant package, role and configured providers.
Purpose
Keep channel eligibility close to activation decisions.
Configure consent types, sources and suppression lists.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Configure consent types, sources and suppression lists.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Monitor consent state, list health and blocked sends.
- Preserve consent history and regulatory channel rules.
Verify the result
Monitor consent state, list health and blocked sends. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Preserve consent history and regulatory channel rules. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.