Tealium
Use warehouse visitor events for Tealium AudienceStream.
Connect this destination to write warehouse visitor events onto Tealium AudienceStream, for use in Tealium audiences and connectors.
This destination writes to your Tealium account and is a good fit when you want to:
- Make warehouse visitor or event data available in AudienceStream
- Match visitors on a visitor ID and include an event name
- Map attributes that already exist as Visitor attributes in Tealium
This maps to GrowthLoop Syncs:
| Use it for | Syncs |
|---|---|
| Sending warehouse visitor events into Tealium AudienceStream | ✓ |
This destination writes visitor events. It does not export GrowthLoop audience membership.
Prerequisites
Make sure you have:
- A Tealium Customer Data Hub account. See Tealium's Customer Data Hub if you need one.
- The Account name from the URL you use to open Tealium.
- A Profile name. Open Manage Profiles in Tealium if you need to copy an existing profile or create one.
- A Data Source Key from an HTTP API data source. In Customer Data Hub, go to Sources → Data Sources, open the data source, and copy Data Source Key. See Tealium's HTTP API Advanced if you need to add that data source.
- Visitor attributes already created in Tealium for any extra fields you will map. See Tealium's add an attribute guide.
Set up Tealium as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination in the top right corner.
- Search for Tealium and click Add Tealium.

- Enter the required information, then click Create.

| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Tealium AudienceStream". |
| Sync Frequency | Set the default sync frequency (for example, daily or weekly). You can override this setting for individual syncs. |
| Account | Tealium account name from the URL you use to open Tealium. |
| Profile | Tealium profile name. |
| Data Source Key | Data source key from Sources → Data Sources. |
| Prefix for Personalization Fields (optional) | Prefix GrowthLoop adds to mapped field names, then strips before sending the event. The default value is fw. Leave this blank for no prefix. If you set one, it must start with a letter and use up to 5 letters or numbers. |
Tealium then appears in your list of connected destinations.

Create a sync in GrowthLoop
Create a sync from a warehouse table to write visitor events onto Tealium AudienceStream. See Syncs for information on how to complete those steps.
Select an Object Type:
| Object | Use it for | Sync modes |
|---|---|---|
| Visitor | Send visitor events into AudienceStream | Insert only, Update only, or Insert or update |
When you configure the sync:
- Connection: Select your Tealium destination.
- Object Type: Select Visitor.
- Update Rule: Choose Insert only, Update only, or Insert or update. GrowthLoop posts events in every mode. See Sync behavior.
- Dataset/Table: Select the warehouse table that holds the records.
- Match Field: Map visitor_id.
After you map fields, click Save Sync or Update Sync. Enable the sync with the toggle at the top of the page.
When you update mappings on an existing sync, choose Updates only unless you need Back-fill. Back-fill rewrites already synced rows and can be expensive on your warehouse.
The mapping UI lists visitor_id. Type event_name and every other Visitor attribute name in the destination field. Names must already exist in Tealium.
Visitor fields
| Destination field | Required | Description |
|---|---|---|
| visitor_id | Yes | Unique visitor identifier. GrowthLoop sends it as tealium_visitor_id |
| event_name | Yes | Event name. Type this destination field. GrowthLoop sends it as tealium_event |
| Additional Visitor attributes | No | Type the exact attribute name from Tealium. The attribute must already exist |
Sync behavior
| Behavior | What happens |
|---|---|
| When it runs | GrowthLoop sends the sync as a batch on the next successful run. |
| Insert only, Update only, and Insert or update | GrowthLoop posts each row as a Tealium event. The update rule does not change that write. |
| Match | Map visitor_id and event_name. Rows missing either field fail. |
| Additional fields | Mapped attributes are included on the event. GrowthLoop strips Prefix for Personalization Fields from those field names. |
| Removes | GrowthLoop does not remove previously sent events or visitor attributes. |
| Deletes | GrowthLoop does not delete Tealium visitors. |
Confirm the export was successful
When the run finishes, confirm you can use the data in Tealium.
- Visitor sync: Open AudienceStream in Tealium Customer Data Hub, select Visitor, and look up a visitor you sent. Confirm the mapped attributes.

This workflow does not create a GrowthLoop audience export.
In GrowthLoop, confirm the sync appears in the Syncs table. See Syncs for more information.
Congrats on successfully exporting to Tealium!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| You cannot create the destination | Account, Profile, or Data Source Key is wrong | Copy the account name from your Tealium URL, the profile name from Manage Profiles, and the key from Sources → Data Sources |
| Rows fail to sync | visitor_id or event_name is unmapped or blank | Map visitor_id and type event_name as a destination field |
| Additional attributes do not appear | The destination field name does not match a Visitor attribute in Tealium | Create the attribute in Tealium first, then type the exact name in the destination field |
| You cannot find the visitor | The mapped visitor_id does not match the tealium_visitor_id Tealium already uses | Use the same visitor ID Tealium stores for that person |
| A sync did not create an audience in GrowthLoop | This destination writes Tealium events only | Confirm the visitor in AudienceStream. Tealium does not receive GrowthLoop audience membership |
Updated 16 days ago
