This article describes how to work with the Tealium DataAccess AudienceDB and EventDB.
In this article:
AudienceDB and EventDB services are used to store 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.
AudienceDB and EventDB must be activated for your account. For additional information, contact your account manager.
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.
_viewhave user-friendly column names with attribute IDs.
visitor - badge - fan (30)
_view_normalizedhave user-friendly column names without the attribute IDs.
visitor - badge - fan
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 are 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, for example:
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:
The following articles provide best practices and examples of useful queries:
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 volume. For additional information, see Live Events and Feeds.
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.
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.
Database Credentials are now generated for each user. Previously, credentials were generated for an account and profile and were shared by all users. If someone regenerated global credentials, all user connections were terminated, and all users had to reconnect.
For user-specific credentials, the generated credentials are based on the account, profile, and the user's email address. Users can regenerate their own credentials without terminating other connections. You can remove access for a specific user without terminating other connections. To deactivate a specific user's credentials, contact Tealium Support.
Previously generated global credentials can still be used, but cannot be regenerated.
Use the following steps to get the database authentication credentials: