To send event data to the Tealium S3 bucket, at least one active event feed is required.
Audience names must be less than 128 characters in length. Longer audience names may be trimmed and errors may occur.
How it works
AudienceStore and EventStore are services that store semi-structured visitor and event data on a customer-accessible Amazon S3 bucket provided by Tealium. Data is stored as shown in the following table:
JSON or CSV
Both services write a new file to S3 whenever the file reaches 100MB (before compression) or 1 hour elapses, whichever happens first. In most cases, files are written significantly more often than that.
The semi-structured data stored in EventStore and AudienceStore remains available in Amazon S3 for the length of time specified in your contract, typically 30 days.
To save event data to EventStore, activate EventStore for one or more event feeds. For more information, see Configure EventStore.
When EventStore is enabled for an event feed, EventDB uses EventStore as a data source, importing the data from the EventStore S3 bucket into the Amazon Redshift database provided by Tealium.
To save audience data to AudienceStore, add an AudienceStore connector for the audience. For more information, see Configure AudienceStore.
AudienceStore is not a prerequisite to activate AudienceDB; these services operate independently. For more information, see About AudienceDB and EventDB.
AudienceStore file paths
Data files for AudienceStore 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:
The action ID can be found in the Details of the AudienceStore connector action, as seen here: