This setup is entirely managed through the AB Tasty interface with minimal tech support required.

Key benefits:

• Brand consistency: Serve the AB Tasty tag from your own subdomain (e.g., tasty.yourdomain.com) for a seamless brand experience.

• Improved trust: Some browsers or extensions block third-party domains. Hosting the tag under your domain helps reduce that risk.

• Better performance & compatibility: Delegating the tag can help with faster loading, fewer tracking issues, and improved site reliability.

• Future-proofing: This approach prepares your setup for stricter browser privacy policies and third-party cookie restrictions. This feature is especially useful for companies with strong security requirements, regulated environments, or those looking to optimize data collection continuity.

To start using this feature, please read

The AB Tasty tag is a lightweight JavaScript snippet that you add to your website to enable all AB Tasty features, including campaign delivery, targeting, and analytics.

The tag is designed for speed and efficiency: it loads essential resources dynamically, ensuring only what’s needed is downloaded, which helps keep your site fast and responsive.

The tag is compatible with all major frameworks (React, Angular, Vue.js) and works on both traditional and single-page applications.

It supports advanced features like deferred campaign loading, visitor ID management, and seamless integration with your site’s consent and privacy requirements.

Curious about best practices, technical details, or troubleshooting?

Check out our articles on tag implementation to make the most of your AB Tasty experience

AB Tasty recommends in code, synchronous, AB Tasty hosted implementation. (Read our step by step tutorial ). But some other methods are available to comply with all specific cases.

Synchronous or Asynchronous ?

The generic tag comes in two versions: synchronous and asynchronous.

You will find the synchronous version, as well as the asynchronous version in the Generic Tag page.

Tag performance refers to the impact of the AB Tasty JavaScript tag on your website’s speed, user experience, and technical metrics (like page load time, Core Web Vitals, etc.). The tag is responsible for loading and executing experiments, personalizations, and tracking events on your site.

You will find : it's useful to understand your tag's weight and find ways to improve it (custom recommendations regarding your specific activities).

For more information about the performance center and guidelines, please refer to the following articles:

The AB Tasty Tag is a lightweight JavaScript snippet that enables dynamic experimentation, personalization, and data tracking across your website. It acts as the entry point for all AB Tasty features, ensuring experiments are delivered efficiently and data is collected reliably.

Key Use Cases

The Tag is used for client-side web experimentation and personalizations:

• Display A/B tests and personalization campaigns

The tag will use the listed domain-s to set the tracking cookie.

If you have set your domain as `website.com`, the cookie will be set to `.website.com`.

However, if you have set your domain as `www.website.com`, the cookie will be set to `.www.website.com`.

The tag is always using the widest possible domain. If you have set `order.website.com` and `website.com`, the cookie will be set on `.website.com`. Specify the subdomain is of any use in this situation and you can remove it.

Cookies are shared following the descending tree domain, but not the other way around! In other words, cookies set on `.domain.com` will be shared with `.subdomain.domain.com` but cookies set on `.subdomain.domain.com` won't be shared with `.domain.com`.

Keep that in mind when setting up your domain and ensure this won't cause tracking issues.

This guide reviews AB Tasty's integration options, detailing their pros and cons to aid businesses in selecting the ideal method.

Whether opting for direct HTML integration's control, the flexibility of a Tag Management System, or the ease of Shopify integration, choosing the right method is crucial to digital strategy success.

The generic tag comes in two versions: synchronous and asynchronous.

The Synchronous mode

In synchronous mode, your website’s code scripts will load one after the other. A script can only be loaded if the previous one has finished loading. If a script is blocked, it will stop the script after it from loading.

This document provides detailed information on the compatibility of various modules and scripting tags, ensuring you can make the most of AB Tasty's capabilities on supported browsers and platforms.

General Tracking

Technical details about tracking can be found in the developer portal.

By default and simply by implementing it on your website, our tag is designed to collect browsing data about your visitors. There are four main categories of automated hits:

• Campaign

• Pageview

• dataLayer

• Batch

Campaign

Each time a campaign is seen by the visitor, a campaign hit is sent with the corresponding campaign ID/variation ID pair. One hit is sent per campaign.

Each time a campaign hit is sent, the analytics integration settings are triggered.

Each time a campaign hit is sent, a corresponding JS event is sent. You can for advanced integration.

Pageview

Every time the visitor visits a page, this hit is sent with all the details about the visited page.

dataLayer

If you have configured a data layer integration, then a hit will be sent once per session with all the available data layer keys.

Batch

To reduce its global footprint and increase performance, our tag sends the information in batches when they are triggered close to each other. When a batch hit is sent, you can find the usual details about each type of hit directly into the h parameter of the payload.

With a standard usage of AB Tasty, you should not be needed to implement any of these hits by yourself.

Events

You can send any event to the collection pipeline. This EVENT type of hit is built according to the following pattern: category/action/label/value.

Category

You are free to set the value of your choice in the event category. However, if you want the event to be used in the reporting as a goal or a filter, it must be set as Action Tracking.

Action

The action is the name of your event as it will be displayed in the goals section, the reporting, or the filters.

Label

A label enables adding text to the hit.

Value

A value enables adding value to the hit.

Format

An EVENT hit must be sent using the following format:

For further information, please refer to this .

Shortcut

You can also use the following method if you only need to send the action (name of a goal).

Suggested articles:

Prerequisites

• Access to your website’s HTML code

• AB Tasty account and platform access

Step-by-Step

For a more detailed procedure read :

Suggested articles:

To make your AB Tasty tag work, you must set the authorized domain in your account settings.

The tag will only run on this domain. If someone copies your tag to another domain, it won’t work.

One domain per account ensures a faster and lighter tag execution and reporting

What is my domain?

Enter the part of your site before the first slash ("/") and after any subdomains. Example: For www.my-website.com/fr, enter my-website.com.

The supports two hosting methods:

1. AB Tasty Hosted – Default

2. AB Tasty Delegated

Suppose you are running several experiments at once on your site or application. In that case, a visitor will see each of them as soon as they enter the targeting, which may influence the results, since one experiment can impact the results of another.

To avoid this, we offer an option that allows you to display only one experiment per visitor, even if multiple experiments are running.

Learn more about this option (activation and prioritization rules) in our dedicated articles:

👉 1 visitor 1 test for Web experimentation

👉 1 visitor 1 test for FE&R

Cross-Domain Tracking

Cross-domain tracking helps you follow the user in the case when one or more pages are hosted on a different domain name than the original one. Cross-domain tracking is necessary when a website has a page (payment confirmation, for example) that redirects the user to an external domain. To set-up a cross-domain tracking, go on this on the settings.

