Triggering Events for the CMP
The user has not yet made a consent choice
Two events are triggered, in order:
-
kixelltag_consent_waiting
-
kixelltag_page_view
The kixelltag_consent_waiting
event will only trigger in this case.
The dataLayer contains the list of vendors you have selected:
kixelltag: {
vendors: "kcv:143,atp:89,iab:91,iab:755,iab:1111,iab:14,iab:1,iab:92,kcv:403",
vendors_denied: "kcv:143,atp:89,iab:91,iab:755,iab:1111,iab:14,iab:1,iab:92,kcv:403"
},
The user makes a choice, and regardless of the choice, the following events will be triggered in order:
-
kixelltag_consent_updated
-
kixelltag_consent_chose
-
kixelltag_consent_ready
The kixelltag_consent_updated
event updates the dataLayer with the list of accepted or denied vendors:
dataLayer.push({
event: "kixelltag_consent_updated",
kixelltag: {
vendors_consent: "iab:1111,iab:14,iab:1,kcv:143,kcv:403",
vendors_denied: "iab:92,iab:91,iab:755,atp:89"
}
})
And thus, in the end, the dataLayer contains the user's selection:
kixelltag: {
vendors: "kcv:143,atp:89,iab:91,iab:755,iab:1111,iab:14,iab:1,iab:92,kcv:403",
vendors_denied: "iab:92,iab:91,iab:755,atp:89",
vendors_consent: "iab:1111,iab:14,iab:1,kcv:143,kcv:403"
},
The vendor IDs are those present in the Kixell Tag module:
The user has already made a consent choice
On page load, two events are triggered in the following order:
-
kixelltag_consent_ready
-
kixelltag_page_view
As soon as the kixelltag_consent_ready
event triggers, the dataLayer contains the user's selection and Google's Consent Mode V2 is already updated.