Back

Learn how event logging works for Tealium Consent Management.

In this article:

Requirements

How It Works

The event logging feature captures changes in user consent and works with all of the Tealium Consent Management offerings. When Tealium Consent Management is deployed to your site and event logged is enabled, each time a visitor grants or revokes consent using the consent prompt, adjusts consent preferences, or changes the "Do Not Sell" option, the new consent state is logged using an HTTP request. For customers of Tealium DataAccess, these events are stored in EventDB and EventStore.

For customers with their own data collection endpoint, a custom URL can be used to receive the events.

The event logging option is offered to help you comply with Recital 42 of the GDPR, which requires that proof of consent be available for auditing purposes.

Event Logging Settings

 The following settings are available:

  • Log Consent Changes - set to Yes to enable event logging (applies to all consent management offerings).
  • Event Log URL - the event collection endpoint used to log consent changes. Only edit this setting if you have your own data collection endpoint.
    Default: 
    https://collect.tealiumiq.com/event
  • Event Log Profile - the profile to which logged events should be sent. The value set here is passed to the Event Log URL as the parameter tealium_profile="PROFILE" .

Related Topics