Explore these articles for a deeper understanding of the steps needed to create a successful campaign that aligns with your objectives. Each step is tailored to provide control and clarity, allowing users to create, manage, and confirm campaigns effortlessly and efficiently. With AB Tasty, crafting a campaign is simple, whether you're setting up experiments or personalizations for your website or application.

Get a demo

Your other resources

Popular articles

New articles

The dashboard also allows you to filter historical data metrics by date.

To apply a filter, select any of the predefined periods from the top menu of your dashboard:

• Past 12 months: data from the past 12 completed months + current month as a result

• Past 6 months: data from the past 6 completed months + current month as a result

• Past 3 months: data from the past 3 completed months + current month as a result

• Past 30 days: data from the past 30 completed days + current day as a result

• Past 7 days: data from the past 7 completed days + current day as a result

Example Usage

Let's say today is April 4th, 2024, and you want to analyze historical data for the past 3 months.

The Date Range will be automatically set to: January 1st, 2024 - April 4th, 2024 as it provides data from January 1st, 2024, up to April 4th, 2024. It encompasses the entire previous three-month period, including data up to the current date.

If you are in need of inspiration or looking to accelerate your ideation process Evi Ideas is here to help. Evi Ideas is a feature designed to help you generate experiment ideas using AI.

Using generative AI CRO Experimentation Expert Agent, continuously improved to provide best practices, UX guidance, and cognitive bias considerations, Ideas Generator, provide relevant and actionable test ideas from an image or Gif.

Here’s how it works:

The can be customized to better fit your business needs. You can add, delete metric and also re-arrange the dashboard layout.

Add a new metric

On the dashboard:

1. Click on the “Customize” button in the upper-right of your dashboard to enter edit mode.

The Editor in AB Tasty is your main workspace for creating and customizing website experiences—no coding required.

With the Visual Editor, you can simply click on elements on your page to modify text, images, styles, and more, all in real time.

For those who prefer more control, the Code Editor lets you directly edit CSS and JavaScript.

Features like responsive mode, navigation mode, and a library of widgets make it easy to tailor your site for any device or scenario.

Whether you’re making quick changes or building complex variations, the editor is designed to be intuitive and accessible for all users.

Curious to learn more? Explore our articles to help you get the most out of your editing experience

AB Tasty enables you to create several types of campaign according to the hypothesis you want to test:

Tests/ Experimentations:

• A/A test

Personalizations:

You can create a campaign from different locations of the platform.

With the Create Button of the campaign list

The main way to create a campaign is from the campaign list page:

1. Go to the or page.

2. Hover over the Create button.

3. Click on the type of campaign you want to create: You will be redirected to the .

To create a Split Test, you must create an A/B test and activate the redirection option in the visual editor.

If you're not sure which type of campaign to choose, you can use our .

From a library element (widget, segment or trigger)

From a widget

You can create a campaign from a specific widget. In this case, the chosen widget will be added by default in the editor. To do so, apply the following steps:

1. Go to Library > Widgets.

2. Select the widget from which you want to create a campaign and click Use.

3. Select the campaign type and enter a name and URL.

4. Click Go to the editor: The URL of the page you specified will display in the visual editor with the widget already added and ready to be configured.

You can also create a campaign from a widget preset (Presets tab) or from a custom widget (Your widgets tab) by following the same procedure.

From a segment or trigger

You can create a campaign from a specific segment (or trigger). In this case, the segment (or trigger) will be automatically selected in the who section (or how section) of the Targeting step of your campaign. To do so, apply the following step:

1. Go to Library > Segments (or Triggers).

2. Select the segment/trigger from which you want to create a campaign and click the + icon at the end of the line.

3. Select the type of campaign: personalization or test.

4. From the , select the campaign type and enter a name and URL.

With the Chrome extension

AB Tasty has released a Chrome extension to create a campaign directly from your website page.

To download the Chrome extension, please follow this .

For more information about the AB Tasty Chrome extension, please visit our specific section about the Chrome extension in the

This option is useful for loading logged pages.

With the Duplicate option

If you want to duplicate an existing campaign and create a new one (and potentially modify some elements of the original test setup), you can use the Duplicate option in the campaign list.

1. Click on the three dots on the right side of the campaign line you want to duplicate.

