Experience Platform · Consent integration
Where consent lives
Laura makes decisions about her data in three places on the same day. None of them reaches Real-Time Customer Profile on its own. Each needs an integration path, and each field is enforced somewhere different. Turn on the paths and see what is respected.
Example assumptions
Example customer, times and decisions.
Real-Time Customer Profile · tomorrow, 09:00
What Laura's profile knows
One row per field, from what Laura decided to activation. Cookie choices stay on the ECID; purposes go to the profile. Highlighted, the layer where it breaks.
Web SDK · AJO · destinations
What happens at each activation
Six moments between today and tomorrow. Each one reads a different field, in a different place.
The recommendation
Separate cookies from purposes, integrate each source through its path and enforce each field where it is used
The cookie banner is not the consent system. It is one of its sources, and the only one tied to a device.
- 01
Cookies through the Web SDK
The CMP calls setConsent on load and when the banner is answered. It stays tied to the ECID, in idSpecific. The Web SDK enforces collect alone; everything else is checked in each rule.
- 02
Purposes via streaming
Preference centre, contact centre and forms send each change to the profile's general consent straight away: CMP source connector, HTTP API or event forwarding. The batch stays as reconciliation.
- 03
Enforcement at every output
With Shield, consent policies on each destination's marketing actions. Without Shield, an explicit filter in every activated audience. AJO checks the channel at send time.
- 04
Nothing empty
An empty consent field does not mean "no": AJO treats an empty email consent as consent by default. Decide the default value and load it for the whole base.