Working with AudienceDB and EventDB

Working with AudienceDB and EventDB

by Community Manager on ‎03-14-2017 12:17 PM - edited on ‎10-26-2017 01:08 PM by (1,706 Views)

This article describes how to access your AudienceDB and EventDB services. These services are used to store your structured audience and event data in a Postgres-like database using Amazon Redshift. From Amazon Redshift, you can then query the data directly using your preferred SQL client or Business Intelligence (BI) tool.

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:

Table of Contents Placeholder

How It Works

When a service is activated, a unique database is created in Amazon Redshift to store your data. The unique database contains tables for each data type that it can store. For audience data, the tables are "visit", "visitor", and attribute. For event data, each stream contains a corresponding table with event attributes represented as table columns.

The table columns 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 "5099", the tables will contain a user-friendly column named "badge_5099". The corresponding column in the view might be "badge - visitor - VIP".

For your convenience, views of normalized data are created to make your queries easier to consume. Tables appended with "-view" contain a normalized view that includes attribute IDs. Visitor-scoped views include a normalized view without the the attribute IDs.

AudienceDB Tables

The following table lists the table types available for audience data:

Table Type

Table Name

View Table Name

Normalized View Table Name

Visitors
Visitor attributes and any audiences they belong to

visitors

visitors_view

visitors _view_normalized

Visitor Lists
Visitor Set of Strings  Attributes only

visitor_lists

visitor_lists _view

visitor_lists _view_normalized

Visitor Tallies
Visitor tally attributes only

visitor_tallies

visitor_tallies_view

visitor_tallies_view_normalized

Visits
Current visit attributes and any audiences they belong to

visits

visits_view

N/A

Visit Lists
Current visit Set of Strings attributes only

visit_lists

visit_lists_view

N/A

Visit Tallies
Current visit tally attributes only

visit_tallies

visit_tallies_view

N/A

Visitor Replaces
Visitor IDs that are stitched in the profile as part of visitor stitching

visitor_replaces

visitor_replaces_view

N/A 

For tables containing event data, event data includes event attributes for all events in the stream. 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 the Live Events and Streams.

EventDB Tables

The following tables are available for event data:

  • events_{STREAM}
  • events_{STREAM}_view (with normalized data)

Enabling Data Storage

  • Attributes
    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 the checkbox on or off to include or omit the attribute from the database.
  • Audiences
    All Audiences are stored in AudienceDB.
  • Streams
    Streams must be configured for the data to be stored in EventDB. EventDB also collects preloaded attributes. Although preloaded attributes cannot be edited from the Attributes screen, you can adjust the preloaded attributes that are stored in EventDB through the DataAccess Console.

    It is recommended to only enable EventDB for the specific streams you need since the amount of data can become quite large depending on your volume

    .
    For additional information, see the Live Events and Streams.

Adjusting Preloaded Attributes

Use the following steps to adjust which preloaded attributes are stored in EventDB:

  1. Go to Act > DataAccess Console.

  2. Under DB is enabled, click Show EventDB Attributes.

  3. Check or uncheck attributes to add or remove them from EventDB .
    All all attributes are checked by default.

    DOM attributes, such as URL, domain, referrer, and user agent are always sent and cannot be excluded.

  4. Click Save. 

Database Credentials

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.

Getting Database Authentication Credentials

Use the following steps to get the database authentication credentials:

  1. Navigate to Act > DataAccess Console.

  2. In the left navigational panel, click DB.

  3. Click Get DB Connection Details.
    The following fields display:
    • Username
      The username for the database connection, usually a combination of your account/profile names.
    • Password
      The password to connect to the database.

      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.

    • Database
      The name of the database, usually the name of your account.
    • Host
      The host name of the database server, specific to your data storage region.
    • Port
      The port number for the connection.

      tealium-udh-db-connection-details.jpg
  4. Obtain the needed information and save for future use.