This guide 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
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.
How to access
The Integration pages enable 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.
The Integration Hub page is split into categories that reflect the different types of integrations you can use:
- Push integrations
Push Integration General Set-up
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.
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.
Integration Hub connector configuration
To configure an integration, select the desired integration and click create connector, then follow the setup steps. Details on setup for each connector is available here.
Setting up a connector in the Integration Hub allows your connector to be configured by default on all your campaigns (not retroactive).
Every new campaign will automatically be populated with these account-level settings.
Campaign connector configuration
Once you will have set up a connector at the account level in the Integration Hub, the connector will be 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.
Once launched, your test will start sending data to all the analytics services that you've configured there.
Every new campaign will automatically be populated with these account-level settings. This means that if as an example you setup Google Analytics 4 in the Integration Hub, Google Analytics 4 integration will be activated by default for every upcoming campaign. If you want a campaign to stop sending data to Google Analytics 4, simply remove Google Analytics 4 from the campaign-level configuration in the test’s Advanced Options.
Good to know 💡
Please note that changes made to the account-level configuration are not applied retroactively to previously created campaigns. They only apply to newly launched campaigns.
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 process.
Pull Integration General Set-up
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 in the targeting options for your campaigns.
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. Details on setup for each connector is available here.
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.
Using and Retrieving Your DMP and CRM Onboarding Audiences
When you have activated and configured an integration, you will be able to retrieve your tool’s audiences 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 use these audiences:
- In the segment builder (available when you create a new segment).
Audiences and traits derived from your integrations are available in the DATA INTEGRATION criteria group.
For each integration, you will have a corresponding item that you can drag and drop to use.
For global information on how to build a targeting segment, please refer to this page.
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.
This data is forwarded to a Tag Management System (TMS), to be centralized and later utilized when preparing marketing actions targeting visitors.
To be precise, with AB Tasty, if the pages of your website feature a data layer, you can use the data made available to you to target visitors during a campaign.
You will need to select the TMS used to manage your data layer via your AB Tasty account settings.
The following TMSs are supported by AB Tasty:
- Google Tag Manager.
Select the Data Layer Manager
You need to select the TMS that enables you to access your data layer information.
To do this, follow the steps below:
- Log in to the AB Tasty platform.
- Click , then Settings > Integrations.
- Click the Data layer.
- Select the desired TMS from the drop-down list.
- Click Save.
Once the configuration is complete, you may use your data layer to add visitors to your campaigns. For further information, refer to Data layer targeting.
AB Tasty offers other integrations that will help you execute different use cases. See details in the following sections: