> 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/import-tealium-audience-to-feature-experimentation.md).

# Import Tealium Audience to Feature Experimentation

The **Tealium AudienceStream** integration allows you to import your FullStory audiences and badges in Feature Experimentation (FE\&R) so you can target them with FE\&R campaigns.

The **Tealium AudienceStream** pull integration will use a webhook connector setup on Tealium’s end and the [Data Layer Enrichment Public API](https://docs.tealium.com/server-side/attributes/data-layer-enrichment/data-layer-enrichment-api/data-layer-enrichment-public-api/#retrieving-a-visitor-profile-with-the-customer-data-hub-profile-definition-api).

This article will walk you through the different steps to setup the integration.

{% hint style="warning" %}
For the user matching to be achieved (and thus let FE\&R target your Tealium AudienceStream audiences) the FE\&R User ID must be the same value as the Visitor ID used in Tealium

More info on the AB Tasty FE\&R User ID [here.](https://docs.developers.flagship.io/docs/universal-collect-documentation#visitor-id)

More info on the Tealium Visitor ID [here.](https://docs.tealium.com/server-side/visitor-stitching/anonymous-user-visitor-id-attributes/#visitor-id-attributes)
{% endhint %}

The **Tealium AudienceStream** pull integration will use a webhook connector to push audience and badge data to FE\&R.

The webhook connector needs to be set up on Tealium AudienceStream’s user interface. Follow the steps below:

![Capture d’écran 2023-09-29 à 16.25.27.png](/files/dfCyW6u6fjaGan3jq2Ok)

1. Access **Tealium > AudienceStream > Audience Connectors**
2. Click **“Add a connector”**

![Capture d’écran 2023-09-29 à 16.26.19.png](/files/PgCYqwGNjqs983U6MVky)

1. Choose **"Webhook"** and click **"Continue"**. Now you will have to set up the data source, the connector and the action to send audiences to FE\&R.

![Capture d’écran 2023-09-29 à 16.26.31.png](/files/QnQwRBLiQznk08Vig1Js)

1. On the **Source tab, Audience,** select the audience you want to send data from.
2. On the **Source tab, Trigger,** select when you want to send data. Most basic option is "Joins the audience", Tealium will sends the data as soon as a user enter the selected audience.
3. Click **"Continue"**

![Capture d’écran 2023-09-29 à 16.27.50.png](/files/7rEo6gwNF9KbduY1YPXP)

1. On the **Configuration tab**, you need to set up the connector (if you do not already have one). Click **"Add a connector"**.
2. Name your connector e.g. "Audience Sender". Other fields are to be skipped. Click **"Done"**. Then **"Continue"** with you connector selected.

![Capture d’écran 2023-09-29 à 16.28.57.png](/files/e2pQpGtn3z1JllBt43Uo)

1. Name the action e.g. "Audience to FE\&R".
2. Select **"Send Visitor Data via HTTP Request"**.

![Capture d’écran 2023-09-29 à 16.29.25.png](/files/R4bp4rQnKHJZhyeUbtQB)

1. In the **Method** field, select **"POST"**.
2. In the **URL** field, input the following URL **"<https://tealium.third-party.flagship.io>"**.

![Capture d’écran 2023-09-29 à 16.29.55.png](/files/iDU01u7zat6l7LUG2Z22)

1. In the **Header** field, add a mapping, **"Map:"** is your **FE\&R API Key** and **"To:"** is **"x-api-key"**. Use custom text to input those fields. (documentation on [API Keys](https://flagship.zendesk.com/hc/en-us/articles/4506406524828--Retrieving-your-third-party-tools-audiences-in-Flagship))
2. Click **"Finish"**.

The Tealium AudienceStream connector is now setup, now you need to enable the integration on FE\&R. See next chapter of this article to do so.

For further information on Tealium AudienceStream connector, please refer to the [Tealium documentation](https://docs.tealium.com/server-side/getting-started/audiencestream-cdp/connectors/) or [Tealium Webhook documentation](https://docs.tealium.com/server-side-connectors/webhook-connector-setup-guide/#action---send-visitor-data-via-http-request).

<figure><img src="/files/HeWCZFJkbG1hUl25kVyP" alt=""><figcaption></figcaption></figure>

To enable the integration on Feature Experimentation, follow the steps below:

1. Access [**Settings > Integrations > Feature Experimentation Tab > Pull**](https://app2.abtasty.com/settings/integration/integration-hub?page=feature-experimentation)
2. Select **Tealium > Create**
3. Select your Environment
4. Input your **Tealium's "Account"** and **"Profile"** (the one you are sending audiences from)
5. Click **“Create”** to finalize the integration.

For global information on how to retrieve audiences, please refer to [this page](https://flagship.zendesk.com/hc/en-us/articles/4506406524828--Retrieving-your-third-party-tools-audiences-in-Flagship).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