2. Click on the first option: Duplicate. The duplication modal opens. From here, you can:

   • Modify the account where you want to create your new campaign.

   • Modify the name of your new campaign (otherwise the name will be the same with

For more information about duplication and transformation use cases, please refer to article.

The uplift card shows the uplift generated by your AB Tasty campaigns on a given month. This information can be analyzed from the ROI dashboard which provides a global overview of your CRO activity and enables you to monitor your campaign’s performance over time.

The uplift is the incremental revenue that would have been generated if the visitors who saw the original version had instead seen the variation, it can be related to the profit made on your campaign. On the opposite, if the uplift is negative, you will find it under the Secured gain section of the ROI dashboard. It corresponds to the revenue you have saved by not implementing an underperforming variation on production.

Information

If you have several transaction tags implemented on your account, you need to choose the one you want to display data for via the drop-down list.

The transaction name coincides with the name assigned to the transaction as it appears in the list of goals to configure and on the reporting. The selection is saved for all the next sessions and displayed by default when you come back to the dashboard. You can still select another transaction name at any time. You can hide the transaction tags you don’t use anymore, for more information, refer to .

Calculation

Uplift = Total Revenue (variation) - Potential Income (original version) The uplift card on campaign dashboards shows:

• The uplift number: the sum of the uplift generated by your tests and personalizations campaigns separately, for a specific account in the current month and on a specific transaction tag you have selected beforehand. This number is based on the currency you have set up in your account settings.

• A graph with the uplift evolution over the past months. On hover, you can see the uplift history over the past 6 months. Data is updated on a daily basis and shows the data up to day-1.

The graph is not displayed when no uplift has been generated for at least two months. To see more data, click the uplift number to be redirected to the .

No uplift

Here are the main reasons why you may not see any uplift on your campaign dashboard:

No transaction tag has been implemented on your account

The uplift calculation is only available on accounts where at least one transaction tag is implemented. To do so, please refer to .

You have just implemented a transaction tag

The uplift calculation is made on a daily basis and aggregated every month. If you have just implemented your transaction tag, the uplift metric will be updated as soon as your campaigns will start collecting data.

The month has just started

If you are looking at the uplift when the month has just started, it probably means that your campaigns’ data have not been aggregated yet and taken into account in the uplift calculation.

You have campaigns running for months, but no uplift recorded on the tag

You have one or several campaigns that have been running for several days and/or months, but you don’t see any uplift generated. It probably means that your campaigns would not make any profit. Depending on the type of campaign, you can consider the following solutions: For test campaigns:

• It can mean that the uplift is negative on your running campaigns, your tests have generated secured gain instead.

• You may consider reviewing your test hypothesis and change your modifications if necessary.

For personalization campaigns:

• You may consider keeping 10% of your visitors on the original version to enable uplift calculation.

No campaigns are currently running on your account

The uplift can’t be calculated when no campaigns are live on your account. The uplift metric will be updated as soon as you will launch at least one campaign and that it will start collecting data.

Use case

Let’s say your uplift card shows 7.5k for the Transaction affiliation in December 2021.

• When clicking the timeframe or “i” icon, you are redirected to the ROI dashboard.

• When hovering the graph on December 2021, you can see that the number displayed is equal to the uplift number displayed on the card.

• When clicking the transaction tag name, you can switch the transaction tag and display its corresponding uplift.

From the ROI dashboard, to retrieve the uplift value, you must select the exact same transaction tag in case you have several transaction tags implemented. If you select several accounts, this value will be different. For more information on the ROI dashboard, refer to .

Campaign duplication is a way of recreating a new campaign based on a previous one, on the same account or on another account to which you also have access.

Find out more about the duplication use case and what a duplication can do in terms of configuration, please refer to this specific article.

To duplicate a campaign, follow these steps:

1. Go to the Test or Personalization dashboard and select the campaign you want to duplicate. The duplication process starts from a specific campaign.

2. To access the duplication feature, click the three dots on the line of the campaign you want to duplicate.

3. Select the Duplicate option from the list.

4. This displays a new pop-in.
5. Choose the destination campaign type: you can either keep the same campaign type (this is what we call an identical duplication) or modify it (this would be a duplication with transformation). Note that A/A tests, Patches, Multipage Patches and Multivariate Tests can only be duplicated in their original campaign types.

6. Select the content to import to your new campaign. Depending on your previous selection, you may have to select the specific variation/experience/page you want to duplicate (in the case of multiple variations/experience campaigns).

7. Select the destination account: it can be the same (by default, your current account is pre-selected)as you’re currently using or any other account you have access to. The list only displays those accounts you have access. You can select up to 5 accounts from this list as destination for your duplication.
8. Optional: Enter a name for your new campaign. By default, your campaign name has the following format: {campaign_original_name_(duplicate)}.

9. Validate by clicking Duplicate. The new duplicate campaign is displayed in its corresponding dashboard (test or personalization) and is paused by default.

Find out more about the duplication use case and what a duplication can do in terms of configuration, please refer .

Welcome to our interactive demo on "How to Use Our Visual Editor." This hands-on experience will guide you through the features and functionalities of our intuitive editor, helping you create and customize your campaigns with ease. If you prefer a detailed description instead of the demo, feel free to check out our comprehensive article: Visual editor discovery.

A Patch or Multipage Patch consists of modifying:

• One or several elements on one page (for example, your homepage, basket page, etc.) or several pages that share the same layout (all your product pages or all your results pages, etc.).

• One or several elements on different pages (for example, your homepage, basket page, etc.) or several pages that share a different layout (all your product pages and all your results pages, etc.).

Patching your website means changing a piece of code to correct an error or to push out an important piece of content or information as soon as possible.

The objective of patching is not experimental or personalization, but only to make a very fast change to a page of your site to fix an error or update something urgent. Therefore, you don't have to set up Goals and it does not generate any reporting.

A Multivariate test enables you to test combinations of changes simultaneously on your website. You can change several elements on a page simultaneously (e.g., the color and wording of a CTA) and identify which of the possible combinations performs best according to the goal you wanted to reach (e.g., increasing the number of clicks, the number of pages viewed, decreasing the bounce rate). You can then apply these changes directly to your website. Unlike an A/B test, which involves testing each hypothesis in a different test, a multivariate test allows you to run hypotheses at the same time and to find the best combination of all. The purpose of multivariate tests is to measure the interactive effects between several supposedly independent elements (e.g. page title and visual illustration). A subtest contains variations that will be tested independently across multiple combinations. For example, if your goal is to test a simple CTA, you might want to create three subtests: Color, Shape, Wording, with as many variations of colors, shapes and wordings as necessary. AB Tasty will create all the possible combinations and display them randomly to your traffic.

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

To create a Multivariate test, go to Web Experimentation, click the Create button and select Multivariate Test.

👉 To learn about the different ways to create a campaign, please refer to .

A Multipage Personalization displays a new experience, message, or piece of content on several different pages of your site that don’t share the same layout – for example on the homepage and the basket page. This new experience, message, or piece of content is shown to a specific segment of visitors to your website and you can track its effectiveness in your campaign reportings.

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

To create a multipage personalization, go to Personalization, click the Create button and select Multipage Personalization.

👉 To learn about the different ways to create a campaign, please refer to .

AB Tasty enables you to configure different campaign types designed to meet various optimization and personalization needs. These campaigns can be categorized into two main pillars: experimentation (tests) and personalization.

If you don’t know which type of campaign to choose, our can help you.

Tests

A/B testing is an activity that consists of challenging or testing, elements of a website to find out whether an alternative will increase engagement and conversions. A/B testing is also a great way to identify the next innovation worth investing in, or for determining what is minimally viable.

AB Tasty offers several types of testing campaigns with your departure hypothesis and what you want to challenge.

An introduction to Ally, your AB Tasty virtual assistant

Ally is your virtual assistant – a module that can guide you towards the right type of campaign for your needs. Ally will pose various questions about your objectives, the type of message or version you want to create, the segment you want to target, and so on. This will help you select the best campaign for your specific objectives. It is important to select the right type of campaign for the following reasons:

• Reports differ according to the type of campaign, as their purpose is to meet the user’s expectations. In order to create the best campaign insights, you need to choose the right type of campaign to begin with.

Shadow DOM is a key technology used in modern web development to create self-contained components. These components are encapsulated, meaning their structure and styles are isolated from the rest of the webpage. This technology is part of the broader Web Components standard, which also includes Custom Elements and HTML Templates. For non-developers like digital marketers or product managers, understanding Shadow DOM helps explain why some tools or integrations, like AB Tasty, might face challenges when interacting with certain web elements.

What is Shadow DOM?

Shadow DOM creates a separate mini webpage within a component on a site. This isolated section has its own styles and scripts that don't interfere with the rest of the page. Similarly, external tools or styles on the main page don't affect what's inside the Shadow DOM.

You can exclude specific IP addresses from your campaigns. Once excluded, visitors coming from those addresses won't see your campaigns and will not be included in your campaign reporting. For example, you may want to exclude specific bots, probes, technical teams or agencies with whom you are collaborating.

Excluding IP addresses

To exclude IP addresses, go to the Settings > Advanced settings > IP exclusions.

You can exclude a single IP address

Or a range of IP addresses

Removing excluded IP addresses

You can also remove previously set exclusions by clicking on the ‘bin’ icon from the exclusion list.

IP exclusions will automatically exclude the specified IP addresses for each new campaign. Campaigns created before the addition or modification of an IP exclusion will not be affected by the modification.

An A/B Test consists of modifying one element on one page (e.g. homepage, basket page, etc.) or a string of equivalent pages that share the same layout (e.g. all of your product pages, all of your results pages, etc.), and measuring if the new variation(s) will be more or less performing than the original.

To learn more about the differences between each type of test, refer to the Types of campaigns article. If you don’t know which type of campaign to choose, our virtual assistant Ally can help you.

To create an A/B test, go to Web Experimentation, click the Create button and select A/B Test.

👉 To learn about the different ways to create a campaign, please refer to How to create a campaign.

Configuration

Step 1: Main information

The Main Information page is the first step toward your new A/B Test campaign.

We recommend establishing a hypothesis of your test according to the following model: If I apply [this change on my webpage] to [this audience], then [it will impact] and enables to enhance [this goal]. And to add it in the hypothesis field.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

You have two ways to create content for your campaign in AB Tasty:

With the visual editor

With the Visual Editor, you can make simple modifications such as changing the color of a button, replacing an image, changing the wording of an element. If it is clickable, always put an action tracking on the element you modify.

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the

With the code editor

The Code Editor enables you to declare your code (JavaScript, CSS) without having to load the Visual Editor. The Code Editor is the best solution for developers who want to save time.

👉 To learn how to use the Code Editor, please read the .

Step 3: Goals

As the primary goal enables you to determine which variation takes precedence over the others, you should choose the action tracking related to the element you have modified. Indeed, it is the user behavior that is more likely to be affected by the modification you have made in the editor.

👉 To learn how to configure Goals, please read .

Step 4: Targeting

You have to declare WHERE your campaign should be visible on your website (e.g. on every page, on specific pages, on only one page, etc.), for WHOM (e.g. your whole traffic, mobile users only, etc.), and in WHICH conditions (e.g. after a certain number of pages, when it’s cold outside, etc.) it should appear. You can also decide WHEN visitors will see the campaign depending on the recurrence you choose.

Be careful when entering the targeted pages (in the Where section) of your test to ensure that it will display correctly on the pages you want to target (e.g. Product pages).

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

By default, traffic allocation is set equally for each variation (50/50 for an A/B test, 33/33/33 for an A/B/C, etc.). For statistical reasons, it is recommended to not make uneven traffic allocation.

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read .

If you want to launch your A/B Test at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

Use cases

A/B tests can be used in the following cases:

A Multi-Experience Personalization displays a new experience, message, or piece of content on one or several different pages (homepage, basket page, etc.), for at least 2 specific segments of visitors to your website. This type of campaign lets you prioritize the different experiences you have created:

• If a visitor matches multiple segments (overlap), they will see only one experience with the highest priority (that you have put in place in the Main information step).

• If a visitor matches only one segment, they will see the experience for which they have been targeted.

• If a visitor does not match any of the segments, they won’t be targeted and thus won’t see the campaign.

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

To create a multi-experience personalization, go to Personalization, click the Create button and select Multiexperience Personalization.

👉 To learn about the different ways to create a campaign, please refer to .

Configuration

First, you need to ask yourself if your campaign may include overlaps. For example, let’s say you plan to create 2 sales popins on your homepage: one to display a coupon code to your VIP visitors, one to display a coupon code for visitors who have purchased within the past month. You need to know which popin you want to display to a visitor who is both a VIP and has purchased within the past month. The most important message will get the “Priority 1”, so that visitors matching both segments (“VIP” and “Last month purchasers”) will see the Priority 1 popin only.

Step 1: Main information

The Main Information page is the first step toward your new campaign.

Choose the right priority for the right message: create each experience based on a specific priority. The most important experience, that is to say the experience that will be seen first, appears at the top (priority 1).

👉 For more information on how to configure this step, refer to .

Step 2: Editor

You have two ways to create content for your campaign in AB Tasty:

With the visual editor

Each experience must display a specific message to a specific segment. If it is clickable, always put an action tracking on the element you add in order to follow the performance of your campaign (ex: cross to close the popin, CTA in the popin etc.). Don’t forget to put action trackings on each experience (for each popin for example, with a different name: “Click cross popin VIP” and “Click cross popin NYC”).

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the

With the code editor

The Code Editor enables you to declare your code (JavaScript, CSS) without having to load the Visual Editor. The Code Editor is the best solution for developers who want to save time.

👉 To learn how to use the Code Editor, please read the .

Step 3: Goals

Once you’ve created your Personalization, you can pre-configure your future reporting to identify easily the metrics that need to be followed as your primary goal (the one which is potentially the most impacted by your Personalization).

👉 To learn how to configure Goals, please read .

Step 4: Targeting

WHO section: this is the most important section, where you have to choose the right segment as a function of the message you have created in the editor.

WHERE section: the target page must be the same for all experiences.

HOW section: this step is optional. You can add specific session-based triggers, such as a required number of viewed pages before displaying a message, the landing page of the session and so on.

The segment and/or the trigger must be different for each experience: in our example, you can create a VIP segment for the Priority 1 experience and a Past month purchasers for the Priority 2 experience.

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

If you allocate 100% of your traffic to the experiences, you won’t be able to know what the increment of each experience (in terms of purchases, for example) is. We recommend leaving 10 to 15% of your traffic on the original version (depending on the amount of traffic on your website). Don’t forget to set up traffic allocation for each experience of your campaign (in our example, for both experiences).

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read .

If you want to launch your campaign at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

Use cases

Multi-experience personalizations can be used in the following cases:

A redirect test (or split test) enables you to test the performance of a new page, created and hosted outside of AB Tasty. This page is used as a variation within an A/B test campaign.

This type of test is useful when modifications involve a significant amount of work (e.g.: a brand-new design).

In this case, 2 URLs are involved:

• The source URL, that is to say the one corresponding to the original version. This is the URL from which you want your visitors to be redirected.

• The destination URL, that is to say the new page used as a variation. This is the page the visitors will be redirected to when they land on the source URL.

As in a classic A/B test, after analyzing the results of your test, you will see if the destination URL has performed better than your original version depending on the goal you wanted to reach (e.g., increasing the number of clicks, the number of pages viewed, decreasing the bounce rate).

A Split Test is a type of A/B test. To create a Split Test, you must create an A/B test (go to Web Experimentation, click the Create button and select A/B Test) and activate the Redirection option from the visual editor.

👉 To learn about the different ways to create a campaign, please refer to .

Configuration

Step 1: Main information

The Main Information page is the first step toward your new Split campaign.

We recommend establishing a hypothesis of your test according to the following model: If I apply [this change on my webpage] to [this audience], then [it will impact] and enables to enhance [this goal]. And to add it in the hypothesis field.

In the URL field, enter the URL you want to load in the editor. This URL corresponds to the source URL. It’s important if you want to set up trackings on this page, such as action trackings.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

To run a Split test, you don’t need to create any specific content. The objective of this setup is to use the classic A/B test campaign workflow to activate a redirection of traffic from the former page (the original) to the new one(s) (the variations).

Variation 1 corresponds to the redirect page. To create the redirection, click on Variation 1 in the header navigation and select the redirect option. You can then paste the URL of the page you want to redirect to in the popin.

We recommend ticking the following boxes:

• Check the accessibility of the page - This option automatically pauses the test when the redirected URL is no longer online (with an email alert to the admins of the account). Once your landing page is available again, another email will be sent and you will be able to play the test again.

• Keep AT Internet referrer in URL - If you use AT internet, this will ensure that you keep the original URL.

• Enable redirection - This option allows AB Tasty to perform the redirection. You must select it. If you want to redirect to several pages, you can select the Regular expression option and enter the regular expression in the URL field.

In a redirected variation, you cannot add Variation JavaScript or make changes. Turning an existing variation (with changes) into a redirection variation deletes all the changes. Only action trackings can be added as they are not specific to a single variation but to the whole campaign.

👉 To learn more about the redirection option of the visual editor, please read the

Step 3: Goals

As primary and/or secondary goals, you can choose action trackings which are common to the original variation and to the new page. For example: if your Split Test consists of testing a new landing page layout, your primary goal should be the bounce rate, along with optional secondary goals.

As the URL of the original version of your page is different from its variations, the code will probably be different. If you want to track clicks on the main CTA of both pages, follow these steps:

• First, add action tracking to the original page. You can access the original page in the editor – it’s displayed by default in the Original tab in the top banner of the visual editor. As with every tracker, AB Tasty will try to detect the presence of the tracked element in both the original and the variation pages, even if this element is present on only one of the two.

• Next, do the same for the variation you want to test. If you return to the Variation tab, you will see the original version of your page – that’s normal; it’s because you’ve used this URL in the Main Information Page. To load the new one, go back to the Main Information Page and paste the new URL in the field named URL to load in the editor, and click save. Then go back to the editor. Your new page will be loaded in the Variation tab.

For the most efficient workflow in setting up an A/B test, list all your metrics and their trackers on a separate sheet or document (for example metric “click rate”, so tracker “click tracking on the element #mainCTA). Then implement all the trackers in the original variation, before finally implementing them all in the variation. Each time, you can copy and paste the tracker names from the list, to ensure none are overlooked and your associated metrics will have the same names. This is necessary to ensure all relevant data is collected under the same KPI in your campaign report.

👉 To learn how to configure Goals, please read .

Step 4: Targeting

You have to declare WHERE your campaign should be visible on your website (e.g. on every page, on specific pages, on only one page, etc.), for WHOM (e.g. your whole traffic, mobile users only, etc.), and in WHICH conditions (e.g. after a certain number of pages, when it’s cold outside, etc.) it should appear. You can also decide WHEN visitors will see the campaign depending on the recurrence you choose.

You must target the source URL.

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

Traffic allocation must be identical for each variation.

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read .

If you want to launch your A/B Test at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

If the AB Tasty tag is not implemented on the page which you want your visitors to be redirected to, they will be able to view the page but no data will appear on the reporting of your campaign.

A Multipage test enables you to test a new version of one or several elements across a user’s journey, that is to say on different pages which don’t share the same structure (such as the homepage, the product pages and the basket page). These element(s) may have different layouts depending on page structure. As for A/B tests, after analyzing the results of your test, you need to decide which version has performed best according to the goal you wanted to reach (e.g., increasing the number of clicks, the number of pages viewed, decreasing the bounce rate). You can then apply these changes directly to your website.

To create a multipage test, go to Web Experimentation, click the Create button and select Multipage Test.

👉 To learn about the different ways to create a campaign, please refer to How to create a campaign.

Configuration

Step 1: Main information

The Main Information page is the first step toward your new Multipage Test campaign.

We recommend establishing a hypothesis of your test according to the following model: If I apply [this change on my webpage] to [this audience], then [it will impact] and enables to enhance [this goal]. And to add it in the hypothesis field.

In the Pages section, enter the URL you want to load in the editor for each page or group of pages. Each page coincides with a part of the user's journey you want to test. You need to include at least 2 pages which must be different (e.g.,: the product pages and the basket page).

👉 For more information on how to configure this step, refer to .

Step 2: Editor

You have two ways to create content for your campaign in AB Tasty:

With the visual editor

You must adapt the modification to each page you have configured. Each page has the same number of variations, as you build an entire new user’s journey. If it is clickable, always put an action tracking on the element you add or modify in order to follow the performance of your campaign (e.g.,: cross to close the popin, CTA in the popin etc.). Don’t forget to put these action trackings on each page.

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the

With the code editor

The Code Editor enables you to declare your code (JavaScript, CSS) without having to load the Visual Editor. The Code Editor is the best solution for developers who want to save time.

👉 To learn how to use the Code Editor, please read the

Step 3: Goals

As the primary goal enables you to determine which variation takes precedence over the others, for Multipage tests, exceptionally, your primary goal should be the result of the user’s journey, regarding the main goal of your test: retention (primary goal should be the number of viewed pages), loyalty (revisit rate) or conversion (transaction rate). You should also choose the action tracking related to the elements you have modified as secondary goals. Indeed, this is the user behavior that is most likely to be affected by the modification you have made in the editor.

👉 To learn how to configure Goals, please read

Step 4: Targeting

You have to declare WHERE your campaign should be visible on your website (e.g. on every page, on specific pages, on only one page, etc.), for WHOM (e.g. your whole traffic, mobile users only, etc.), and in WHICH conditions (e.g. after a certain number of pages, when it’s cold outside, etc.) it should appear. You can also decide WHEN visitors will see the campaign depending on the recurrence you choose.

The target pages (Where section)must be different for each page, as they relate to a specific step in the user’s journey. The segment(s) (Who section) must be the same for each page. Don’t forget to configure the targeting for each page. If one or several sections (Who, Where, How) have the same configuration, you can use the .

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

By default, traffic allocation is set equally for each variation (50/50 for an A/B test, 33/33/33 for an A/B/C, etc.). For statistical reasons, it is recommended to not make uneven traffic allocation.

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read .

If you want to launch your A/B Test at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

Use cases

Multipage tests can be used in the following cases:

An A/A test is a type of campaign that enables you to gather insights about your website by tracking events or specific behaviors using the AB Tasty tag.

This is a type of test for which:

• The traffic allocation is 0% on the original version and 100% on the variation.

• The variation is empty: you don’t create any new content to push, so the campaign is totally transparent for your visitors.

• You have set up goals to follow in the reporting.

So, what’s the point of an A/A Test?

• Gathering baseline data: All market analytics tools track events differently (technologically and also in the way they calculate certain metrics). Thus, it’s normal to observe differences between the metrics displayed by two different analytics tools. With an A/A Test, you can collect your visitors’ main KPIs using AB Tasty and establish a baseline to analyze your future campaigns more accurately.

• Analyzing before and after revamp: If you’re planning a large revamp of an important feature on your website and can’t A/B test the two versions, it’s important to have a record of the previous performance of this feature. For example, let’s say you want to change the structure of your navigation bar. If you launch an A/A Test before the release, you’ll get the exact click rates for each tab. After the revamp, another A/A Test will enable you to collect the new click rates on the new tabs and, after several weeks, you’ll be able to measure the impact of your release on the navigation behavior.

• Adding click zones or segment performance:

To learn more about the differences between each type of test, refer to the article. If you don’t know which type of campaign to choose, can help you.

To create an A/A test, go to Web Experimentation, click the Create button and select A/A Test.

👉 To learn about the different ways to create a campaign, please refer to .

Configuration

Step 1: Main information

The Main Information page is the first step toward your new A/A Test campaign.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

As the A/A test objective is not to change content of your website but to gather data and insights, you can still use the Visual Editor but only to create trackers.

In the Editor, you can add trackers to your campaign, such as click trackings, custom trackers and widget trackers.

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the

Step 3: Goals

Once you’ve set up your trackers, you can preconfigure your future reporting to easily identify the metrics needed to track your primary goal. The notions of primary and secondary goals are not significant with A/A Tests because the objective here is to recall all the trackers you’ve set-up in the editor.

Once your campaign has started, you can add secondary goals, but action tracker such as clicks or widgets won’t be retroactive in your reporting and will be calculated from the date you added these metrics as goals. All the other goals will be calculated from the date you launched your A/A Test, even if you add them afterward.

By default, A/A Test will embed some goals like:

• Transaction Goal

• Bounce Rate

• Number of pages viewed

• Revisit Rate

The Transaction Goal will be set as the Primary Goal if you have a transaction tag implemented. If not the bounce rate will.

👉 To learn how to configure Goals, please read .

Step 4: Targeting

You have to declare WHERE your campaign should be visible on your website (e.g. on every page, on specific pages, on only one page, etc.), for WHOM (e.g. your whole traffic, mobile users only, etc.), and in WHICH conditions (e.g. after a certain number of pages, when it’s cold outside, etc.) it should appear. However, you can't change WHEN visitors will see the campaign depending on the recurrence as the A/A test will be instantly trigger.

Be careful when entering the targeted pages (in the Where section) of your test to ensure that it will display correctly on the pages you want to target (e.g. Product pages).

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

By default, traffic allocation it is locked to 100% of your traffic to the variation.

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracker you applied 👉 To learn how to use the QA Assistant, please read .

If you want to launch your A/A Test at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

A Simple Personalization consists of displaying a new experience, message, or content on one page (e.g. homepage, basket page, etc.) or a string of equivalent pages that share the same layout (all your product pages, all your results pages, etc.) for a specific segment of visitors of your website. You can measure the performance of your campaign in the reportings.

To learn more about the differences between each type of test, refer to the Types of campaigns article. If you don’t know which type of campaign to choose, our virtual assistant Ally can help you.

To create a simple personalization, go to Personalization, click the Create button and select Simple Personalization.

👉 To learn about the different ways to create a campaign, please refer to How to create a campaign.

Configuration

Step 1: Main information

The Main Information page is the first step toward your new campaign.

👉 For more information on how to configure this step, refer to .

Step 2: Editor

You have two ways to create content for your campaign in AB Tasty:

With the visual editor

The Visual Editor enables you to create the personalized experience you want to push on your website for a specific segment.

👉 To learn how to use the Visual Editor, discover options, and dive into our widget libraries, please read the

With the code editor

The Code Editor enables you to declare your code (JavaScript, CSS) without having to load the Visual Editor. The Code Editor is the best solution for developers who want to save time.

👉 To learn how to use the Code Editor, please read the .

Step 3: Goals

Once you’ve created your Personalization, you can pre-configure your future reporting to identify easily the metrics that need to be followed as your primary goal (the one which is potentially the most impacted by your Personalization).

👉 To learn how to configure Goals, please read .

Step 4: Targeting

WHO section: this is the most important section, where you have to choose the right segment as a function of the message you have created in the editor.

WHERE section: choose the unique URL (or a saved Page) or the type of pages having the same construction (such as Product pages) on which your message will be visible. The URL used in the editor step remains a sample of the URL(s) you configure in this step.

HOW section: this step is optional. You can add specific session-based triggers, such as a required number of viewed pages before displaying a message, the landing page of the session and so on.

👉 To learn how to configure targeting, please read .

Step 5: Traffic allocation

If you allocate 100% of your traffic to your experience, you won’t be able to make a comparison with the original version. We recommend leaving 20 to 30% of your traffic on the original version (depending on the amount of traffic on your website) to be able to control the performance of your experience.

👉 To learn how to configure Traffic allocation, please read .

Step 6: Advanced options

The advanced options are not mandatory.

• Enable the third party tool(s) you have connected to AB Tasty to send your test data to your tool.

• Select a loading method for your campaign.

• Activate Sequential testing to detect if your experiment will not be successful at all based on the results of your primary goal (if it is based on a Conversion/Transaction Rate).

👉 To learn how to configure Advanced options, please read .

Step 7: QA

The QA of the campaign is one of the most important steps before launching your campaign into production. The QA allows you to verify and test in real condition :

- the targeting configuration - the tracking - the modifications you've made

👉 To learn how to use the QA Assistant, please read .

If you want to launch your campaign at a specific hour on a specific day, and/or if you want to pause it at a specific hour on a specific day, see our guide on

Use cases

Simple personalizations can be used in the following cases:

When you configure a campaign, you must define the way your campaign will load on the visitor’s website. Your campaign can be either embedded directly in the tag or downloaded only when required. This option has a direct impact on the tag performance.

Configuration

To determine how the campaign will load on your visitor’s website, you must select one of these 2 options:

• Deferred loading

Deferred loading

This option is selected by default. The loading of your campaign is deferred, meaning that it will be downloaded afterwards, only when the targeting conditions are met and won’t be embedded in the AB Tasty tag. Once downloaded, the campaign will behave as usual. Therefore, the campaign won’t add weight to the tag, which avoids impacting the loading time of your website and slowing it down. This is particularly useful when you are running several experiments at a time on your account.

When selecting this option, the additional loading time should not exceed a few dozen milliseconds. When using this option, the targeting of every live campaign is still embedded in the tag. The tag will evaluate as fast as possible which campaigns the visitor needs to be exposed to (the campaigns where the visitor matches and respects the triggering conditions, if any), but will only download the deferred campaigns when they need to be applied. For example, if your campaign is targeted for mobile users only, it is not necessary to download it for desktop users.

Instant loading

When selecting this option, your campaign code, including the modifications, targeting, analytics, widgets, and so on, will be embedded directly into the AB Tasty tag. This means that all your visitors, even those who are not targeted by the campaign, will download its content. Selecting this option can drastically increase the size of the tag, and thus have a negative impact on its performance, especially if it is used in many heavy campaigns. We recommend using it only for very specific use cases (for instance when configuring a redirect test) and for a short period of time.

When changing the loading of a campaign, you must refresh the tag.

Use cases

Let’s say you have configured a campaign displaying a pop-in promoting your latest mobile application and targeting your mobile users only:

• If you select the deferred loading (default): The campaign will be downloaded and executed only for targeted visitors (in this case, for visitors on a mobile device). After an initial download from our servers cache, the campaign will be cached for 1 year (if no modifications are made) in the visitor browser for an instant loading each time the visitor sees the campaign.

• If you select the instant loading: The campaign will be downloaded for all visitors but executed only for those matching the targeting conditions. It will be cached in the tag for 30 seconds. A heavy campaign can add several KB of data for each visitor that will re-download the campaign when the cache expires (after 30 seconds). This may increase the execution time of the AB Tasty tag.

The Dwell Time Tracking widget is part of the Tracking widget category. For more information on the widgets, please refer to Widgets configuration in the visual editor.

Introduction

The Dwell Time Tracking widget enables you to track the time your visitors spend on a page. Visitors who reach a given duration will be grouped under this duration goal.

For example, you can create three separate goals in one single widget.

Let's say: 10 seconds, 60 seconds, and 180 seconds. You will see in the reporting for each goal, how many visitors reached it.

This will give you an idea of the time your visitors spend on a single page, whether it is a content page with a long scroll or a simple task-oriented page (or group of pages, depending on your targeting criteria).

In theory, you should always have a higher number of reached goals for the shortest durations and a lower number of reached goals for the longest durations.

Configuration

To configure the widget:

1. Give it a name (for the Goals setup step and the Reporting),

2. Define a duration (make sure to name it accordingly),

3. Save. To use more than one goal, add them into the same tracking widget (by clicking "Add a setting") instead of adding another tracking widget. If you added one by mistake or if you would like to remove one inside a tracking widget, just click on the red cross to delete it.

In order for your goal(s) to be displayed in your campaign reports, you need to add them as main or secondary goals. For more on the goal configuration step, refer to the

To avoid creating conflicts within your campaign's reporting data, we recommend adding a single widget in which all your dwell time goals will be defined.

To enable a fair comparison, event tracking widgets are applied to the original version and to the campaign variation(s).

The Element Visible Tracking widget is part of the Tracking widget category. For more information on the widgets, please refer to Widgets configuration in the visual editor.

Introduction

The Element Visible Tracking widget enables you to track whether one element (an image, a button, a paragraph, a div, a section, a collapsible div, etc.) has been "visible" in the viewport of the visitor.

There are several possibilities:

• the element is visible above the "fold line" at page load,

• the element is only visible once the visitor has scrolled to a certain point and suddenly appears in the viewport (triggered when the element starts to be visible and is not fully visible, for example, a large <div> or an image),

• the element is hidden and is only displayed after a click (or any other user behavior).

In all of these cases, we collect a hit. Once an element has been made visible in the viewport, reading it and re-displaying it will not count it twice. However, if the visitor reloads the page and the element is visible again, a new hit is sent.

If you have a responsive website, it is probably more convenient to use the Element Visible Tracking widget instead of the Scroll Rate Tracking widget, which will consider a scroll rate the same way for visitors on desktop and on mobile.

Depending on how your website is designed and/or the device you use, you may see an element or not, without this being related to the scroll progression.

You can nevertheless use the Scroll Rate Tracking widget in two different campaigns, each one targeted on a per-visitor device basis.

Configuration

To configure the widget:

1. Select the element you want to track,

2. Give it a name (for the Goals setup step and the Reporting),

3. Save.

To use more than one goal, add more in the same tracking widget (by clicking "Add a setting") instead of adding another tracking widget. If you added one by mistake or if you would like to remove one inside a tracking widget, just click on the red cross to delete it.

In order for your goal(s) to be displayed in your campaign reports, you need to add them as main or secondary goals. For more on the goal configuration step, refer to the

To enable a fair comparison, event tracking widgets are applied to the original version and to the campaign variation(s).

The campaigns dashboards are available for both Experimentation & Personalization campaigns. The experimentation campaigns dashboard includes all the tests (A/B tests, A/A tests, multivariate tests, multipages tests, tests with dynamic allocation) and patch and multipages patch campaigns created on the website of the account and the personalization campaigns dashboard includes all personalizations campaigns (simple personalizations, multipages personalizations, multiexperiences personalizations) created on the website of the account. By default, the first 12 campaigns are loaded in the list. To show more, click on the other pages at the bottom right of the list.

To access the test and patch dashboard, click Experimentation from the lateral navigation.

To access the personalization dashboard, click Personalization from the lateral navigation.

It is important to add trackers in order to track how visitors respond to the changes you make on your website.

For example, if you change the color of a button, you’ll need to track the clicks on it.

Add a tracker

Select the element you want to track and click on Add Tracker.

How to edit Shadow DOM in the visual editor

This guide will walk you through the process of editing Shadow DOM elements using the visual editor. is a powerful feature that allows for encapsulation of DOM and CSS, creating self-contained components. With the latest updates, our visual editor now supports editing these elements, enhancing your ability to personalize and experiment with modern web technologies.

This guide will walk you through the process of editing Shadow DOM elements using the visual editor. is a powerful feature that allows for encapsulation of DOM and CSS, creating self-contained components. With the latest updates, our visual editor now supports editing these elements, enhancing your ability to personalize and experiment with modern web technologies.

Prerequisites

Before you begin, ensure that:

• You have access to the visual editor with the Shadow DOM feature enabled.

The Virtual Click widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Virtual Click widget will help you virtually click on an element on the page to save your visitors the hassle. This click will happen at page load.

It can be used in many different ways, such as clicking to hide a panel, display a pop-in, pre-filter results, accept conditions, tick a checkbox...anything you would like your visitors to do but can't force them to do, or anything you would like to save your visitors from doing.

It can be very convenient once a decision for an evolution has been made, and you would like to implement it as soon as possible without having to wait for the development to be in production.

Definitions

A Redirect Test/Personalization (or Split Test/Personalization) enables you to test or personalize a new page created and hosted outside of AB Tasty.

This page is used as the entire variation or scenario within a campaign.

Two URLs are involved:

• The source URL

The Banner widget is part of the Promotional Content widget category. For more information on the widgets, please refer to .

Introduction

The Banner widget enables you to display a banner and possibly a button linking to a specific URL. Images can be added as background images.

This guide will walk you through the process of editing iframe elements using the visual editor. are HTML elements that allow you to embed content from another web page within your current page. With the latest updates, our visual editor supports editing these elements, enhancing your ability to manage and customize embedded content.

Prerequisites

Before you begin, ensure that:

• You have access to the visual editor with iframe editing capabilities enabled.

The Sticky Element widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Sticky Element widget helps you keep important elements in the viewport of your visitors. This limits confusion and reminds them of the main expected task for each page.

For example, on product pages, it can be the "Add to Cart" button, on travel websites, the "Book Now" button, on SaaS apps, the "Save" button, and so on.

The Comment feature allows you and all stakeholders to communicate on your campaigns. This will facilitate collaboration with your colleagues (when working on common campaigns) and help you keep track of key information inside AB Tasty.

You can access the Comment feature by clicking on any test or personalization campaign. All comments are managed at campaign level.

The comment menu is located in the upper-right corner of your campaign’s creation flow (except the Visual editor) and in the reporting.

The number of comments posted in your campaign will be displayed next to the comment button. A red icon indicates what there are unread comments. You can list them by clicking on the Comments button.

You can post comments as internal notes or to send a comment to someone and notify them. This can be done by tagging them in your comments using the ‘@’ sign followed by their name. The tagged user will also receive an email notifying them that they have been tagged in a comment post. The email contains a URL link that redirects the user to the step where the comment has been posted.

Comments can also be deleted. While the comment’s content will be deleted, the event will remain in the comment history.

The Snowflake Animation widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Snowflake Animation widget enables you to simulate snow falling on any element of the web page with an icon of your choice.

It can be useful to add playfulness to your website during a specific time of year (Christmas, Halloween, Thanksgiving, Valentine's Day, your company anniversary and so on) or to highlight a specific section of the page.

The Celebrate widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Celebrate widget enables you to place an icon of your choice on any element of the web page.

This can be useful:

• to add playfulness to your website during holiday season,

We've updated the Visual Editor with a fresh look that aligns with our company's branding. This includes new colors, fonts, and icons for a more modern and consistent experience.

The Quick-Action Bar

When you select an element, the Quick-Action Bar appears just below it, offering shortcuts to the most frequently used actions. This allows you to perform common edits without needing to open the full context menu.

The standard actions include:

The Scroll Rate Tracking widget is part of the Tracking widget category. For more information on the widgets, please refer to .

Introduction

The Scroll Rate Tracking widget enables you to set one or more scroll goals on a web page.

Once the scroll threshold has been reached by a visitor, a goal is recorded in the report. If a user scrolls down, reaches a goal, scrolls back up and scrolls down again, the hit is not sent twice.

If they refresh the page and reach the scroll rate goal, a new hit is sent.

If you have a responsive website, it is probably more convenient to use the Element Visible Tracking widget instead of the Scroll Rate Tracking widget, which will consider a scroll rate the same way for visitors on desktop and on mobile.

The Social Sharing widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Social Sharing widget lets you display a sidebar (left, right, top, bottom of the page) on pages where you would like your visitors to share content on social media or via email.

The Search & Replace widget is part of the Special widget category. For more information on the widgets, please refer to .

Introduction

The Search & Replace widget will help you replace all the occurrences of a word or a group of words on a page.

This is useful, for instance, for A/B testing a change in wording or microcopy, or simply to replace an old product name with a new one, or even the name of the former CEO with the new one.

The impact of this widget on your text is visible in the editor directly.

The global dashboard is the first page displayed when you access your AB Tasty account and allows you to keep track of your C.R.O campaign's performance.

The dashboard keeps track of 10 main indicators:

• Live campaigns

• Campaign status overview

• Campaign launch

Customizable dashboard

You can by choosing which card you want to display and its exact place.\

Date filters

You can change the timeline by choosing between several options, from the past 12 months to the past 7 days.

Please refer to

Single account vs Multiple account view

Single-account view

The single-account view mode is the default mode and displays data for a single account.

Multi-account view

The multi-account view mode displays aggregated data of all accounts within an . Multi-account view mode is activated automatically when you select several accounts in your organization.

To select multiple accounts, in the upper right corner of the Dashboard, click on the drop-down menu.

You must be a super admin of your organization to be able to select several accounts.

Campaigns activity metrics

The dashboard shows real-time and historical tracking of your campaigns' activity.

Campaigns are split by category and type where applicable.

Live Campaigns

This section shows the total number of campaigns currently running on your AB Tasty account or organization. It is the sum of campaigns with live or live in QA status. It'a "real time" card, meaning that the usage of the date filter can't impact it.

Status Overview

This section provides a 2 steps overview status. First it gives a brief summary of activity by status. Second, clicking on a status reveals more details about the associated campaign types. Additionally, selecting a specific campaign type will redirect you to a filtered campaign list.

If a campaign type does not appear in the list, it means there are no campaigns of that type in the current status.

Campaign launch

This section shows the total number of times campaigns have been launched in the past 12 months. It is calculated by the sum of launches that took place, excluding campaigns in QA mode and counting only 1 launch per day per campaign at maximum.

Upcoming scheduled campaigns

This section shows real-time updates on your scheduled campaigns of your account or organization.

It includes the list of:

• All paused campaigns ready to be launched on a future date

• All live campaigns planned to be stopped on a future date

• All campaigns with recurring scheduled options that didn’t hit the last occurrence

The dot next to the campaign name informs about the current status:

• in green the campaign is live

• in yellow the campaign is paused

The information area resumes the next action scheduled on the campaign. The color of this area is linked to the type of the action:

• in yellow the campaign has been scheduled to be paused

• in green the campaign has been scheduled to be played and paused

• in blue the campaign has been scheduled with a recurrency

By hovering the information area you'll find the full details about the schedule. By clicking on the pictogram on the right of the line, you're redirected to the campaign flow.

10 most active collaborators

This section shows the list of the 10 most active users on your AB Tasty account or organization with their:

• First name

• Last name

• Number of connexions till the beginning

• The last connexion date

As a user, it is possible to declare you first name and last name in the . If these fields are not completed, the email address is automatically displayed for both fields. An active user is a user whose last login time to AB Tasty was in the past 12 months. Users are sorted by number of connections, in descending order.

Unique visitors

This section shows two metrics:

1. All: The total number of unique visitors tracked by the AB Tasty tag, regardless of whether they are assigned to a campaign. This should be equivalent to the MAU (Monthly Active Users) count as we count a visitor once it has accepted the cookies.

2. Tested: The total number of unique visitors (new) tracked by the AB Tasty tag, and assigned to a campaign.

By hovering the graph, you can access to the monthly details.

Performance metrics

Tag size

The tag size is the size of AB Tasty HTML tag, in kilobytes. Its size should be under 125 Kilobytes for optimal performance. For more information, go to the article.

Integrations metrics

Your are listed in the Global dashboard as Connected Apps:

You can access the from this section.

Experiment Health Check

Experiment Health Check enhances the reliability and efficiency of experimentation programs. Experiment Health Check automatically monitors your experiments, providing alerts and insights to help you maintain the integrity of your data.

Types of Alerts

• : This alert indicates a discrepancy between expected and observed traffic allocations. It’s crucial to address SRM to maintain the validity of your test results.

• : Alerts you to potential statistical anomalies that may arise from improper sequential testing practices.

You can mark all alerts as resolved or check them individually by hovering on the elements or headers.

EmotionsAI Key Insights

This card allows you to have a glance at the main information of a Journey Analysis request you have made on the .

The card displays the information of the saved Journey Analysis for which the end date is the closest to today.

You will find there a lot of condensed information to assess the emotional performance of your website :

• Estimated Losses on the period

• The Top 3 EmotionsAI audiences composing your traffic.

• The Top 3 Dissatisfactions by EmotionsAI audiences to manage.

• The Top 3 pages where most emotional improvements have to be addressed.

Depending on the Journey Analysis available, you will be able to filter the Journey Mapping and its goals you want to monitor.

Real time vs. Historical metrics

The Global Experience dashboard tracks 3 types of data: Real-time, Historical and Specific.

Real-time metrics

Real-time data metrics are identified by a “Real time” icon and label placed on top of the section. Real-time metrics cannot be filtered by date.

Historical metrics

Historical data are identified by a “Filter” icon followed by a date range. Those data are updated every day and can be filtered up to the past 12 months.

Specific

The card fetch data on a period specific to the card.

Iframes, or inline frames, are HTML elements that allow embedding one web page within another. They are commonly used to integrate external content like advertisements, videos, or widgets into a webpage. However, as a digital marketer or product manager using AB Tasty, understanding how iframes work is crucial. Iframes can impact user experience and tracking capabilities, often presenting challenges for implementing optimizations and collecting analytics.

What is an iframe?

An iframe is an HTML element that creates a separate browsing context within a webpage, effectively embedding another HTML document. This embedded content can come from the same domain or a different one, enabling diverse content integration but also introducing complexities for tools that rely on manipulating or tracking page elements.

Key attributes of Iframes:

• src: Specifies the URL of the document to embed. This determines what content is displayed inside the iframe.

• width and height: Define the iframe’s dimensions, either in pixels or percentages.

• sandbox: Adds security restrictions on iframe content, limiting capabilities like script execution or form submission.

• allow: Lists features that the iframe is allowed to use, such as autoplay or camera access.

Why might users encounter iframes?

Iframes are widely used by websites to embed external content seamlessly. For example:

• Videos: Embedding YouTube or Vimeo videos.

• Interactive maps: Displaying Google Maps on a webpage.

• Third-Party widgets: Integrating chat systems, social media feeds, or surveys.

Common Scenarios in AB Tasty:

1. Embedded content in target pages: When running experiments or personalizations on a webpage, certain sections of the page may exist inside iframes.

2. Third-Party tools: Platforms like YouTube or external booking engines often use iframes, meaning those areas might not be directly editable by AB Tasty.

3. Cross-Domain restrictions: If an iframe points to an external domain, browser security policies might block scripts or interactions within the iframe.

Challenges Iframes present for AB Tasty Users

Content Integration and Isolation

Iframes create isolated environments where the embedded content operates independently of the parent page. While this ensures that scripts and styles from the parent page don’t interfere with the iframe’s content (and vice versa), it also means that tools like AB Tasty may face restrictions:

• You may not be able to directly edit or test the content inside the iframe.

• Scripts injected by AB Tasty might not work within the iframe due to its isolated context.

Security restrictions

Many iframes use the sandbox attribute to restrict actions like running JavaScript or accessing cookies. While this enhances security for the page owner, it limits tracking and modifications by third-party tools.

Cross-origin content

When iframes load content from a different domain (cross-origin), browsers enforce strict security policies (e.g., CORS). These policies often block access to the iframe's content, making it difficult for tools like AB Tasty to track user behavior or apply visual changes inside the iframe.

Example: How an Iframe works

Here’s a simple example of embedding a YouTube video using an iframe:

In this case, the embedded video is entirely controlled by YouTube, and tools like AB Tasty cannot directly access or modify the content inside the iframe.

Why this matters for AB Tasty users

Impact on experimentation and personalization

1. Limited modifications: If your target content is within an iframe, AB Tasty might not be able to modify it directly unless the iframe is hosted on the same domain and does not have restrictive settings.

2. Tracking challenges: User interactions (e.g., clicks or form submissions) within an iframe may not be captured by default.

Potential workarounds

• Collaborate with developers: Ask developers to avoid using iframes for critical content or ensure that iframes are configured to allow interaction (e.g., same-origin policy, no sandbox restrictions).

• Custom tracking solutions: For iframes that must remain, custom solutions may be needed to track user actions, such as implementing event listeners at the iframe level.

• Custom tracking solutions: For iframes that must remain, custom solutions may be needed to track user actions, such as implementing event listeners at the iframe level.

The Drawer widget is part of the Promotional Content widget category. For more information on the widgets, please refer to Widgets configuration in the visual editor.

Introduction

The Drawer widget allows you to incorporate a dynamic element into your variations. The drawer appears as a tab (referred to as the "Sticky Button") affixed to one edge of the screen, presenting a headline (and optionally an icon) to invite visitors to click on it. If clicked, a panel will unfold from the edge of the screen to present content to the visitor.

Similar to other widgets offered by the platform, extensive configuration options enable you to define what you want to present to your visitors within this experience.

Configuration

Layout tab

In addition to the typical sizing and layer definition configurations, the layout section allows you to define two positions for the widget. The "Button layout" section describes the positioning of the drawer tab precisely on the site, and consequently, the direction in which the drawer will unfold upon clicking (a tab on the left implies the drawer unfolds to the right, a tab at the top implies a downward unfolding, and so on).

The "Layout" section more conventionally describes the organization of elements presented within the content itself.

The content section provides options to present text elements as well as an image. It is worth noting, however, that the drawer offers the option to work with "Text only" or "Image only" content if the experience requires it.

Content tab

The content configuration also allows you to define the content of both the tab (Sticky Button) and the drawer itself.

For the Sticky Button, the configuration involves defining the text displayed to the user and optionally an icon if desired.

For the drawer part, the content configuration is relatively similar to that of an Image Popin. You can define the elements you want to display to your visitors and configure them. Thus, it is possible to choose whether the drawer will present a title and text. You can also configure the content of these elements and the image to be displayed.

Finally, still in the content section, it is possible to configure the button or buttons offered to visitors as well as their behavior (closing the widget, redirection, etc.).

Style tab

Similarly, the style configuration allows adaptation for both the Sticky Button and the drawer itself.

The configuration of the Sticky Button is quite similar to that of a button in other widgets. Colors, borders, and texts can be adjusted to the context of the site where the widget will be deployed.

Note that in the case of the Sticky Button, a position configuration is offered. This allows you to define the position of the tab in relation to the drawer itself: in the middle, at the top, at the bottom, or across the entire length of the drawer.

For the container section, typical widget configurations can be performed: texts, colors, buttons, and borders can be adapted to the context of the site on which the widget will be deployed.

Conditions tab

Finally, analogous to other widgets, the condition parameters allow you to define the conditions for appearance, recurrence, and the animation of the widget's appearance on the page.

What is the replicate targeting option

The Replicate targeting option enables you to copy the targeting configuration of a subtest or a scenario and to paste it into other subtest(s) or scenario(s). It's available on Multipages Tests, Multipages Personalizations and Multiexperiences Personalizations.

The option is available on the top right of the page.

It saves you from having to configure targeting independently for each scenario and each subtest and allows you to save time.

What is the replicate targeting option

To use the Replicate targeting option, you must configure targeting for at least one subtest/scenario first. It can be any subtest/scenario. To replicate one or several sections of this subtest/scenario to one or several subtests/scenarios, select the sections of the current subtest/scenario you want to copy. It can be the Who, Where, How sections. You can also select all sections if you want to replicate the whole targeting configuration of your current subtest/scenario.

Use cases

The Replicate targeting options is available for the following campaign types:

• usually, the Who (segment of visitors) and How (triggering rules) sections are the same for all subtests. Only the targeted pages (Where section) differ. We recommend configuring the Who and How sections in the first subtest, before replicating them directly in all subtests. Then, you can configure the Where section independently for each subtest.

• : the targeting configuration must be exactly the same in all subtests. We recommend configuring targeting in the first subtest, and replicating it directly in all subtests.

• : usually ,the Where and How sections are the same in all scenarios

Let’s say you plan to display a promotional message on the Homepage, the product pages and cart page for clients who purchased more than 5 times in the past year (20% discount) and for clients who purchased less than 5 times in the past year (15% discount). In this case, your personalization campaign is made up of two scenarios. First, configure targeting for the first scenario as follows: Who: Purchase Frequency > The visitor purchased more than 5 times within 365 days. Where: is > http://yourwebsite.com/homepage | is > http://yourwebsite.com/product | is > http://yourwebsite.com/basket How: Any time Then, click Replicate targeting from the current scenario (1) and select the Where and How sections. Select All scenarios (as you only have two scenarios) and click Apply. Go to scenario 2 and configure the Who section: Purchase Frequency > The visitor purchased less than 5 times within 365 days. Click Save step.

A trigger is a temporary user condition that enables you to display your campaign in a specific context. The trigger enables the campaign to be displayed to the configured audience only when additional conditions are met.

Where to create triggers

You can create triggers in 2 areas of the platform:

• in the targeting step of the campaign creation flow, inside the segment selection dropdown, by clicking on Create new trigger:

• from the by clicking on Create trigger

How to use the trigger builder

In both cases, the trigger builder opens:

From there, you will find a list of criteria categories that will help you define your trigger. Click the chevron to access specific options for that category.

Drag and drop your criteria from the left panel list to the working area on the right.

Each criterion will present different specificities. Fill in the requested fields depending on the trigger criteria you selected (see below for additional explanations on each criterion), and how you want to target your visitors.

With some criteria, you can add more conditions to your targeting by clicking Add conditions.

You can combine two or more criteria using AND or OR values found inside the trigger builder’s middle column:

• AND means your campaign will only be shown to a visitor if ALL of the selected trigger criteria are met (more information in the section below)

• OR means your campaign will be shown to a visitor if at least ONE of the selected trigger criteria is met

Don’t forget to name your trigger in the specific name field, found above the configuration space. Click Save to save to retrieve it in your trigger library.

The available triggering criteria

If you need more information about the available criteria to build your triggers (how they exactly work), please refer to our .

The Iframe Click Tracking widget is part of the Tracking widget category. For more information on the widgets, please refer to Widgets configuration in the visual editor.

Introduction

The Iframe Click Tracking widget enables you to record clicks in an iframe (an HTML element that lets you display content from another web page - the same website or another one).

For example, YouTube videos are displayed in an iframe when you embed them in your website. It is pretty much the same thing for any web app that lets you embed a part of or the full content of a page. Generally speaking, except for websites that forbid it, any web page can be embedded in an iframe.

Configuration

To configure the widget:

1. Give it a name (for the Goals setup step and the Reporting),

2. Select the <iframe> element you would like to track (use the Select Parent or Select Children option to select the right element if needed),

3. Save.

To use more than one goal, add them to the same tracking widget (by clicking on the "+" button) instead of adding another tracking widget. If you added one by mistake or if you would like to remove one inside of a tracking widget, just click on the red cross to delete it.

In order for your goal(s) to be displayed in your campaign reports, you need to add them as main or secondary goals. For more on the goal configuration step, refer to the

If you want to track clicks in several iframes on your page, you will need to add one widget per iframe.

To enable a fair comparison, event tracking widgets are applied to the original version and to the campaign variation(s).

The Tooltip widget is part of the Promotional Content widget category. For more information on the widgets, please refer to Widgets configuration in the visual editor.

Introduction

The Tooltip widget lets you display a tooltip on one or more elements.

Tooltips are useful in many different situations: as soon as you notice friction points, you can start improving by adding a simple tooltip. Very often, this will quickly relieve users of a painful experience or upgrade a confusing interface.

Configuration

Layout tab

• Select the element which you want to trigger and display a tooltip on.

• Select the position which the tooltip is displayed on: left side, right side, top, bottom. Default is top.

• Select the most suitable layout depending on the design of your web app or the amount of text you need to provide in your tooltip: "Simple" or "Rich".

Content tab

• Type a Title in the "Title" text area.

• If you've selected the "Title & Text" layout in the layout tab, add a text in the "Text" text area.

Style tab

• The Text color will be applied to both Title and Copy. We recommend picking a light color.

• The Background color is black by default. We recommend picking the most contrasted background based on your text color. If most of your website has a light background, use a dark color for your tooltip backgrounds. A tooltip must be clear and very readable.

• Border color, thickness, and radius settings will help you adapt the tooltip to your website style and make it seamless.

• Drop shadow and drop shadow blur radius: you can decide to add a drop shadow and adjust its opacity.

Background can be set up with an image using the image-fitting policy

4 options are provided:

• "Cover": the image is resized keeping the aspect ratio to fill the background container even if, by doing this resize, the image may overflow the background container.

• "Contains": the image is resized keeping the aspect ratio so that the whole image is included in the background container (no overflow)

• "Fill": the image is resized to fill the background container without keeping the aspect ratio

• "None": the image is left unchanged.

Conditions tab

You can choose whether you want to display your tooltip when clicking or hovering (hover does not work on touch devices).

You can choose to display the tooltip by default at page load. We do not recommend using several tooltips, as this can quickly become overwhelming and stressful for your visitors.

You can choose whether the tooltip will be displayed only once per page or every single time the trigger is triggered.

You can use the Tooltip widget as a pseudo-onboarder and add several in one page. In this case, we recommend triggering each one only once per page. This way, once the visitor has finished clicking in the different "new" areas, they can start really using the website without making the tooltips pop again. If you use tooltips as legends for images, links, etc., we recommend not limiting the trigger to once per page.

A segment is a cluster of visitors that share some identical traits, as defined by you, though sessions. Visitors who match these segment criteria are the only ones who will see the campaign on your website. For more information about segments, please refer to the following tutorial.

Where to create your Segments

You can create segments in 2 areas of the platform:

• in the of the campaign creation flow, inside the segment selection dropdown, by clicking on Create new segment:

• from the by clicking on Create segment:

How to use the Segment builder

In both cases, the Segment builder opens:

From there, you will find a list of criteria categories that will help you define your segment. Click the chevron to access specific options for that category.

Drag and drop your criteria from the left panel list to the working area on the right.

Each criterion will present different specificities. Fill in the requested fields depending on the segment criteria you selected (see below for additional explanations on each criterion), and how you want to target your visitors.

With some criteria, you can add more conditions to your targeting by clicking Add conditions.

You can combine two or more criteria using AND or OR values found inside the segment builder’s middle column:

• AND means your campaign will only be shown to a visitor if ALL of the selected segment criteria are met (more information in the section below)

• OR means your campaign will be shown to a visitor if at least ONE of the selected segment criteria is met

Don’t forget to name your segment in the specific name field, found above the configuration space. Click Save to use the segment in your campaign and save it to your account library. It will now be reusable in other campaigns (see Using a saved segment, below).

Click Cancel to go back to the targeting page without saving. Note: this will erase your current configuration.

If you have created and saved a new segment, it will be automatically available in your segment list.

The available segmentation criteria

If you need more information about the available criteria to build your segments (how they exactly work), please refer to our .

Introduction

Evi Content is an AI-powered tool designed to simplify the process of creating and modifying website experiences using natural language prompts. Evi is primarily designed for users who wish to modify their campaigns but are not familiar with editing code, or wish to improve their text content. This tutorial will guide you through the steps of using this feature effectively.

The Simple Popin widget is part of the Promotional Content widget category. For more information on the widgets, please refer to .

Introduction

The Simple Pop-in widget lets you display a pop-in containing a text. This widget can be useful if you want to catch your visitor’s attention on a specific piece of information, momentum or important message. It can be used for many different use cases. Maintenance operations, crisis communication, or even for seasonal greetings.

You'll find all useful information about what is personalization prioritization in this .

Using this module means to steps:

Prioritization is possible for all personalization campaign types : (SP), (MPP), (MEP).

Once you’ve created your variation(s), you need to pre-configure your future reporting to easily identify the metric(s) that you want to track as your primary goal and (optional) secondary goals.

Definitions

A goal is a metric that has been chosen to monitor your experimentations or personalizations and helps you make informed decision-making about your campaign.

The Goals step enables you to select goals from a list of metrics (which can be created and managed in the or in the ).

These trackers are divided into 5 different categories:

When creating a test or a personalization campaign, you need to define the percentage of visitors assigned to the variation(s) (in case of a test) or scenario(s) (in case of a personalization) and to the original version of your website.

To learn about the traffic allocation step of the campaign creation flow, refer to .\

Allocation system

For each individual visitor, we compute what we call a seed, a unique alphanumeric string that will be persistent in time. This seed, also unique for each campaign, will be used to generate a score between 1 and 100 and then the same logic as before applies.

As the seed is computed each time, we do not need to store the result anymore.

The Code Editor is an alternative to the visual editor to quickly and easily make CSS and/or JavaScript-based changes to your campaign. As in the visual editor, you can add, rename, delete a variation or duplicate an existing one.

The Code Editor is available for all types of campaigns, except the A/A test.

Accessing the Code Editor

When you create a campaign, in the step Main Information, you have the option to load the Code Editor instead of the visual editor. You can also switch to the Code editor from the Visual editor by clicking the "Switch to Code editor" button.

The Action button widget is part of the Promotional Content widget category. For more information on the widgets, please refer to .

Introduction

The Action button widget allows you to incorporate a dynamic element into your variations that executes when the button is clicked.

Those elements are: