About AudienceStore and EventStore
This article describes how to access AudienceStore and EventStore services.
Prerequisites
- Tealium DataAccess must be enabled.
- To send visitor profile data to the Tealium S3 bucket, an Active AudienceStore connector is required. For more information, see the AudienceStore Connector Setup Guide.
- To send event data to the Tealium S3 bucket, at least one active event feed is required.
These services must be activated for your account. Contact your account manager for more information.
How it works
AudienceStore and EventStore services store unstructured audience and event data as compressed JSON files on Tealium’s Amazon S3 bucket. The Tealium Collect tag (or other Collect library) sends event data to the Customer Data Hub where it’s captured in Tealium’s Amazon S3 bucket as flattened JSON data.
If AudienceDB or EventDB are enabled, when the S3 bucket reaches a size of 100 MB (uncompressed) or 1 hour elapses, whichever comes first, the data is compressed and prepared for Amazon Redshift. The compressed data is then copied and imported into the Redshift database for AudienceDB or EventDB.
Changes to stored attributes
If you make changes to the attributes you selected during configuration of EventStore or AudienceStore and publish the changes, all the data for the deselected attributes is deleted from DataAccess. In addition, the deselected attributes are not shown in the database table.
If you select these attributes again, and publish the changes, the attributes will appear in the database table, but the column will be empty until data for these newly selected attributes is sent to EventStore or AudienceStore.
AudienceStore file paths
Data files for AudienceStream are stored in the S3 bucket with a path structure that matches your account name, profile name, and the action ID of the AudienceStore connector:
{account_name}/{profile_name}/audiences/{action_id}
The action ID can be found in the Details of the AudienceStore connector action, as seen here:

Example path to AudienceStore file:
my-account/main/audiences/bafc28ca-9542-3929-3b94-577a84f3d672
EventStore file paths
Data files for EventStore are stored in the S3 bucket as follows:
{account_name}/{profile_name}/events/{event_feed_id}
The event feed ID can be found in the URL for the event feed. Navigate to Live Events and click the feed to select it. Inspect the URL to retrieve the feed ID, as shown below:

Example path to EventStore file:
my-account/main/events/bafc28ca-9542-3929-3b94-577a84f3d672
Data retention
The semi-structured data stored in EventStore and AudienceStore remains available in Amazon S3 indefinitely, unless you remove it.
This page was last updated: July 11, 2023