> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/tealium-feature-experimentation-integration/send-feature-experimentation-event-to-tealium.md).

# Send Feature Experimentation Event to Tealium

{% hint style="warning" %}
**Visitor ID Requirement**

To make this server-side integration work properly, you need to pass the visitor ID provided by your third-party tool.

What you must do:\
• Create the connector\
• Ensure Tealium knows the visitor ID\
• Retrieve the visitor ID using: *`utag.v_id`*\
• Call the Decision API with this visitor ID, otherwise, the hit will not be sent to the third party
{% endhint %}

## Overview

The AB Tasty > Tealium Server-Side Connector lets you automatically send experiment data from AB Tasty’s Feature Experimentation platform to Tealium EventStream or AudienceStream. This integration enables you to analyse the impact of specific feature flags and variations on your key metrics directly within Tealium’s ecosystem without relying on client-side tracking.

Once set up, the connector transmits campaign and variation identifiers as custom events or attributes whenever a decision is made for a visitor. This ensures consistent server-side tracking across both platforms, allowing for unified reporting and more accurate behavioural insights.

### How-to

{% tabs %}
{% tab title="1. On Tealium" %}

#### **1. Define a Feature Experimentation Event**

* In the left menu, go to **Event Specifications** (under *Event Data*).
* Click **+ Add Event Specification**.
* Fill in the form:
  * **Event Name:** `flagship`
  * **Description:** Something like *Triggered when AB Tasty delivers a feature decision.*
* Save the specification.

You now have an empty event definition called flagship that will structure incoming data.

**2. Add Event Attributes**

* Still under *Event Data*, open **Attributes → Event Attributes**.
* Click **+ Add Attribute** twice to create:
  * `flagship_campaign` → *String*
  * `flagship_variation` → *String*

These attributes tell Tealium what data to expect and how to type it.
{% endtab %}

{% tab title="2. On AB Tasty" %}

#### **Create a Tealium Connector**

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FLaz0QCT6IhkwZZW1ZqPb%2FCapture%20d%E2%80%99e%CC%81cran%202026-03-09%20a%CC%80%2014.49.01.png?alt=media&amp;token=12b8e64c-90e7-424a-b530-1d00345bcb6f" alt=""><figcaption></figcaption></figure>

On AB Tasty go to [**Settings > Integration > Feature Experimentation Tab**](https://app2.abtasty.com/settings/integration/integration-hub?page=feature-experimentation)

* Look up for Tealium card on the push section and click on **Create**
* [Fill in](#user-content-fn-1)[^1]
  * Tealium account
  * Tealium Profile
* Create the connector
  {% endtab %}
  {% endtabs %}

### **FAQ**

**Why include the visitor ID?**\
Tealium needs a known `tealium_visitor_id` to link the event to a visitor profile. Without it, the hit won’t appear in Live Events or trigger connectors.

**How to get it?**\
Retrieve it from `utag.v_id` on the Tealium client and include it when calling the AB Tasty Decision API.

**What if I skip it?**\
The event won’t be processed or visible in Tealium.

**How to check the hit?**\
Go to **EventStream → Live Events** to confirm your `flagship` event was received.

[^1]: <img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fk85PArHaMIQOLlPbaOAR%2Funnamed-2.png?alt=media&amp;token=ce4784d4-86c6-408c-b1a5-9b8956dc9ee9" alt="" data-size="original">


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentations-integrations/tealium-feature-experimentation-integration/send-feature-experimentation-event-to-tealium.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.