This article shows how to access your AudienceDB and EventDB services, which store your structured audience and event data in a Postgres-like database using Amazon Redshift where you can query the data directly with your preferred SQL client or BI tool.
These services must be activated for your account. Contact your account manager for more info.
This article covers:
When the service is activated a unique database is created in Amazon Redshift to store your data. This database will contain tables for each kind of data that can be stored there. For Audience data, this will be "visit", "visitor", and attribute tables. For event data, each Stream has a corresponding table with event attributes represented as table columns. For your convenience, there are also views created to make your queries easier to consume.
The tables available for audience data:
Each table has a corresponding view where "_view" is appended to the table name eg. "visitors_view". The table columns are named according to the attribute type and the internal attribute ID. For example, if you have a Badge attribute whose internal ID is "5099", the tables will have a column named "badge_5099". This is where the views come in handy because they provide user-friendly names for these columns. The corresponding column in the view might be "badge - visitor - VIP".
The tables available for event data:
Each table has a corresponding View to make it more convenient to browse the data. The table columns are named according to the attribute type and name, with only some attributes referencing internal ID's. Standard Universal Data Object variables will be 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 will also include information about which tags executed on the page and page performance metrics.
See the EventDB Data Guide for more details.
Data storage is controlled at the Attribute level. Event Attributes and Visit/Visitor Attributes have a checkbox that determines if it will be stored in the database. Simply edit the Attribute and toggle this checkbox to include or omit the Attribute from the database.
All Audiences are stored in AudienceDB.
Streams must be configured to have their data stored in EventDB. We recommend only enabling EventDB for the specific Streams you need since the amount of data can become quite large depending on your volume. See the guide on creating new Streams for more info.
Additionally, EventDB will collect preloaded attributes. These attributes are not editable from the Attributes screen, but you can adjust which ones are stored in EventDB via the DataAccess Console.
To adjust which preloaded attributes are stored in EventDB:
DOM attributes (URL, domain, referrer, user agent, etc.) are always sent and cannot be excluded.
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.
To get the database credentials:
The following fields are displayed:
Save the password for later. It cannot be retrieved once you close the dialog box.
For security purposes the Password is only displayed once, so it's important to store it securely for later use. If you ever lose this value you can regenerate a new one, but it will invalidate all previous connections that used the old value.