CED: Email Behavioral Tracking-Consent

A data subject's behavioral tracking-consent preferences are stored in the Profile List per channel per trackable behavior, and a data subject may be optedIn or optedOut of the given tracking-consent preference for a given channel and behavioral signal. Each change to the given tracking-consent preference raises an event for optin/optOut, and these event changes are provided via the CED exports. 

For email, these Tracking-Consent preference changes are available via the new TRACK_CONSENT CED output.

Each channel-specific output contains the tracking-consent preference changes for the trackable behaviors within the channel. For example, TRACK_CONSENT contains data subjects' tracking-consent preference changes for Email Open Tracking, Email Click Tracking, and Email Conversion Tracking. Each trackable behavioral signal has its own Tracking Event Type ID.

CED TRACK_CONSENT Layout

Column Nullable? Description
ID N  
EVENT_UUID N  
EVENT_TYPE_ID N Fixed value of "60", as the event type for email tracking-consent preference changes
ACCOUNT_ID N  
LIST_ID N  
RIID N  
CUSTOMER_ID Y  
EMAIL Y Email address that is the subject of the given tracking-consent preference
EVENT_CAPTURED_DT N  
EVENT_STORED_DT N  
TRACKING_EVENT_TYPE_ID N
  • 4 = Email Open Tracking-Consent preference
  • 5 = Email Clicked Tracking-Consent preference
  • 6 = Email Converted Tracking-Consent preference
TRACKING_CONSENT N
  • I = optedIn for behavioral signal tracking of the given behavior
  • O = optedOut for behavioral signal tracking of the given behavior
CAMPAIGN_ID Y  
SOURCE Y  
REASON Y  

You may select to output the "Tracking Consent" Email Event in your CED Connect job configuration.

CED Email Tracking Consent selection

CED Email Tracking Consent selection

Steps to enable and configure

You don't need to do anything to enable this feature.

Tips and considerations

A Tracking Consent event occurs for every value change occurring on the given Tracking-Consent preference.  The initial Tracking-Consent value population triggers a Tracking Consent event; this can occur with the creation of a new RIID record as well as the initial population of the new attributes for existing RIID records.