Consent Change Event Specifications

Consent Change Event Specifications

by Community Manager on ‎04-19-2018 10:41 AM - edited on ‎07-19-2018 11:48 AM by (418 Views)

Consent events are used to collect user responses to tracking and data privacy prompts.

In this article:

Table of Contents Placeholder

Overview

Data privacy and tracking are important to consider when collecting visitor activity. These consent events provide a way to send consent changes into the Universal Data Hub.  These events are offered as Event Specifications under the category "Privacy".

Consent Change Events

The following consent events use these optional parameters:

Name Description Example
policy The context of the consent, usually specific to the terms presented to the visitor upon gaining consent. "gdpr"
consent_categories The category names of approved types of tracking and data collection. ["Affiliates", "Social"]

grant_full_consent

This event indicates that the visitor has granted full consent to tracking and data collection.

Example:

{
    "tealium_event" : "grant_full_consent",
    "policy"        : "gdpr"
}

grant_partial_consent

This event indicates that the visitor has only granted partial consent to be tracked. This event is accompanied by a list of category names that the user has consented to.

Example:

{
    "tealium_event"      : "grant_partial_consent",
    "policy"             : "gdpr",
    "consent_categories" : ["Affiliates", "Social"]
}

decline_consent

This event indicates that the visitor has declined (or revoked previous) consent.

{
    "tealium_event" : "decline_consent",
    "policy"        : "gdpr"
}

forget_me

This event indicates that the visitor has requested that all existing data associated with their visitor record be deleted. This event does not imply decline_consent.

{
    "tealium_event" : "forget_me"
}