This article describes how to work with the AudienceDB and EventDB offerings of Tealium DataAccess.
The services described in this article must be activated for your account. For additional information, contact your account manager.
This article covers the following topics:
AudienceDB and EventDB services are used to store your structured audience and event data in a Postgres-like database (Amazon Redshift). From Amazon Redshift, you can then query and analyze the data directly using your preferred SQL client or Business Intelligence (BI) tool.
When a service is activated, a database is created in Amazon Redshift to store your data. The columns in the tables are named according to the attribute type and the internal attribute ID. For example, if you have a badge attribute with an internal ID of "30", the table will contain a column named "badge_30". Views and normalized views of data are created to make it easier to write queries. The normalized view is similar to the view but with the attribute ID omitted from the field name.
The views also simplify the process of running queries with aggregations such as
Visit and visitor attributes are stored in database table columns according to their attribute type and name. Each table is keyed using a
visitor_id. Database views have been created for each table to make it easier to write queries.
The following tables are available for visit and visitor data:
In addition, the following tables exist for special attribute types:
For detailed information, see the AudienceDB Data Guide.
For tables containing event data, event data includes event attributes for all events in the event feed. Table columns are named according to the attribute type and name, with only some attributes referencing internal ID's. Standard Universal Data Object (UDO) variables are named with a "udo_" prefix and most column names match their corresponding attribute names eg. "udo_event_name".
Event data coming from the Tealium collect tag also includes information about which tags executed on the page and page performance metrics.
For additional information, see Live Events and Feeds.
The following tables are available for event data:
It is recommended to only enable EventDB for the specific event feeds that you need since the amount of data can become quite large depending on your volumeFor additional information, see Live Events and Feeds.
Use the following steps to adjust which preloaded attributes are stored in EventDB:
DOM attributes, such as URL, domain, referrer, and user agent are always sent and cannot be excluded.
Use the following steps to adjust which visitor attributes are stored in AudienceDB:
You must use a third-party tool with Postgres support to connect to your database. These tools require authentication credentials to connect, which are provided in the DataAccess Console.
Use the following steps to get the database authentication credentials:
Save and securely store the password for later use. The password cannot be retrieved once you close the dialog box.
If you lose the password, you can regenerate a new one, but it will invalidate all previous connections that used the old value.