You can add a URL pattern as a setting for pages hosted on other domains. Then, click Add and validate your modification.

When our tag is running on a website, it offers a set of variables, constants, functions, and methods you can use to interact with it.

Everything is hosted under the window.ABTasty object. Here are the most convenient ones you might need:

In this object, you will find all the tests that are currently active on your accounts. It displays more information than you would usually need for standard usage but this is convenient to have if you need to dig into your tests.

This object is a simplified version of the ABTasty.accountData.tests object. It will display your active tests with a focus on their current status. Are they running? If not, why have they been rejected? This is the most common object you might use to debug and QA your tests.

This object will display tests that are currently running on the page.

This object will return the visitor ID for the current visitor.

This object will return the campaign history for the current visitor. The campaign history is all the campaignID/variationID pairs that the visitor is currently assigned to.

This object will contain all the settings of the account running on the website. It is convenient to get the identifier, the account name, or various settings, such as framework version or storage mode.

Activate One visitor One test Option on Web experimentation and Personalization

To enable this option, go to:

is a JavaScript library. The purpose of jQuery is to make it much easier to use JavaScript on your website. jQuery takes a lot of common tasks that require many lines of JavaScript code to accomplish, and wraps them into methods that you can call with a single line of code.

AB Tasty offers 3 options for configuring jQuery loading.

Follow the steps below to configure jQuery loading:

1. Go to Settings > Framework

2. Access the Load jQuery section

Click on your profile icon to the top right of the screen to access your profile settings.

Preference

This page is divided into two main sections:

• User Information: Displays the user's profile picture, name, and email. The first and last name fields are editable. The profile picture can be updated, while the email is displayed as read-only.

Plan details

Current plan details

This section covers a range of advanced use cases and custom setups to help you tailor AB Tasty to your specific technical environment. From custom integrations to advanced tagging and optimization methods, these guides are designed for developers and technical users looking to go beyond standard implementation. Each article provides step-by-step instructions to ensure smooth and effective configuration.

You can view your AB Tasty accounts and contacts from the Organization overview page

Accounts

Contacts

Here is a list of Organization settings:

To use AB Tasty on your website, you need to install our tag on your website. The generic tag will allow you to apply the JavaScript layer for your page modifications. For more information about tags, please refer to our article What is AB Tasty Tag?.

The Tag Implementation Page supports two hosting methods:

1. AB Tasty Hosted – Default

2. AB Tasty Delegated (to know more about it please read our tag domain delegation presentation article)

Follow these steps to implement the Tag:

Best practices

These are our recommendations for a good implementation:

• Prefer the synchronous tag version

• Prefer a direct implementation vs a custom implementation (with a TMS for exemple)

• The tag should be placed in your website’s </head> tag, this way you will be sure that your modifications will be applied immediately, before the website loads. This will avoid the flickering effect and will offer an optimal user experience

To follow your tag performance though time, you can access the in the AB Tasty platform and read this article about .

To support users hosting their commercial websites on Shopify, AB Tasty offers two integration methods:

1. Shopify App aka Web Pixel (Recommended)

AB Tasty provides a native app available on the Shopify Marketplace, offering a seamless integration experience.

Key Benefits:

• Automated Tag Installation

• All standard Event Tracking

• Transaction Data Retrieval

• Checkout on Subdomains fully supported

Available for All Shopify Plan : Premium / Plus

When to Use This Method:

• You want to follow Shopify transactional events during the campaign.

• You want to retrieve extended transactional data such as payment info & Cart events

• You don’t want to install AB Tasty Tag on Shopify

• You are using a subdomain for checkout

To know how to use our app, please read article.

To learn more about the functionalities, please read.

2. Custom Application aka Custom Pixel

For users with non-native Shopify setups, a custom integration may be more suitable.

When to Use This Method:

• You have a non-standard Shopify implementation.

• You can manage the AB Tasty tag injection manually.

• You only need to retrieve transaction data on a checkout domain or subdomain.

To know how to configure a Custom Pixel in Shopify, please check article.

Before launching any campaigns, it’s important to validate that the AB Tasty tag is properly implemented and functioning across your website.

Here is a short summary of the availables methods:

Please refer to our dedicated FAQ:

Prerequisites

• A (free) with your configured variables

• AB Tasty platform access

• Published AB Tasty campaign (optional, for validation)

A Single Page Application (SPA) is a type of website that interacts with the user by dynamically rewriting the current page rather than loading entire new pages from the server.

Good to know 💡

AB Tasty is running on a native Vanilla TypeScript framework. Our tag is compatible with a lot of modern JS frameworks, including React, Angular, Vue, Meteor or Ember. The tag is unique for all environments and doesn’t require any additional implementation. To improve its behavior on server-side rendering (SSR) frameworks, an additional step might be needed to delay the application of the modifications.

Addition of JavaScript code

You can add your own JavaScript code. All variations created in our Visual Editor using one of the WYSIWYG features will generate an ES2020 compatible script that will be executed on client-side.

You can also add your own JavaScript code using the Code Editor or the “Add JavaScript” option of the Visual Editor. In this case, the code won’t be transpiled into another language. For example, an ES7 script might not be working on older browsers. It’s therefore your responsibility to manage the compatibility of your own code when adding custom JavaScript.

Management of modifications

The modifications you make in your campaigns are stored into a JS object that will be read and executed on client-side. When a modification targets an existing HTML element, the original one isn’t modified. It is cloned and this clone is modified and then displayed by AB Tasty. Each time the URL changes, the tag checks the targeting criteria to know whether the modifications still need to be applied. If they don’t, the original content is displayed. For CSS additions, we inject custom CSS in the head section of the webpage, using the “!important” tag in order to add and/or override styles.

In addition to that, our tag adds and listens to a Mutation Observer on the whole DOM. Each time a DOM modification is detected and relevant to us, the tag quickly re-applies its changes. A DOM modification is a change in an HTML element regarding its style or structure. We use the window.requestAnimationFrame() feature in the browser in order to interweave our modifications between two versions. With a high refresh rate of 60 times per second, the changes are applied before the human eye can see it, thereby avoiding any flickering effect.

Automatic reload of the framework option

The option of the settings is enabled by default and automatically detects a URL change and reinitialize the AB Tasty framework as if the page had been reloaded. If the page’s status changes while this option is turned enabled, the changes made will be reapplied.

Server-side rendering

When the webpage is rendered on server-side and hydrated on client-side, there might be a conflict if AB Tasty’s changes are applied before the page is fully loaded. We recommend implementing a delay in our tag’s execution and only trigger it when the page is ready.

