# Integrations general information

This article will help you configure the integration of AB Tasty using your web analytics tool or any other tools or platforms for which integration is made possible within the AB Tasty interface.

## Concept and Definition <a href="#h_01hdh7drnx1rshx8atem3prqy0" id="h_01hdh7drnx1rshx8atem3prqy0"></a>

Integration is a connection between AB Tasty and a third-party tool (Analytics tools, DMPs, CDPs,…). When the connection is established, tools can exchange data.

The integration allows the realization of specific use cases involving both tools. A basic example would be to create an audience in a third-party tool and to display an AB Tasty variation to the same audience.

Integrations are set up directly within the interfaces (AB Tasty + Partner) and require no specific programming skills.

Your integrations are listed in the **Global dashboard** as [**Connected Apps**](/dashboard/global-experience-dashboard-discovery.md#h_01jp23gvrmt5bj3yen0a8sz6kq):

<img src="/files/keC7UJI9l1U9HEzQfv8r" alt="" width="375">

## The Integration Hub <a href="#h_01hdh7drnxdc2jd7ap8x8ht114" id="h_01hdh7drnxdc2jd7ap8x8ht114"></a>

The [**Integration Hub**](https://app2.abtasty.com/settings/integration/integration-hub) enables you to create, set up, and manage the integrations with the third-party tools available.

To access the integration page, in the left menu click **Integrations**.

<img src="/files/YTwq8qPpFWVE7Ngwj8Qa" alt="" width="563">

The **Integration Hub** page is split into categories that reflect the different types of integrations you can use:

* ***Push integrations***
* ***Pull integrations***
* ***Data Warehouse integrations***
* ***Productivity tools (available soon)***

## Push data Integration General Set-up <a href="#h_01hdh7drnx3n4nehxsv1x6b3w1" id="h_01hdh7drnx3n4nehxsv1x6b3w1"></a>

AB Tasty offers a very simple and detailed report interface. However, you may prefer to read your test results directly in the Analytics tool you are used to, and where you have already defined your objectives.

<img src="/files/eLVbG6ANZ5CFFRpPZR2k" alt="" width="563">

This section is used to create, set up, and manage the integrations that send campaign information viewed by your website visitors to your web analytic tools. This will process them directly in their reporting interface.

### Configuration <a href="#h_01hdh7drny66x8bnem6461c2cm" id="h_01hdh7drny66x8bnem6461c2cm"></a>

To configure an integration, select the desired integration and click create connector, then follow the setup steps.

{% hint style="success" %}
Details on setup for each connector is available here [Push integrations](/integrations/push-integrations.md)
{% endhint %}

When setting up a connector in the Integration Hub, you can decide to automatically send campaign data to your connector. To do so, check the box in the *Options* section, and your connector will be automatically added to the *Advanced step* of your future campaigns (it's not retroactive).

This can be useful if you want to receive all your (future) campaign data in your tool without having to add the connector for each campaign.

<img src="/files/mxNloBz14JyXIigUktMU" alt="" width="563">

By default, the box is not checked, meaning that when you create a campaign, the connector won't be added to the advanced step. You can still select this connector for specific campaign(s).

Once your connector has been created at the account level in the Integration Hub, it is available at the campaign level.

The campaign-level setup allows your campaign to send data to the analytics tool of your choice. This setup is configured at the 6th step of the campaign setup funnel (Advanced options step).

To edit the campaign-level integration, and configuration, open the **Advanced options** step of your campaign and select your tool from the drop-down list. You can activate multiple integrations simultaneously.

<img src="/files/9BMK8K4Lw8AG6tGPloEW" alt="" width="563">

You can also decide to send campaign data to your connector from the connector list of a third-party tool. To do so, go to the Integration Hub, click on the tool card and go to the *setup* tab, unfold the desired connector, tick the box and save your changes.<br>

<figure><img src="/files/L2NhSEL3l6QpgjwGEKAS" alt="" width="375"><figcaption></figcaption></figure>

Once launched, your test will start sending data to all the analytics services that you've configured there.

If you wish to have an integration with a tool that is not on the list, please send us a request using our [Feedback request form.](https://feedback.abtasty.com/features-requests)

## Pull data Integration General Set-up <a href="#h_01hdh7drny31e0mnxgpv89em4x" id="h_01hdh7drny31e0mnxgpv89em4x"></a>

This section allows you to create, set up, and manage the integrations that will allow you to use the audience segments generated by your Data Management or CRM Onboarding tools.

Once a tool has been activated, the audience segments associated with it appear as available criteria in the [**segment builder**](/web-experimentation-and-personalization/targeting-step/how-to-create-a-segment-who-section.md).

<img src="/files/HCNuhzQP25RTMNfzQ75a" alt="" width="563">

### Configuration <a href="#h_01hdh7drny4xtn1ah8fy7cxj24" id="h_01hdh7drny4xtn1ah8fy7cxj24"></a>

To configure an integration, select the desired integration and click create connector, then follow the setup steps.

Each CDP or CRM platform or tool that can send cohorts to AB Tasty has a different way to integrate with AB Tasty.

{% hint style="success" %}
Details on setup for each connector is available in the [Pull integrations](/integrations/pull-integrations.md) section
{% endhint %}

If you wish to have an integration with a tool that is not on the list, please send us a request using our [feedback deposit process](https://feedback.abtasty.com/features-requests).

### Using and Retrieving Your CDP/ DMP segments <a href="#h_01hdh7drnyd24cf4627d2hf2qw" id="h_01hdh7drnyd24cf4627d2hf2qw"></a>

When you have activated and configured an integration, you will be able to retrieve your tool’s segments in AB Tasty.\
Note that it may take some time for the audiences to be displayed in AB Tasty depending on the tool (see the documentation of your tool to learn more).\
You can retrieve these segments in the segment builder, in the "external data" category:\ <br>

<figure><img src="/files/QYEJlVBgJtM1vczDIvJi" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Good to know 💡 -** audience availability in the segment builder

For an audience to be available in the segment builder, it must not be empty, meaning that we have to identify at least one user belonging to the audience.

Once a user is identified, the audience will appear in the segment builder.
{% endhint %}

## DataLayer Integration general information <a href="#h_01hdh7drnywbjkcg2v3kbkn99s" id="h_01hdh7drnywbjkcg2v3kbkn99s"></a>

### Definition <a href="#h_01j3n77fjt0j2mvkttvskrjwax" id="h_01j3n77fjt0j2mvkttvskrjwax"></a>

A data layer is a JavaScript object implemented into a website’s HTML code. The dataLayer collects information related to the interactions between the visitor and the website pages. This information is varied: it can be personal information on the visitor, the currency used for purchases, the product categories available on the website, etc. It is always made up of a name and variable pair (for instance, **Site\_currency** is a name and **USD** is the variable).

This data is forwarded to a Tag Management System (TMS), to be centralized and later utilized when preparing marketing actions targeting visitors.

### Use cases <a href="#id-01j3n7n6z9zxz9w0rjvh2qyk4v" id="id-01j3n7n6z9zxz9w0rjvh2qyk4v"></a>

With AB Tasty, if the pages of your website feature a dataLayer, you can use the data made available to address 3 use cases:

* **Retrieve your dataLayer variables** and use them to create specific triggering conditions to target your campaigns (in the trigger builder - see [article](/assets-library/creating-and-managing-triggers/list-of-trigger-criteria/datalayer-criterion.md))<br>

  <figure><img src="/files/B5qDPSA9bjVUfjYOjpSs" alt="" width="375"><figcaption></figcaption></figure>
* **Create custom trackings** and trigger events for your campaign reports (see [article](/assets-library/trackers-page/how-to-create-a-custom-tracker-via-the-datalayer.md))
* **Create a transaction tracking affiliation** to get some transactional events in your reports (see the [article](broken://pages/Vcf2nmWwkzOAg642d5hu))

### How to set-up your dataLayer <a href="#id-01j3n7mvggbj0kg6r646vxk6nm" id="id-01j3n7mvggbj0kg6r646vxk6nm"></a>

The following TMSs are nativelly supported by AB Tasty:

* TagCommander
* Tealium
* Google Tag Manager

But **if you are using a TMS other than those listed above**, **simply define a custom dataLayer** and specify the JavaScript object containing your data in the dedicated field.

In the [dataLayer set-up page](https://app2.abtasty.com/settings/integration/datalayer), you need to select the TMS that enables you to access your data layer information.

If you are using a TMS other than those available on the list, select **Custom** from the drop-down list and enter the JavaScript object that matches your data layer.

<img src="/files/3M3sYXdTQh9o6kysUbWn" alt="" width="563">

Once the configuration is complete, you may use your dataLayer to add visitors to your campaigns.

## Other Integrations <a href="#h_01hdh7drny9hretbc9vkafybbp" id="h_01hdh7drny9hretbc9vkafybbp"></a>

AB Tasty offers other integrations that will help you execute different use cases. See details in the section [Other integrations](/integrations/other-integrations.md).


---

# Agent Instructions: 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:

```
GET https://docs.abtasty.com/integrations/integrations-general-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.