Consent Preferences: Consent Validity
146+0%Consent & Preferences
Collapse / Expand
Consent & Preferences is the operational workspace for consent preferences within customer 360, where teams manage concrete records, dependencies, and execution decisions rather than static summaries. The business and compliance goal is to keep consent and frequency caps aligned with approved claims, consent controls, market rules, and audit evidence at every step. This page presents role-scoped actions, linked downstream impacts, and policy-aware guardrails so users can work quickly without violating promotional or safety obligations. Next, use this consent preferences workspace to execute governed tasks and route outcomes to connected teams.
Access Boundaries
SSO + RBAC/ABAC controls are evaluated by brand, market, function, agency zone, and risk tier before actions are enabled.
Field Surfaces: Approved-only enforcedExternal Partner: Submit-onlyRisk Tier Scope: Low/Moderate/High/Critical
Consent Preferences: Cap Compliance
153-4%Consent Preferences: Suppression Hits
160-8%Consent Preferences: Policy Exceptions
167+5%Consent Preferences: Update Timeliness
174+1%Consent Preferences: Audit Coverage
181-3%Operational Focus
- Track consent version by market.
- Apply frequency caps by persona segment.
- Block non-consented activation attempts.
What To Do Next
- Review expired consents.
- Publish updated suppression lists.
- Audit override attempts.
Consent and Preferences Studio
Control channel consent, suppression lists, and frequency caps before audience activation.
| ID | Title | Market | Owner | Status | Risk | Related |
|---|---|---|---|---|---|---|
| CNS-0001 | Consent Preferences · Consent policy 1 | ES | Privacy | Draft | High | Open HelpOpen Settings |
| CNS-0002 | Consent Preferences · Preference update 2 | JP | Compliance | In Review | Critical | Open HelpOpen Settings |
| CNS-0003 | Consent Preferences · Frequency cap 3 | AU | IT Security | Approved | Low | Open HelpOpen Settings |
| CNS-0004 | Consent Preferences · Suppression rule 4 | BR | Privacy | Active | Moderate | Open HelpOpen Settings |
| CNS-0005 | Consent Preferences · Consent policy 5 | MX | Compliance | Blocked | High | Open HelpOpen Settings |
| CNS-0006 | Consent Preferences · Preference update 6 | SG | IT Security | Escalated | Critical | Open HelpOpen Settings |
| CNS-0007 | Consent Preferences · Frequency cap 7 | US | Privacy | Draft | Low | Open HelpOpen Settings |
| CNS-0008 | Consent Preferences · Suppression rule 8 | CA | Compliance | In Review | Moderate | Open HelpOpen Settings |
| CNS-0009 | Consent Preferences · Consent policy 9 | UK | IT Security | Approved | High | Open HelpOpen Settings |
| CNS-0010 | Consent Preferences · Preference update 10 | DE | Privacy | Active | Critical | Open HelpOpen Settings |
| CNS-0011 | Consent Preferences · Frequency cap 11 | FR | Compliance | Blocked | Low | Open HelpOpen Settings |
| CNS-0012 | Consent Preferences · Suppression rule 12 | IT | IT Security | Escalated | Moderate | Open HelpOpen Settings |
Page-Specific Data
Consent data enforces preference history, cap settings, and suppression rules before activation. Current page path: /consent-preferences.
Relationship Graph
Linked entities are enabled so users can traverse parent-child dependencies and downstream impacts without manual lookup.
Consent Tools
Update channel preferences with audit entry.
Set frequency cap per segment/channel.
Sync consent snapshot to activation surfaces.
| Execution Step | Owner | ETA |
|---|---|---|
| Validate input | Ops | 5m |
| Policy checks | Compliance | 8m |
| Route next action | Workflow | 3m |
Consent and Privacy Module
| Rule | Segment | Channel | Cap | Status | Related |
|---|---|---|---|---|---|
| CNS-001 | US-Oncology-HCP | 2/week | Active | Open | |
| CNS-002 | UK-Cardio-HCP | Web remarketing | 4/week | Active | Open |
| CNS-003 | JP-Patient-Support | SMS | 1/week | Pending | Open |
| CNS-004 | BR-Field-Followup | CLM | 3/month | Expired | Open |
Governance Notes
- Every approval, publication, policy block, and AI output writes an audit event.
- Consent and frequency caps are evaluated before deployment packaging.
- Expiry and withdrawal controls maintain cross-channel evidence status.
- Safety routing is always flag-and-route with human adjudication.
Geo Coverage
US1,820 active
UK640 active
DE550 active
JP730 active
BR500 active
AU320 active
Seed Coverage Summary
brands: 8campaigns: 30briefs: 200assets: 6,000components: 20,000claims: 2,500references: 8,000markets: 12localizationJobs: 1,500mlrPackages: 15,000reviewSteps: 60,000annotations: 200,000interactionsRollup: 2,000,000socialSignals: 50,000aeSignals: 1,500experiments: 5,000reports: 3,000connectors: 250auditLog: 300,000