How it works
Trigger and data needed
Trigger: consent change or page view with known consent state
- CMP consent signal
- Consent fields in the profile schema
- Data usage labels
- Fallback content
Audience and journey logic
- Capture consent in the CMP
- Send it with Web SDK
- Store it in profile consent fields
- Enforce policies at segmentation and activation
- Serve personalised or fallback content
- Audit consent coverage regularly
Channels
- Web
- App
- Ads
How to measure it
- Share of traffic with known consent
- Personalisation reach within consented traffic
- Policy violations blocked
Guardrails
- Default to the most restrictive state until consent is known
- Propagate consent to custom actions
- Test fallbacks for declined visitors
See it in a case study
This use case is implemented in the related case study.
Last updated: