API explorerChangelog
Overview

Sections

Theme switcher

Consents

Consent is pivotal in modern data-driven interactions, ensuring user privacy and regulatory compliance. Our consent webhook events offer concise updates on changes in user consents throughout their customer journey, providing essential insights for regulatory compliance and user privacy management.

Consent events are only triggered for consents associated with your webhook subscription. To receive events across all consents, specify "AllConsents” when creating your webhook subscription.

{ "Entity": "Consents", "EventType": "consent.status.updated", "ConsentTypes": [ "AllConsents" ] }

Consent Added: The consent.added event is triggered when a consent is added to a profile.

Plain text

Consent Updated: The consent.updated event is triggered when a consent is updated on a profile. This includes updates to the consent status, consent attributes, etc. Additionally, if you opt-out of a preference associated with the consent, the consent.updated event is generated resulting in the consent status update from Granted to Revoked.

Plain text

Consent Deactivated: The consent.deactivated event is triggered when a consent gets deactivated on a profile. This situation often arises when you attempt to add an already existing consent but with a different locale. As a result, the previous consent is deactivated.

Plain text

Consent Element Association Created: The consent.elementassociation.created event is triggered when a consent gets associated with a contact element for the first time.

Plain text

Consent Element Association Updated: The consent.elementassociation.updated event is triggered when a consent associated with a contact element is updated. This happens when you update the associated consent by changing its status, updating consent attributes, etc.

Plain text

Consent Element Association Deactivated: The consent.elementassocation.deactivated event is triggered when a consent associated with the contact element is deactivated. This happens when you update the contact element value associated with the consent and the PreserveConsents flag is set to false.

Plain text

Consent Filter Association Created: The consent.filterassociation.created event is triggered when a consent gets associated with a preference for the first time.

Plain text

Consent Filter Association Updated: The consent.filterassociation.updated event is triggered when a consent associated with a preference is updated. This happens when you update the associated consent by changing its status, updating consent attributes, etc. Moreover, should a preference that was once linked with a consent becomes dissociated and subsequently re-associated, the consent.filterassociation.updated event is generated.

Plain text

Consent Filter Association Deactivated: The consent.filterassociation.deactivated event is triggered when a consent associated with a preference is revoked eliminating the preference association. Additionally, if subscribed, you will also receive the preference.archived event.

Plain text
Was this section helpful?

What made this section unhelpful for you?

On this page
  • Consents