We provide a that consists of two parts:

• Adding the ̀window.lockABTastyTag` which will tell the tag not to apply the modifications. It needs to be set as soon as possible and before calling the AB Tasty tag.

• Triggering the `window.unlockABTasty()` method provided by the tag itself. This will resume the execution and display the campaigns. It as to be called when you consider the website to be ready.

The AB Tasty Shopify app (Web pixel) is one of the two options we have build to help you integrate AB TAsty in your Shopify workflows. To know more about the two options and decide which one you should use, please refer to the AB Tasty integration with Shopify article.

The AB Tasty extension for Shopify lets you implement the generic AB Tasty tag in your website, using your Shopify admin.

You must be an AB Tasty customer to use the extension. You will need your AB Tasty identifier (the ID of your tag) to complete the installation.

Installation of the AB Tasty extension via the Shopify App store

Step 1: Install the AB Tasty extension

The first step is to install the AB Tasty extension in your Shopify admin.

You can either go directly to the AB Tasty extension using the following link here or search for it in the by typing “AB Tasty”.

Once you find the extension, follow the following steps:

1. Click Install

2. Follow the installation procedure by accepting the set-up

Step 2: Log in to your AB Tasty account

Now that the AB Tasty extension is installed, you need to link it to your AB Tasty account.

To link your account, follow the steps below:

1. Click on the Configure App button.

2. Add your AB Tasty identifier (ID of your tag).

The identifier can be found in your AB Tasty account, in the .

In section 2 of the page, you can directly copy your AB Tasty account identifier in the clipboard.

Once done, paste it in the Shopify app field.

1. (Optional) In the Advanced options section, you can choose to load the Tag Synchronously or Asynchronously and to track on a subdomain. Read to know more.

2. Click Save.

For performance reasons, Shopify recommends using the asynchronous tag : in this case, scripts load simultaneously, which can improve page load speed but may cause flickering as modifications are applied after the page loads. If you encounter flickering effects on your website, you can use the synchronous mode. In this case, scripts are loaded in order, minimizing flickering effects by applying modifications before the website loads.

Your AB Tasty tag is now implemented on your Shopify e-commerce website. All the standard Event Trackers are immediately created in your account, ready to be used in your next campaigns.

Step3: Verify your AB Tasty tag

To ensure that your generic tag is correctly implemented, create an A/B test campaign from the AB Tasty interface. You can then add click trackings that you have selected in the "goals" step, and that you target on all your pages, on all your traffic, and without any particular trigger conditions.

Launch your campaign, then go to the reporting of the test:

• If you see data on your reporting, your tag is correctly set up.

• If no data comes up several minutes after the campaign has been launched, please refer to this , or check that the identifier you have entered is the right one.

When implementing tags, it's possible to restrict their execution to specific subdomains. This ensures that tags will only function on designated subdomains and not on others.

Subdomain Restriction Examples

• Top domain Execution: If you set the tag to "my-website.com," it will execute on all my-website.com subdomain, including eshop.my-website.com and blog.my-website.com.

• Specific Subdomain Execution: Setting the tag to "eshop.my-website.com" will restrict its execution to the "eshop" subdomain. It will not execute on blog.my-website.com.

Suggested readings :

If one or several URL might contain sensitive data as a URL parameter, you can tell the tag to avoid collecting it.

Block simple URL parameter

1. Go to the sensitive data page

2. Set the parameter you want the tag to ignore

   1. for example, input email if you want to remove an email from this sample URL: https://www.mywebsite.com/[email protected] .

3. You can add as many parameters as you need

Block a parameter based on a regular expression

1. Go to the

2. Set the required regular expression that the tag needs to evaluate to ignore a URL parameter

   1. for example, to define the URL https://example.com/url-part-to-hide/other-part, enter the following expression (https?://example.com/).*?(/other-part)

jQuery Library option

By activating this option, the jQuery library will be loaded with the tag.

Note that it's not mandatory to install the library jQuery to make AB Tasty work on your website.

There are three options for configuring jQuery loading in the .

• Load AB Tasty’s jQuery

Compiling your AB Tasty tag enables you to push the modifications you have made to your AB Tasty campaigns (since the previous update) on your website. The tag is updated automatically when you change the status of a campaign but you can also ‘force’ compilation by clicking the tag button in the header of the platform.

Compilation process

The tag compilation process includes 4 major steps. When the tag is being refreshed, you will be able to follow its progress via an animated tooltip.

For many reasons, in particular to see if AB Tasty can cause errors on your website, you can deactivate AB Tasty on your website, meaning emptying the AB Tasty script.

Performing this action deletes the content of the JavaScript file that is normally called to apply the modifications. The AB Tasty tag will still be present on your website, but the file it calls is empty of any JavaScript instructions. Therefore, it cannot cause any errors on your website.

If errors persist on your website after you have emptied the AB Tasty script, you can eliminate AB Tasty from your investigations and look for other sources of errors.

Emptying the script

To empty the AB Tasty library, apply the following steps:

There are different methods and levels to adding JavaScript code on AB Tasty. Select one depending on the scope you need from the JavaScript code. In most cases, you can add JavaScript code in both the visual editor and the code editor.

The various JavaScript codes are executed in the following order:

1. Account JavaScript

2. Campaign JavaScript

3. Element JavaScript

The Next tag is our Early Adopter program for the AB Tasty tag. It is a specific and early branch, where we put our latest optimizations and features that have been internally tested and validated but that are awaiting a more global validation (early adopter feedback) before being deployed to all users.

By joining the program, you will be able to test our latest improvements and new features instantly.

How to join the program?

In the Framework section of your AB Tasty account, you can see which branch of the tag you are on. We currently have 3 branches running:

• Latest: the public and most used branch, referred to as the “default” branch;

• Next: the early and advanced branch you are able to test;

• Unstable: an experimental and internal branch. On a normal use, you will never see this branch.

If your tag is set on Latest, you are free to join the Next program by clicking Learn more and Join now from the popin. However, you can’t join the program on your own if you are on the Deprecated or Unstable branch.

After joining the Next program, you must refresh your tag to push the modifications live. Otherwise, the changes will be pending.

Next tag FAQ

This feature is in the early adoption phase. To benefit from it, please get in touch with your CSM.

The Tag Implementation Page supports two hosting methods:

1. AB Tasty Hosted – Default

2. AB Tasty Delegated

To know how to select a domain and check your implementation, please read the full procedure on .

Some items in your account information are configurable. You can change the account name, configure a time zone, and set a default currency.

These changes can only be carried out if you have administrator rights (admin or super admin role) for the account.

These 3 customizations can be performed from the page Account/ General Information.

Account information

You change the name of the account you are one here.

Timezone

Definition

A timezone is a geographic region within which the same standard time is used.

Time zones tend to follow the boundaries between countries and their subdivisions instead of strictly following longitude, because it is convenient for areas in frequent communication to keep the same time.

All time zones are defined as offsets from Coordinated Universal Time (UTC), ranging from UTC−12:00 to UTC+14:00. The offsets are usually a whole number of hours, but a few zones are offset by an additional 30 or 45 minutes, such as in India, South Australia and Nepal.

Some areas of higher latitude use daylight saving time for about half of the year, typically by adding one hour to local time during spring and summer.

AB Tasty is using the IANA database, which is a collaborative compilation of information about the world's , primarily intended for use with computer programs and operating systems.

Choosing a Timezone for your account

Each account has to be linked to a timezone. If your website is used in several countries or in a country that use several timezones (such as the United States of America), you’ll still need to select one reference timezone to set-up your account.

Main usage of the timezone

The chosen timezone will manage the timestamp for the following main use cases:

Information:

• Start date and hour of a campaign - appears in dashboards and reports

• Pause date and hour of a campaign - appears in dashboards and reports

• The dates and times at which visitors carried out actions on your site are recorded in the reports and displayed as a function of the configured timezone.

Actions:

• Scheduled start date and hour of a campaign - appears in dashboards and reports and triggers the campaign start action

• Scheduled pause date and hour of a campaign - appears in dashboards and reports and triggers the campaign stop action

In general, all the timestamps which are available and displayed into the platform are based on the offset of the selected timezone.

How to change the timezone

You need to select your chosen timezone in the dropdown and it will immediately become your the default timezone of your account.

Currency

You may choose the currency in which you transactions will be displayed in the reports of the campaigns. Make a selection among all the currencies available.

The Visitor Identity Management page allows you to choose how you want to manage the visitor ID. The options are:

• Use AB Tasty’s visitor ID management system

• Manage the visitor ID on your side (BYOID)

Bring your own ID (BYOID) settings

The Bring your own ID (BYOID) option allows you to manage the visitor ID yourself instead of using AB Tasty visitors ID management system.

When you activate BYOID, you will be responsible for generating the visitor ID, storing the visitor ID in a first-party cookie, a JavaScript variable, or local storage, and retrieving the visitor ID from the storage location. You will also be responsible for sharing the visitor ID with AB Tasty so that AB Tasty can track the visitor’s behavior on the website and personalize the website for the visitor.

To activate BYOID, select Manage the visitor ID on your side (BYOID)

Once activated, you can select the three options to manage the visitor ID: - Cookie - JavaScript variable - Local storage

Cookie

You can select this option if you decided to store the visitor IDs in a cookie. In this case, set the cookie name and a pattern to extract the ID from the cookie. Note that you must create the cookie beforehand.

JavaScript variable

You can select this option if you decided to store the visitor IDs in a JavaScript variable. In this case, specify the JavaScript variable name which contains the ID.

Local storage

You can select this option if you decided to store the visitor IDs in the local storage. In this case, specify the local storage variable name and pattern to extract the ID from the local storage.

Migration mode

The migration mode allows you to either use the existing visitor ID until AB Tasty’s cookie expires or immediately switch from AB Tasty’s visitor ID management system to your own ID management.

• Select Toggle ON to keep the existing visitor ID until AB Tasty’s cookie expire.

• Select Toggle OFF to switch to delete all existing visitor ID and switch to BYOID immediately.

We recommend using toggle off to start a fresh visitor ID tracking.

The enables to execute different types of JavaScript files on the website.

To learn more about of these kinds of JavaScript files, please refer to the .

There are different methods and levels to adding JavaScript code on AB Tasty. Select one depending on the scope you need from the JavaScript code. In most cases, you can add JavaScript code in both the visual editor and the code editor.

The various JavaScript codes are executed in the following order:

1. Account JavaScript

2. Campaign JavaScript

Once the is implemented on your website, you need to run it through the QA process. This will ensure that for each purchase, the information is correctly collected by the AB Tasty tag and that the transaction goal is visible on the goal configuration page.

If the transaction tag has been implemented properly, the data should be displayed after a few moment in the report. Otherwise, it means that it has not been installed the right way, and you need to review the code using . The transaction data is not retroactive and available only when the transaction tag has been implemented

There are three different ways to verify the transaction data collection:

• with the QA Assistant,

• with the console’s Network

DOM ready principles

In order to fine-tune when your custom JavaScript is executed within your campaigns, you have the option to choose between two options: when the DOM is ready or before.

When a webpage is loaded, the browser goes through the process of reading the code and creating a representation of the page called the Document Object Model (DOM). The DOM-ready point is when the browser has finished this process and the page is fully loaded and ready to be interacted with.

It makes sure that the page is ready to be used and that all elements can be accessed before the code is executed.

This option can be set up:

Configure the SAML integration

For security reasons, your company may choose to use single sign-on (SSO). This is a unique authentication system that enables you to connect to several platforms using the same email address and password.

AB Tasty lets you implement SSO through SAML 2.0, an open-standard data format for exchanging authentication and authorization information. AB Tasty’s SSO feature allows you to secure your workspace and control your users’ access. All your team members can log in to AB Tasty using one set of sign-in credentials from existing authentication providers. SSO is an email-level feature that will apply across all projects and experiments.

When you use SSO, our platform automatically links AB Tasty to your professional portal.

Before you begin

If your organisation uses Microsoft Entra ID to access applications, you can use it to sign in to AB Tasty as well. To create an AB Tasty application in your Microsoft Entra ID tenant, you must have a Microsoft Entra ID account with one of the following permissions:

• One of the following roles: Global Administrator, Cloud Application Administrator, or Application Administrator.

To use Microsoft Entra ID to access AB Tasty, you first need to add it as a new SAML application within Microsoft Entra ID, then add the connection information for Microsoft Entra ID to AB Tasty.

There are different methods and levels to adding JavaScript code on AB Tasty. Select one of these depending on the JavaScript code you need to execute.

The various JavaScript codes are executed by the tag in the following order:

1. Account JavaScript

2. Campaign JavaScript

3. Variation JavaScript

Specific rule for Element JavaScript: the code is executed once the element is loaded on the page, meaning that this execution can happen at any time, even never.

Where and when do these javascript files run?

• Account JavaScript: on all pages on which the tag is set, after the DOM ready (depends of preferences set-up in the settings)

• Campaign JavaScript: on all the pages where the targeting is valid, on all variations, after the DOM ready (depends on your choices in the editors)

• Variation JavaScript: on all the pages where the targeting is valid, when the visitor is assigned to the variation, after the DOM ready (depends on your choices in the editors)

Where to configure these JavaScript files?

Account JavaScript

Please refer to this to follow the steps to implement account JavaScript.

The AB Tasty tag enables you to inject JavaScript code into your website. At times, you may need to add a JavaScript snippet on all the pages where the AB Tasty tag is present. This could be for different reasons, such as to use it as an analytics catalyst, to add a custom script to be executed on all pages, to connect with third-party tools, or to add a quick patch.

This code is applied to all pages where the AB Tasty tag is present.

You can select to run this JavaScript as soon as the tag is ready or only when the DOM is ready. This means the code will not run until the Document Object Model has been constructed completely, with the initial HTML document loaded and parsed (though without waiting for stylesheets, images, and subframes to finish loading). This option is recommended because your script might need elements on the page that won't be yet loaded on the page when executed. Once done, don't forget to save. Discover more about Window: DOMContentLoaded

Code History

Each time you click Save, the code and its creation date are saved. Once saved, a version of that JavaScript code will be created. Different versions are displayed just below the editing area. It’s possible to roll back each version by selecting it. If necessary, you can reuse a previous version. To do this, simply copy the content of the saved code and paste it into the input window.

The code will be executed on all pages where the AB Tasty tag is present. All the conditions and restrictions need to be set up manually by developers in the code.

Use cases

Using global code is useful if you want to track certain events systematically in all your future campaigns, for example:

• Custom tracking (scroll on a specific page, video fully viewed, etc.)

• Global tracking

• Flag visitors with specific information: cookies, storage variables, etc. (to filter a report or target a new campaign, for example)

• Targeting campaigns by events (to start campaigns manually)

Campaign JavaScript

You can also scope your JavaScript code to one single campaign (it will be executed on all variations and sub-tests of this campaign, including the original version). You can do this in two different environments: visual editor and code editor.

Please refer to this to follow the steps to implement campaign JavaScript.

Use cases

Using Campaign JavaScript is useful to code directly the events you need to track on your campaign, and that are not configurable via the Action Tracking options in the visual editor.

• Custom tracking (scroll on the page, video fully viewed, etc.)

• Action tracking on an element which is not loaded on DOM ready

• etc.

For more information about campaign JavaScript file execution and options, see this specific .

Variation JavaScript

Variation JavaScript is executed in a single variation of a campaign. You can do this in two different environments: visual editor and code editor.

Please refer to this to follow the steps to implement Variation JavaScript.

Use cases

This kind of JavaScript code should not be used to track events at all. It's useful to code your modifications instead of using the wysiwyg capabilities. But it's totally compatible with other modifications in wysiwyg and the usage of widgets.

Element Javascript

You may want to wait for a specific element to exist on the page before you execute your JavaScript. That’s where Element JS could be the right option.

A JavaScript code can also be triggered when an element is present in the . This means the JavaScript code related to that element will run before DOM-ready (before Window: DOMContentLoaded). In this case, the JavaScript code will be executed once the element exists.

Please refer to this to follow the steps to implement Element JavaScript.

Use cases

This kind of JavaScript code should not be used to track events at all. It's useful to code your modifications instead of using the wysiwyg capabilities. But it's totally compatible with other modifications in wysiwyg and the usage of widgets.

Integrating Product Hits is a mandatory step if you want to launch campaigns using segment criteria such as Cart abandonment and Content interest.

To learn more about how to set-up these 2 criteria, please refer to the following article.

AB Tasty lets you save the data related to what kind of product your visitors view and add to their cart during their visits on your website. This integration enables AB Tasty to offer you complementary services to improve your testing and personalization strategy.

Every “hit” integration works the same way, you can follow the same process whether you are interested in using Cart abandonment or Content interest criteria.

Like every JS snippet, you have different ways to proceed with the integration. We will present you three options we consider the best to integrate the hits product script:

• Directly on your website:

• • In your code base

  • Through a tag manager (like GTM for instance)

• From your AB Tasty account, inside the account's global JavaScript menu

To learn more about Product hits and its principles, refer to .

How to integrate Product hits

From your website

We recommend integrating this script directly into your website codebase. You will easily be able to execute it on the right page depending on the context and type of hits you want to send to AB Tasty:

• On every product page for the ‘VIEW’ type of hit product. AB Tasty will receive a precise hit of navigation from your visitors

• As soon as a visitor adds a product to its cart for the ‘CART_ITEM’ type of hit product

• As soon as a visitor initiates a cart for the ‘CART_TOTAL’ type of hit product

You can encapsulate the script given above in the "what to implement" section in the right context that will match your requirements and specificities.

From your AB Tasty account

You can integrate this script from your . The main difference is that it will be executed directly by our tag.

You can integrate the same conditions as you would do with a proper integration in your codebase, but you are not dependent on developers to plan a release as it’s our tag that will execute it on your website.

On the , the basic “hit” integration should look like this:

From your Tag Manager System

If you use a Tag Manager System like Google tag Manager, you can integrate the hit product as every other JS script (like AB Tasty generic tag for example) in this environment. You just need to follow the basic steps - here an example with Google tag Manager:

1. Create a new tag

2. Choose Custom HTML as a tag type

3. Integrate into the “HTML” field the hit product. Do not forget to pass you real variables to replace the values we passed as examples in the documentation. You may have those variables already configured in your GTM, which would make the process quick to proceed with

4. Choose the “triggering” rule to define in which context the script will be called from GTM. We advise firing it on all pages where a user can proceed with an “add to cart” action.

In context example

Here you will find complete codes example that properly respects three essentials to fire the hit product events:

1. Incorporate the hit product JS script, to fill in the right data/variables of your website context

2. Securely wait for the tag to be executed by using a native function that the AB Tasty generic tag will interpret

3. Wait for your add-to-cart event to fire the hit product in the right context

Good to know 💡

AB Tasty gives its customers some solutions to help them with this kind of integration. Please contact your CSM or your main AB Tasty interlocutor, they will be happy to help you with this. We have a dedicated technical team that can help you with this integration, to go further and accompany you until it’s up and running on your website!.

How to check the integration

To verify the integration, you can look into the payload of the "ariane.abtasty.com" request through the network tool:

You will find all the data in a specific index.

Please refer to

Transaction tag generator enables you to implement your transaction tag easily as you just need to indicate where to find the transaction data. The transaction tag will be automatically embedded in the generic tag with no need for creating or modifying any code.

Transaction tag generator enables you to implement your transaction tag easily as you just need to indicate where to find the transaction data. The transaction tag will be automatically embedded in the generic tag with no need for creating or modifying any code.

Benefits:

👉 Debugging is made easier since we have more visibility on what has been set up compared with a code you have to add to your source code or your TMS.

👉 The transaction tag generator is based on data layer variables or CSS selectors you have defined. These parameters are more stable than using a custom code.

Configuration

You can implement your transaction tag using one of the three following methods:

👉: by declaring the variables from your data layer containing the transaction-related information.

👉: by declaring the CSS selectors containing the transaction-related information.

👉: by completineg the code snippet.

To use the data layer mode, you first need to integrate.

Depending on the settings you specified, a JavaScript code is created and will be automatically included in the AB Tasty tag. This code is updated each time the configuration is modified and saved with the tag up-to-date.

First, you need to create an affiliation, which coincides with the name you will give to your transaction tag.

Then, you must specify the URL(s) of your website on which the transaction information is available, such as the confirmation page.

You can create as many affiliations as you want and you can edit and delete them.

You need to select the method with which you want to implement your transaction tag:

Data Layer Mode

The data layer mode enables you to implement your transaction tag based on the variables defined in your data layer.

For each mandatory field, you need to enter the name of the key that will be extracted from the corresponding variable. These keys can be found in your data layer.

For example, to fill in the transaction ID, you need to enter the key corresponding to the transaction ID you configured in your data layer. If the transaction is available in the key order_id with a corresponding value OD564, this means that you need to enter the order_id in the transaction ID field.

Please note that the tag will try its best to automatically format your data to the correct data type, ie. transform a character string into a number, but some specific data conversion will not be possible. You should type in already formatted data rather than let the tag automatically convert them to avoid any issues.

Selector Mode

The selector mode can be used if the transaction data is available directly in the code of your confirmation page. In this case, you need to fill in each field with the corresponding CSS selector that can be used in the document.querySelector function.

The item count number (icn) coincides with the total number of items purchased during the transaction. It can be calculated via three different methods.

Example:

👉 If your key (data layer mode) or selector (selector mode) contains the total number of purchased items, select Default.

In the code example, the key would be items_count (returns 5)

👉 If your key or selector contains unitary purchased items, select Count.

In the code example, the key would be products[] (returns 2) 👉 If your key or selector contains the quantity of each purchased item, select Sum.

In the code example, the key would be products[].quantity (returns 5)

Expert mode

The Expert mode enables you to implement your transaction tag via a JavaScript code. By default, there is a code example that you can edit and replace with your own data, available in your source code or Datalayer. You also need to apply the appropriate format to your values (string, float or integer) as described in our .

The transaction affiliation/name (ta), transaction id (tid), transaction revenue (tr) and item count number (icn) must be declared during transaction tag implementation. The other settings are optional, however we recommend configuring them also in order to enable the application of matching filters in the reports later on.

Adding Purchased Items Data

Information related to the purchased items can be linked to each transaction to apply matching filters in the campaign reports or to use purchase-related targeting criteria.

Purchased items data can be collected via the three available methods: Datalayer, Selector, or Expert.

• First, select Array of items as an optional value and enter the key or selector corresponding to the array of objects of all items purchased during the transaction.

In the above example, all item-related data are stored in the transactionProducts array of the data layer, on the purchase confirmation page.

• Click Add optional value: All the data corresponding to items’ characteristics appear as additional fields where you can insert the data layer key or selector corresponding to the item name, price, quantity, ID, and category:

In this example, on the data layer, the item name can be found in the name key, the ID in the SKU key, and so on.

To add the purchased items data in the Expert mode, apply the following steps:

1. Complete the variable corresponding to “__TRANSACTION _ITEMS_ARRAY__”.

2. Complete all the items characteristics with their corresponding variables in tid, in, ip, iq, ic and iv.

Preview

The preview enables you to verify that your transaction tag has been correctly configured by showing the latest transactions registered on your website.

The Transaction Tag Generator is using universal collect data. This is why, after you have implemented your transaction tag, it may take a few hours for the first transactions to be visible in the preview.

Once the new affiliation has been saved, do not forget to refresh the tag (in the header right) to be sure that all your modifications are taken into account in production.

For each transaction, the values corresponding to the keys you specified in your transaction tag are displayed:

If the preview is still empty after several hours, it probably means that one of the fields has not been implemented correctly. Please, check the URL page and all the fields again to be sure that everything is set up correctly. If not, you should ask your technical team or your dedicated AB Tasty consultant to do it for you.

What is a secure profile?

A secure profile is a profile that does not rely solely on a login and a password. This is why a user who has configured Multi-Factor Authentication (MFA) will be considered secure since additional information required from the user will be asked to login.

MFA means that besides requesting you to sign-in through your login and password, you will also be asked to provide a secret code you will get through other means like an Authenticator app, via email or SMS.

Why is securing your profile mandatory?

One of the main reasons is to prevent yourself from being a victim of a phishing campaign. A phishing campaign aims at retrieving your login and password through fake emails, SMS or a website that will mimic the communications or a product that you are used to. Though, you can usually spot the fakes, they tend to be more and more accurate and it's easier and easier to fall in their traps.

But if you have secured your profile with MFA, they will not be able to log into your account even though they got your login and password since they will still be missing one key component: MFA.

Obviously, if you have a secured profile and you somehow divulged your login and password through a phishing campaign, you should still reset your password as a precaution.

Configuration

You have 3 MFA methods at your disposal:

• Authenticator app

• Email

• SMS

An authenticator app is an application that, once set up, will provide time-based codes to use for the different applications that you linked it to.

Here is a list of several Authenticator apps that you can use:

• Google Authenticator

• Microsoft Authenticator

• Authy

Once you access your AB Tasty account for the first time, you'll have to set-up your MFA entirely.

Activating MFA with an Authenticator app

To activate MFA with an Authenticator app, go to the :

1. Click the Setup MFA CTA

2. Choose App authentication

3. A QR code is displayed;

   • You can either scan it with your Authenticator app or

MFA is now active on your profile. You can download and save the backup codes that are generated for you.

Activating MFA with Email

To activate MFA with Email, follow the steps below:

1. Click the Setup MFA CTA.

2. Choose Email authentication

3. A code is sent to the email address filled in your profile

4. Enter the code in the appropriate field and click Verify.

MFA is now active on your profile. You can download and save the backup codes that are generated for you.

Activating MFA with SMS

To activate MFA with SMS, follow the steps below:

1. Click the Setup MFA CTA.

2. Choose SMS authentication

3. Fill in your phone number. You will receive a code by SMS.

4. Enter the code in the appropriate field and click Verify.

MFA is now active on your profile. You can download and save the backup codes that are generated for you.

Signing-in with MFA

Once the configuration is complete, when logging in to the AB Tasty platform, follow these steps:

1. Sign-in like you are used to with an email and password, through SSO or via Google Sign-in

2. Once done, you will be asked to enter an authentication code

3. Depending on the MFA method you chose, you can either

   1. Get a code from your authenticator app

If you are not able to get a code on Step 3, then you can select the method "Backup code" and try and enter one of your backup codes so you can login.

Good to know You can also check the Don’t ask me again for the next 2 weeks option if your device is fully secured and if you do not want to enter a code on this one specifically for the next 2 weeks.

The Custom pixel is one of the two options we have built to help you integrate AB Tasty in your Shopify workflows. It specifically ensures transactional hits during checkout through Shopify's checkout extensibility. However, you'll still need to inject the AB Tasty tag manually on other pages of your site to capture full user interactions. To learn more about the two options and decide which one you should use, please refer to the article.

To use the extension you must be an AB Tasty customer. To complete the installation, you will need your AB Tasty identifier (the ID of your tag). Your store must use Shopify Hydrogen or another Headless Framework This application works as a standalone

Installation steps

1. Log In Shopify

Definitions

The restrict cookie deposit option enables you to manage the AB Tasty tag’s behavior to comply with regulations and adapt the configuration to user specificities. Since the implementation of the Guidelines on consent under Regulation 2016/679 (GDPR) by the European Data Protection Board on May 4, 2020, you have a legal obligation to ask your visitors for their explicit consent before tracking them and collecting their personal information through the acceptance of a cookie banner (either fully or partially).

Moreover, you must provide proof of this consent and AB Tasty must help you do so.

As soon as consent is given, proof of this consent is automatically sent to AB Tasty’s servers and stored for 13 months.

Stored consent information includes the date and time, the condition and mode used, the visitor ID, and the perimeter.

It remains your full responsibility to implement the cookie banner on your website and make its content compliant with local data protection regulations.

In the page in the settings, you must select one of these three options:

• Not restricting cookie deposits. This means no consent is requested from the visitors and the campaign is automatically displayed and data tracked.

• Managing the consent proper to AB Tasty within a third-party tool, such as a CMS. In this case, the TMS automatically checks the visitor’s consent before triggering the tags it contains. Proof of consent will still be collected; however, the consent will specify that it was collected by an uncited third-party source.

• Delegating the consent to the AB Tasty. In this case, the tag will try to determine whether the visitor gave their consent on the website before tracking them and collecting their data.

For more information about privacy and storage methods, please refer to this reference .

Using your assistant to discover the right deposit method

To help you to choose the right method for your cookie deposit policy, you can trigger our virtual assistant Ally by clicking on Start on the banner.

The tour explains all the options you can choose and the benefits and risks of each of them.

Option 1: Never verify visitor's consent to collect their data

If you select the ‘Do not ask for visitor consent and track data anyway’ option, you won’t ask your visitor’s consent to track their data.

AB Tasty campaigns will be automatically displayed, and all the actions they will perform will be tracked and stored.

No proof of consent will be collected. We don’t recommend selecting this option as it may not comply with your local legislation.

Options 2: Manage consent via a third-party tool

To activate the consent obtained by a third party, just choose the option.

When activating this option, the visitor’s consent is considered to have been given as soon as the tag is executed. The proof of consent will be written in the AB Tasty infrastructure instantly without checking any other trace of consent on the website.

When selecting this option, AB Tasty won’t be responsible for checking the consent of your visitors.

Option 3: Manage visitor consent directly in AB Tasty

Campaign execution restriction

You now need to choose how the tag will operate on your website when the visitor has not given their consent according to the campaign type.

• If you tick a campaign type: campaigns of this type are triggered and the visitor can be assigned to a variation, or to the original version. As data is not tracked, the visitor may see different variations when browsing the website.

• If you don’t tick a campaign type: campaigns of this type are not triggered and the visitor sees the original version.

In both cases, data is neither collected nor stored until consent has been given. Data will be collected as soon as the visitor gives their consent.

Test

• If you tick the box, the visitor may be assigned to a variation, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.

• If you don’t tick the box, the visitor will see the original version so the actions they perform won’t impact the results of the test either.

Personalization

• If you tick the box, the visitor will see the personalization, but the potential actions they perform won’t be collected and stored.

• If you don’t tick the box, the visitor won't see the personalizations.

💡 We recommend ticking this box as you don’t necessarily need to collect data. If a visitor doesn’t give their consent, they will still be able to see the personalization.

Split/redirect campaign

• If you tick the box, the visitor may be assigned to a redirection, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.

• If you don’t tick the box, the visitor won't see the redirection so the actions they perform won’t impact the results of the campaign either.

A/A test

• If you tick the box, the visitor may be assigned to a variation, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.

• If you don’t tick the box, the visitor will see the original version so the actions they perform won’t impact the results of the test either.

Patch

• If you tick the box, the visitor will see the patch, but the potential actions they perform won’t be collected and stored.

• If you don’t tick the box, the visitor won't see the patch.

AB Tasty cookies placement

You now need to choose how AB tasty will determine that a visitor has given their consent and therefore that their actions can be tracked and stored : you need to choose between the following options:

• The user completes an action on the page

• My website deposits its cookies

• A specific cookie is placed

• Didomi consent

The user completes an action on the page

If you choose this option, the consent of the visitor is considered to have been given as soon as the user completes an action on the page (a scroll, a click, or any other action).

My website deposits its own cookies

If you choose this option, the consent of the visitor is considered to have been given if the AB Tasty tag detects any other cookies on the page (from the website itself or a third-party tool).

A specific cookie is placed

Choose this option if your visitor’s consent is stored in a specific cookie. To configure this option, follow these steps:

• Specify the name of your cookie

• Select an option from the drop-down list: contains expression, regular expression or corresponds exactly

• Enter the expected value of your cookie

As soon as the tag is executed, it will seek to confirm this condition and visitor tracking will only begin once consent has effectively been acknowledged. The tag will then conduct regular checks (upon each reload) to ensure the condition is still valid. If not, it will apply the effects specific to the revocation of consent.

Didomi consent

Choose this option if you want visitor consent to be managed by Didomi. Didomi is a Consent Management Platform (CMP) that enables you to manage your vendors (or third-party tools), and their associated purposes, and to configure the way your visitors can consent to data usage.

For more information about the Didomi integration, please refer to the following .

A JavaScript is triggered

Select this option if you manage consent with specific JavaScript events when a visitor has given or revoked their consent. For more information, refer to this .

Custom condition (JavaScript)

Select this option if you want to create a custom JavaScript function to personalize the way consent is given by the visitor. This function must return ‘true’ if the condition is valid and if consent was obtained by the visitor. In this case, the AB Tasty tag will trigger and execute the JS function and start tracking.

The AB Tasty Shopify app (Web pixel) is one of the two options we have build to help you integrate AB TAsty in your Shopify workflows. To know more about the two options and decide which one you should use, please refer to the AB Tasty integration with Shopify article.

To install the app, please read How to implement Shopify app article.

Basic functionalities

Once set-up, the app will allow you to

Retrieve Transaction & Checkout Events from Shopify through our Web Pixel

These events are available on:

• AB tasty reporting

• Data Explorer

Select Shopify custom trackers in the AB Tasty editor to track Shopify standard events.

More than 10 events are automatically added to your custom trackers, (both for FE&R and Web experimentation platforms).

These events can be added as Campaign Goals on the Web experimentation platform.

You can Subscribe / Unsubscribe to any event from Shopify Admin.

Two layers of consent

The Shopify app will only run either

If AB Tasty Tag Consent has been granted / giving it authorization to run in the AB Tasty page. (If you inspect the page, Analytics Should be “true”)

If Shopify Consent has been granted in Shopify in the Customer Privacy API page (if you inspect the page consentReady should be “true”)

If one of these 2 is missing, then web pixels won’t run.

Advanced functionalities

Choose to load the Tag Synchronously or Asynchronously

For performance reasons, Shopify recommends using the asynchronous tag: in this case, scripts load simultaneously, which can improve page load speed but may cause flickering as modifications are applied after the page loads. If you encounter flickering effects on your website, you can use the synchronous mode. In this case, scripts are loaded in order, minimizing flickering effects by applying modifications before the website loads.

Synchronous loading can help reduce flickering effects if it occurs, enhancing the overall user experience on Shopify stores.

To enable one option or the other:

1. Go on AB Tasty app homepage.

2. Click on edit app configuration.

3. Scroll down to advanced options

4. Toggle on or off the Load the Tag synchronously feature.

Track on a subdomain

Even if your checkout workflow is on a subdomain, you can track it. This option will:

• Create a dedicated cookie

• Keep the standard configuration on localstorage

• In case of 2 events sent at the same time, AB Tasty Tag will ensure reconciliation to avoid double-positive

To enable this feature:

1. Go on AB Tasty app homepage.

2. Click on edit app configuration.

3. Scroll down to advanced options

4. Toggle Handle checkout on Subdomain on.

How the Shopify App is functionning?

The AB Tasty generic tag will be placed on all pages of your website, except for checkout pages (by checkout, we mean the whole payment funnel, excluding the shopping cart). This restriction applies to all Shopify partner tools. More information in the Shopify .

This means that you will be able to:

• Test and personalize your entire website, including the shopping cart page, except for checkout pages.

• Track any event on your website, including transactions, since the AB Tasty Shopify app retrieves the Shopify transaction natively. There is no need to install a transaction tag.

The AB Tasty tag or the Shopify app can be blocked by browsers add-ons, privacy settings, etc. Some discrepancies in transactions reports should be expected.

Shopify events

Standard events

With Shopify, you can track a variety of events that occur on your website. Once you have installed the AB Tasty app on Shopify, these events are automatically created.

You can retrieve them in the (in the Custom trackings tab, marked with a Shopify label) of the Web experimentation & Personalization platform. These events can be used as goals for your campaigns from the Goal step of any campaign, under the Custom trackings category to monitor your campaign performance. For more information on goals, refer to

You can't edit, delete or hide a Shopify event from the WE&P interface.

Here is the list of Shopify events available in Web Experimentation & Rollouts:

Checkout events

To track events on the checkout, it is not possible to directly use the AB Tasty tag (which cannot be executed there). For these pages, the extension uses the Shopify API. This way, you'll be able to track, for all your campaigns:

• Transactions and associated metrics: transaction rate, number of visitors who have done at least one transaction, total number of transactions, average basket, number of items per transaction, average item price per transaction, and so on.

The name of the associated transaction goal will be "Purchase".

• The dimensions associated with each transaction: currency, voucher use, payment method, delivery method, and so on.

• Page views: cart page, review page

For other click tracking and custom tracking events, you need to declare the events to be tracked directly in your Shopify admin. See tracker set-up section.

Collecting the "voucher" dimension

If a discount code ("voucher") has been entered by the buyer, it will be sent to data collection and available in AB Tasty reporting. The associated transaction amount will be the one with the discount applied.

Privacy

When using Shopify, privacy is based on the configuration you have set up in the Web Experimentation & Personalization platform ( of the Settings). You don't have to configure anything privacy-related in Shopify. This way, when using Shopify, visitor tracking is consistent and campaigns reliable.

For different purposes, AB Tasty lets you save the data related to what kind of product your visitors view and add to their cart during their visits on your website. This integration enables AB Tasty to offer you complementary services to improve your testing and personalization strategy.

We built two in-house targeting criteria to help our customers to go further in their experimentation and personalization strategy:

• Cart abandonment: these criterion helps our user to target their “abandonist” visitors

• Content interest: this criterion helps identify and target visitors based on their specific interests detected on your website. It can either work through the page title (which it does natively) or through product hits that you can send us if you find it more accurate. The hit product integration will also allow AB Tasty to display some conversion data on content interest audiences.

To make those solutions work, we just need some data that our can not properly detect, read, and interpret. To answer that limitation, we developed a specific JS function, that we call “product hit”, for you to send us the right data in the right context, which we will leverage in the AB Tasty platform to offer you new services (inside the targeting for example).

To send those product data to AB Tasty, you need to add a Javascript script on every product page, while your visitors are doing two types of events: viewing a product (i.e: loading any product page), and adding a product to their cart.

To learn how-to integrate Product hits, refer to .

What to implement for the Cart abandonment criterion

We are going to see how the hit JS event is built, with a quick overview of its key components.

The event uses the ‘window.abtasty.send’ function to call the global ‘abtasty’ object integrated into your website through the generic tag. This is how the collection will work. The script will pass some specific product data to our generic tag to be sent to our data pipeline. From this collection, we can build up services for you to leverage those data.

Inside the script, you will find a list of parameters that you will need to fill in to send us the appropriate data depending on your visitor's context. Some parameters are mandatory for some specific kind of hits, defined by the first parameter, the product interaction type (first line of the following table). Apart from that, to succeed in your implementation, you just need to respect the value type of each parameter and link the right data on your side to the right parameters. Let’s deep dive into each parameter: