Understanding Restricted Data

Understanding Restricted Data

by on ‎04-27-2017 07:02 PM - edited on ‎02-15-2018 02:48 AM by (1,160 Views)

This article covers the attribute property Restricted Data. This property is used to identify attributes that contain data that should be omitted from Universal Data Hub (UDH) services that send data out of the system, such as 3rd party connectors or DataAccess.

In this article:

Table of Contents Placeholder

What is Restricted Data?

In general terms, restricted data refers to any attribute containing data that is:

  • ✔ private or personal
  • ✔ protected by privacy laws
  • ✔ subject to controlled access

By default, attributes are not restricted and may flow through to a variety of destinations. Attributes are made available to services such as EventDB, as well as 3rd party connectors. Attributes have a setting called Restricted Data that, when set, will prevent that attribute from being included in processes that send data out of the UDH. Attribute enrichments are not affected.

Identifying Restricted Attributes

On the Attributes screen there is a filter named "Restricted Data" that will show all attributes that have been marked as restricted.

udh-restricted-data-filter.png

When editing attribute details you can see the Restricted Data field in the properties section.

udh-attribute-restricted-data-checkbox.png

 

For security purposes, attributes of type Visitor ID are always marked as restricted. This cannot be changed.

How Restricted Attributes Are Handled

The following services handle restricted attributes:

  • EventStore/EventDB

    By default, restricted attributes are omitted from incoming streams. This behavior can be changed in the settings for each stream. (See Live Event and Streams.)

  • Data Layer Enrichment

    By default, restricted attributes are omitted from the visitor attributes returned to the on-page data layer via data layer enrichment with AudienceStream. When the Tealium Collect Tag sends out a request for the latest visitor profile AudienceStream returns attributes that are not restricted. This behavior cannot be changed.

The following services do not handle restricted attributes:

  • AudienceStore/AudienceDB

    By default, restricted attributes are always included, whether they are sent to AudienceDB or exported using the AudienceStore connector. This behavior cannot be changed.

  • Connectors (including Webhook)

    By default, restricted attributes are always included, whether you are sending them to the vendor through mappings or as part of the visitor profile. This behavior cannot be changed.


    A warning message will appear if your connector request contains one or more restricted attributes.

Summary

  • Marking an attribute as Restricted protects it from being sent to select Tealium services.
  • EventStore, EventDB, and Data Layer Enrichment services honor restricted data.
  • AudienceStore, AudienceDB, and Connectors do not honor restricted data.
  • Restricted attributes are available to all enrichments.