Targeting Guide

The Targeting step will allow you to define the conditions in which your campaign will be displayed. 

In this guide, you will learn how to define:

• Who: The SEGMENT who should or shouldn’t see the campaign:
• Where: On which PAGES of your website the campaign should be visible
• How: The browsing and contextual conditions that need to be met to TRIGGER the campaign
• When: The frequency at which the campaign will be displayed to the targeted audience
• Verification: Option to let the AB Tasty tag recheck the condition(s) at regular intervals
• Specific options: Replicate targeting and Add to targeting

1. Where to find the Targeting configuration

Targeting is a step inside the campaign creation flow. You have several options to access it. 

👉 From your existing campaign list, in the Experimentation or Personalization menu.

Hovering over each test, you can access the Targeting configuration by clicking the pen icon and choosing “targeting” from the list (step 2 for Personalizations, step 4 for Tests)

👉 When designing a new campaign.

When you create a new campaign, you will have to define the Targeting configuration. You can access it as soon as you start creating a new campaign (step 2 for Personalizations, step 4 for Tests).

2. Defining a segment 

A segment is a cluster of visitors that share some identical traits, defined by you. Those who match the segment criteria are the only ones who will see the campaign.

Where to set up your segment

• From the audience page, click on the CTA “New Segment”. You can:
  
• Create your segment from scratch
  
• Use a pre-built segment template from the Template gallery.
  You can also access this from the tab in the green header
  
  

• From the Test or Personalization dashboards, click , then Targeting. You can also access this targeting panel when configuring a campaign (step 2 for personalizations, step 4 for tests).

How to set up your segment in the campaign flow

Important to know⚡️: The segment applies to your whole A/B Test, meaning the original variation (V0) and all the variations (V1, V2, and V3 for an A/B/C/D test, for example).
e.g. “target your campaign on your engaged visitors only”
The A/B Test will be triggered only if AB Tasty recognizes the trait “engaged”, with a random chance for visitors to see the original, V1, V2, or V3.

Single-page Experiences vs. Multipage Experiences

👉For A/B Tests, Simple Personalizations, and Patches, you’ll have to define one single segment for your campaign because these types of campaigns have only one “experience” (one type of new content generated with AB Tasty to display).

👉 For Multipage Tests, Multivariate Tests, Multipage Personalizations, and Multi-experience Personalizations, you’ll have to define a segment for each “experience”. This rule can be the same or different depending on your needs. 

• For Multipage Tests and Personalizations, we call the experiences “Pages”
  
• For Multi-experience Personalizations, we call the experiences “Experiences”
  
• For Multivariate Tests, we call the experiences “Sub-tests”

⭐️  Best practices :

• Use the same segment on Multipage Tests, Multipage Personalizations, and Multivariate Tests, to ensure the continuity and visibility of all experiences during the visitors’ navigation.
  
• Use a different segment on every experience of your Multi-experience Personalization campaign since the objective of this kind of campaign is to display different messages to different segment audiences while preserving the rule of one visitor/one message, even for visitors who match several segments. For more information about these campaigns, you can read the guide to personalization.
  

❗️In any case: Don’t forget to use the dropdown menu on the Targeting page to switch between experiences and set up your segment for every experience

We also offer a “Replicate” option, which allows you to replicate the full targeting setup or one part of the targeting setup of one experience in another experience, or in all experiences.

For more information refer to this section.

Using the dropdown menu

The dropdown menu will present you with several of these three options:

• The “All Visitors” option (native pre-selected option)
  
• The list of segments you have already created (account level), if the account has already some
  
• The option to create a new segment (at the bottom)

Using no segment - targeting the campaign to all visitors 

The first time you access the targeting section of your campaign, the “All Visitors” option is selected by default in the How the Test/Personalization/Sub-test/Experience/Page panel.

This means no specific segment is defined and the campaign will display for all your visitors.

Creating a new segment

To create a new segment, take these steps:

1. Select Create New Segment from the dropdown menu (last option)

2. The Segment Builder opens

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

4. Fill in the specific requested fields depending on the segment criteria you selected (see below for additional explanations on each criterion)

5. You can combine your criteria with AND or OR 

1. • OR means that your campaign will be shown to a visitor if at least ONE of the selected segment criterion is met
     
   • AND means that your campaign will only be shown to a visitor if ALL of the selected segment criteria are met (more information in the section below)
     

6. Name your segment

7. Click on Save to use the segment in your campaign and save it to your account library. This way it will be reusable in other campaigns (see section Using a Saved Segment)

8. Click on Cancel to go back to the targeting page without saving anything

If you created a new segment, it will be automatically selected in the dropdown: the segment setup is now complete.

You can save your Targeting configuration by clicking on Save on the bottom right.
For more details on each criterion please refer to our guide about segment criteria. 

Using a saved segment

If you want to use a segment that has already been configured, you can find it directly in the dropdown list:

Click on it to select it for your campaign: the segment setup is now complete.
You can save your Targeting configuration by clicking on Save on the bottom right.

Managing your saved segments

If you want to edit, duplicate or delete an existing segment, you can do so directly from the dropdown menu: 

• Click on the pen icon and you will open the Segment Builder. You can then modify the name of your segment and/or its configuration. Click Save to record your changes.
  

📎  Note: If your segment is already used in a live campaign or is live in QA, you won’t be able to save your modifications. In this specific case, you’ll get a yellow disclaimer with the details of the campaign(s) that is (are) using the segment and that is (are) currently live or live in QA.

In this case, you can: 

• • Pause the ongoing campaign(s) to edit the segment: you can edit and save it 
    
  • Duplicate the segment to have a new one with the same configuration
    

• By clicking on the trash icon, a prevention pop-in will ask you if you’re sure you want to delete the selected segment. Click Delete to delete, or click Cancel to return to the previous screen. 
  
  

• By clicking on Duplicate, the selected segment will be duplicated and will appear just after the selected one in your dropdown list
  
  

❗️Important: You can’t delete a segment that is already used in a live campaign or is live in a QA campaign. You need to pause the campaign(s) that use(s) the segment to be able to delete the segment from your account.

How the segment criteria work

Easily build a new segment by clicking on the Create button at the bottom of the dropdown in the segment section. Open the Segment Builder and play with the segment criteria.

Discover our complete guide to segment criteria by visiting the Segment Criteria page.

3. Defining targeted page(s)

Configuring the targeted pages of your website means specifying the page(s) for which the changes made via the variation editor will be seen by your visitors. This configuration is made inside the targeting interface, on the same page as the segment configuration, in the “where” section. 

How to set up your targeted pages in the campaign flow

Important to know ⚡️: The targeted pages apply to your whole A/B Test, meaning the original variation (V0) and all the variations (V1, V2, and V3 for an A/B/C/D test, for example).
e.g. “target the campaign on the Homepage only”
The A/B Test will be displayed on the URL of the homepage each time a visitor lands on it, with a random chance to see the original, V1, V2, or V3.

Single-page Experiences vs Multipage Experiences

👉For A/B Tests, Simple Personalizations, and Patches, you’ll have to define one single targeted page rule for your campaign because these types of campaigns have only one “experience” (one type of new content generated with AB Tasty to display).

👉 For Multipage Tests, Multivariate Tests, Multipage Personalizations, and Multi-experience Personalizations, you’ll have to define a targeted pages rule for each “experience”. This rule can be the same or different depending on your needs. 

• For Multipage Tests and Personalizations, we call the experiences “Pages”
  
• For Multi-experience Personalizations, we call the experiences “Experiences”
  
• For Multivariate Tests, we call the experiences “Sub-tests”

⭐️ Best practices: 

• Use different targeted pages for Multipage Tests and Multipage Personalizations. This is the objective of these kinds of campaigns: displaying several different messages (the experiences, to create a relevant and complete user journey) on several different targeted pages.
  
• Use the same targeted pages for Multivariate tests if you’re testing a combination of several changes on the same page and try to discover the better combination (color of the CTA, small style banner, new product carousel on a product page)
  
• Use the same targeted pages for Multiexperience Personalizations: this kind of campaign has been designed to help you to launch several messages to different segments in the same campaign and to assure no overlap between messages. To learn more about them, please refer to this article

❗️In any case: Don’t forget to use the dropdown menu on the Targeting page to switch between experiences to set up your targeted pages in every experience.

We also offer a “Replicate” option, which allows you to replicate the full targeting setup or one part of the targeting setup of one experience in another experience, or in all experiences. 

Discovering the options to target pages

When you land on the page, you’ll find the following: 

• The option to set up your targeted pages with the URLs directly (the best way to do it is if the URL of your website reflects its content)
  
• The URL you’ve used in the Main Information page loaded in the Visual Editor is pre-pasted in the URL field
• Additional options: CSS selector and Code

❗️Be careful: the URL field is case sensitive (i.e. a targeting 'contains' 'CHECKOUT' will not affect visitors on a URL like 'https://abtasty.com/checkout/' to the campaign).

Using the dropdown to work with URLs

The dropdown will present you with several options, in this order:

• Inclusive operators: is, is exactly, contains, is regular expression, and is saved page
  
• Exclusive operators: is not, is not exactly, does not contain, is not regular expression, and is not saved page
  
• Target All URLs
  
  

Using Target All URLs

Targeting all URLs will target your campaign on all your website pages where the AB Tasty generic tag has been installed.

Caution: If you have several sub-domains for all of the languages or countries you’re addressing, your campaign will be displayed on all of them. Use this option with caution, if you are sure that your campaign should be targeted on 100% of the pages of your domain. 

Details about inclusive and exclusive operators

This is the matrix about the way the operators work: 

Inclusion(s) only

If you include one or several specific URL(s), all the other URLs will automatically be excluded from the targeting. At least one of them has to match.

Combination of inclusions and exclusions

You can combine inclusive operator(s) (is, is exactly, contains, is regular expression) with the exclusive operator(s) (is not, is not exactly, does not contain, is not a regular expression). 

In this case, to be accepted in the targeting, a website’s URL has to match:

• All the exclusion rules
  
• Some (at least one) of the inclusion rules
  

For example, to target all the pages of your website except product pages, apply the following steps:

1. Select contains → http://mydomain.com.
   
2. Click Add Condition.
   
3. Select “does not contain” → /product/

Heads up ⚡

You add multiple URLs at the same time by copying/pasting those inside the same field, separated by a space. We will recognize each URL independently and add them inside your targeting configuration in the right way, on the same operator. 

🗒 Use case : 

Here are some examples of configuration, depending on the pages of your website you want to target:

Using saved pages

From the dropdown, you can access the list of the pages you’ve previously set up in the page builder. For that, you just have to select the following operator: 

• Is saved Page 
  
• Is not saved Page 
  

You can access the page builder by clicking on “Manage Saved Pages”.

Please refer to this article for more information. 

Useful tip: You can see the setup of your saved pages by hovering over them: 

You can directly click on the saved page you want to include/exclude by using the dedicated “is saved page” option in the previous dropdown. 

You can mix the inclusion of saved pages with the exclusion of saved pages by clicking on “Add Condition”. 

You can also mix saved pages with custom URLs. 

In any case, the functional rules between inclusions and exclusions are the same for the setup by URLs: 

Inclusion(s) only

If you include one or several specific URL(s) and saved pages, all the other URLs will automatically be excluded from the targeting. At least one of them has to match.

Exclusion(s) only

If you exclude one or several specific URL(s) and saved pages, all the other URLs will automatically be included in your targeting configuration.

Combination of inclusions and exclusions
You can combine inclusive rules with exclusive rules. 

In this case, to be accepted in the targeting, a website’s URL has to match:

• All the exclusion rules
  
• At least one of the inclusion rules

Using the CSS selector option

Use the CSS selector option if you want to display changes on the pages of your website containing an element linked to a specific ID or class, whose presence cannot be determined by a URL. It is useful for targeting a set of pages that don't share a specific URL structure. 

You can choose between the ID of your element, the CSS class, or any other parameters (custom choice in the dropdown). If the element you want to declare exists on the page you’ve loaded in the editor, it will appear while beginning to fill in the field by auto-completion.

❗️Caution: Don’t forget to add a ‘.’ for a class or a “#’ for an ID. 

This option is compatible with other options in the section, except for the Target All URLs option.

Important ⚡️: When you use this option with targeted URLs, the operator between both options will be AND.  Meaning that the targeted pages will have to respect both rules in the targeted URLs section and the class option section. 

Using code option

The code-based option enables you to insert JavaScript code to trigger a campaign depending on the presence of a specific JS instruction.
This option is compatible with other options in the section, except for the Target All URLs option.

When using this option, you must comply with the following rules:

• Do not use a function (){ at the beginning of your code.
• The function/condition you code must return a true or false value.
• If you plan to use jQuery, you must enable the use of jQuery in Settings. In this case, go to Account Management → Framework and select Load AB Tasty’s jQuery.

Targeting verification

When this option is in use, some elements can be called after the page has been initially loaded, or after the visitor carries out a certain action. In this case, the targeting conditions must be verified at regular intervals until they are met.

You can either (1) select the AJAX option: the targeting code will be executed only when your code returns true.

Or (2) use promises with the abResolve keyword, which is better for performance purposes.

Triggering your whole campaign by event

In some instances, you might want to launch a test after a user completes a certain action on your site, for example, after they have clicked a certain button, or after they have spent a certain length of time on a given page.
You can condition a test in this way using the JavaScript function ABTastyStartTest. This function takes a single, unique parameter: the ID of the test you would like to launch. It must be called after the AB Tasty tag.
The function takes the following form:

ABTastyStartTest(testID); // 

Where testID is the ID of the test to be launched.

This function must be called as soon as each visitor has completed the action on which the test is performed. Note: the tested page must be the page on which the action takes place (you cannot test modifications on another page).

To create a test conditioned on an event, you must:

1. Create a standard test, applying your desired modifications
   
2. Tick the checkbox “Target by Event” in the targeting options window, in the same box as the URL targeting options. Note that other targeting options will no longer be available
   
   
   
   
   
   
   
3. Set up the rest of your test as usual
   
4. Launch your test
   
5. Call the function ABTastyStartTest directly from your application whenever the event occurs.

For example, if you would like test 12345 (set up in advance) to be triggered by a click on a button, you can do this in the following way:

<button onclick='ABTastyStartTest(12345)'>Launch a test from this button</button>

You can use any other method which links this function to an event. For example, you could use jQuery, or a callback function might be used if your site uses AJAX.

4. Defining a trigger

A trigger is a temporary user condition that enables you to display the campaign in a specific context.

The trigger enables the campaign to be displayed to the configured visitor segment only when the conditions are met.

How to set up your trigger in the campaign flow

Important to know ⚡️: The trigger applies to your whole A/B Test, meaning the original variation (V0) and all the variations (V1, V2, and V3 for an A/B/C/D test for example).
e.g. “trigger the campaign when at least 4 pages of the website have been visited”
The A/B Test will be triggered on the 5th page of the visitor’s session, with a random chance to see the original, V1, V2, or V3.

Single-page Experiences vs Multipage Experiences

👉 For A/B Tests, Simple Personalizations, and Patches, you’ll have to define one single trigger rule for your campaign because these types of campaigns have only one “experience” (one type of new content generated with AB Tasty to display).

👉 For Multipage Tests, Multivariate Tests, Multipage Personalizations, and Multi-experience Personalizations, you’ll have to define a trigger rule for each “experience”. This rule can be the same or can be different depending on your needs. 

• For Multipage Tests and Personalizations, we call the experiences “Pages”
  
• For Multi-experience Personalizations, we call the experiences “Experiences”
  
• For Multivariate tests, we call the experiences “Sub-tests”

⭐️ Best practices : 

• Use the same trigger on all experiences when this trigger is linked to your visitor’s current situation (e.g. geolocation criteria, device criteria, etc.)
• Use a different trigger on all experiences when the trigger is linked to a contextual behavior.
  e.g. Experience 1 is a pop-in that will be triggered after 5 viewed pages to promote sales (trigger = minimum viewed pages), Experience 2 is a banner in the basket (no specific trigger)
• Option to use different triggers in the case of Multi-experience Personalization. This kind of campaign has been designed to help you to launch several messages to different segments in the same campaign and to ensure no overlap between messages.
  
  To learn more about this, please refer to this article.

❗️In any case: Don’t forget to use the dropdown menu on the Targeting page to switch between experiences and set up your trigger for every experience

• We also offer a “Replicate” option, which allows you to replicate the full targeting setup or one part of the targeting setup of one experience in another experience, or in all experiences.
  

Using the dropdown 

The dropdown will present you with several of these three options: 

• the “Any Time” option (native pre-selected option)
  
• The list of triggers you have already created (account level), if the account has already some
  
• The option to create a “New Trigger” (at the bottom)

Using no trigger: Triggering the campaign without any specific condition

The first time you access the targeting section of your campaign, the “Any Time” option is selected by default in the How the Test/Personalization/Sub-test/Experience/Page panel.

This means no trigger is defined and the campaign will display in all cases, without any specific triggers.

Creating a new trigger

To create a new trigger to condition the display of your campaign, you need to select the triggering criteria to be applied to your campaign. 

To create a new trigger, take these steps:

1. Select New Trigger from the dropdown menu (last option in the dropdown)

2. The Trigger Builder opens

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

4. Fill in the specific requested fields depending on the trigger criteria you selected (see below for more explanation on each criterion)

5. You can combine your criteria with AND or OR 

• OR means that your campaign will be triggered if only ONE of the selected trigger criteria is met
  
• AND means that your campaign will be triggered if ALL of the selected trigger criteria are met (more information in the section below)
  

6. Name your trigger

7. Click on Save to use the trigger in your campaign and save it to your account library. This way it will be reusable in other campaigns (see section Using a Saved Trigger)

8. Click on Use Without Saving to use this trigger in this campaign only (if you don’t want to use it again in the future)

9. Click on Cancel to go back to the targeting page without saving anything

If you’ve created a new trigger, it will be automatically selected in the dropdown: the trigger setup is now complete.

You can save your Targeting configuration by clicking on Save on the bottom right.

For more details on each criterion please refer to our guide about trigger criteria. 

Using a saved trigger

If you want to use a trigger that has already been configured, you can find it directly in the dropdown list:

Click on it to select it for your campaign: the trigger setup is now complete.
You can save your Targeting configuration by clicking on Save on the bottom right.

Managing your saved triggers

If you want to edit, duplicate or delete an existing trigger, you can do it directly from the dropdown menu: 

• Click on the pen icon and you will open the Trigger Builder. You can then modify the name of your trigger and/or its configuration. Click on Save to record your changes.

Please note: If your trigger is already used in a live campaign or is live in QA, you won’t be able to save your modifications. In this specific case, you’ll get a yellow disclaimer with the details of the campaign(s) that is (are) using the trigger and that is (are) currently live or live in QA. 

In this case, you can: 

• Modify the configuration and use the new trigger in this campaign only (CTA Use Without Saving). The new trigger will be used for this campaign only, and you’ll find it at the top of the list in the dropdown. If you edit it again, you’ll be able to give it a new name and save it as a new saved trigger
  
• Go back to the previous dropdown and duplicate it before editing 
  
• Pause your campaigns first before editing and saving it 
  
• By clicking on the trash icon, a prevention pop-in will ask you if you’re sure you want to delete the selected trigger.

Click Delete to delete, or click Cancel to return to the previous screen. 

• By clicking on Duplicate, the selected trigger will be duplicated and will appear just after the selected one in your dropdown list

❗️Important: You can’t delete a trigger that is already used in a live campaign or is live in a QA campaign. You need to pause the campaign(s) that use(s) the trigger to be able to delete the trigger from your account.

How the trigger criteria work

Easily build a new trigger by clicking on the Create button at the bottom of the dropdown in the trigger section. Open the Trigger Builder and play with the trigger criteria.

Discover our complete guide to trigger criteria by visiting the Triggers Criteria page.

5. Defining targeting verification

In this section, you’ll discover how the AB Tasty Tag is interacting with your website and triggers (or not) the campaigns following the target setup you did.

When a page loads, the AB Tasty Tag verifies the targeting conditions. At this point, the URL of the page, the elements used to trigger the campaign (ID/Class/Element options), the segment, and the defined trigger can be detected. The campaign is only displayed to visitors who meet ALL the targeting conditions.

However, some elements are called after the page has been initially loaded, with a slight delay, or after the visitor completes a certain action. This is why, in some cases, they do not appear on your pages once the test is launched.

Good to know 💡 

The verification interval is based on the ‘setTimeout’ JavaScript function, which verifies the URL targeting first.

If the URL doesn’t match the setup configured in the target pages, the campaign won’t trigger.

If it does, the verification applies as follows: the targeting configuration is verified (ID/Class/Element, Segment, Trigger).

If the function returns false, which means that conditions are not met, the ‘setTimeout’ function is called and will detect if the element appears after the specified delay.

If the element is never detected, the campaign won’t be triggered for the chosen visitor segment.

⚙️ Configuration

To determine how the targeting verification will be performed, you must select one of the two targeting verification options:

• When the page loads
  
• At regular intervals until the conditions are met
  
  

Good to know 💡:

A “Recommended” label is displayed next to the option we recommend using. The second option is recommended when you have at least one criterion which requires it. The list of all the configured criteria requiring this option is displayed.

Targeting is verified when the page loads

This option is selected by default. Most targeting criteria can be validated when the page loads. If any of the criteria you have configured require the second option, in other words, if the second option is not recommended, you can keep this option.

Targeting is verified at regular intervals until the conditions are met

This option is useful when your campaign targeting includes one or several criteria that cannot be verified on page load.

🗒 Use case:

• When using the ID/Class/Element triggering criteria
  
• When using a segment based on one or several segmentation criteria that are not available on page load, such as data layer variables (which can display after a small delay) or some DMPs
  
• When defining a specific custom code in the targeting step to refine the triggering conditions
  

🗒 Use case : 

On a travel website, the “Book” CTA only appears once the visitor has selected their travel dates. Selecting the “at regular intervals until conditions are met” option allows the tag to verify the conditions at regular intervals until they are met (when the element is finally loaded and appears).

• If the triggering conditions are met at one point during the multiple verifications, the campaign will be triggered on the page
  
• However, if the triggering conditions are never met, the campaign won’t be triggered on the page

In other words, the campaign is triggered on the page only if the conditions are met at some point during the verification.

Good to know 💡

When creating a custom code trigger, you can use JavaScript Promises, which enable you to wait for a specific event to happen without impacting your overall website performance. We recommend using them as much as possible.

When using a Promise in the custom code trigger, the setTimeout() function won't apply and the AB Tasty Tag will wait for your own function to resolve.

🗒 Use case : 

You may want to change the color of the pop-in that appears when the user clicks Add to cart on the product page of your website. This pop-in is not natively on your product page but appears after the user has completed a specific action. In this case, you must select the “at regular intervals until the conditions are met” option. To do so, take these steps:

1. In the Where section, select your product pages in the dropdown list
   For further information on how to add a page element to the Where section from the editor, please refer to section Add to Targeting Option.
   
2. In the How section, select the ID/Class/Element triggering criteria, select ID and enter the ID of your pop-in
   
3. Select the “at regular intervals until the conditions are met” option.

This way, AB Tasty will check whether the pop-in appears on the product pages only at regular intervals. When the pop-in is loaded and appears, the modifications are applied.

6. Defining the Display Frequency

In this section, you will learn how the AB Tasty tag interacts with your website to apply the display frequency defined for a campaign.

When a page loads, the AB Tasty Tag verifies the display conditions that you configured inside this targeting step. This section adds new conditions on top of what you previously configured (URL of the page, specific page elements, triggers, and segments). The display frequency condition are set on user level. The campaign will only be displayed to visitors who meet ALL the targeting conditions.

⚙️ Configuration

Good to know 💡

By default, the campaign will be displayed "anytime" the targeted audience lands on the page and enters the other targeting criteria (where/who/how).

To determine at which frequency the campaign will be displayed to the targeted audience, follow the steps below:

1. Open the When to display the personalization block and select one of the following display frequency options:
   - Anytime - this is the default option - for the campaign to be displayed each time the targeted audience lands on the page and respect other targeting criteria. 
   - Once - for the campaign to be displayed once per user that match the targeted audience, when he/she lands on the page.
   - At regular intervals - for the campaign to be displayed at specific regular interval. Display intervals should then be configured.
   
2. Click Save step. 
   The When to display the personalization block is folded.

Configure Display Intervals of the Campaign

To configure the display intervals of the campaign, follow the steps below: 

1. Open the When to display the personalization block and select the At regular intervals option in the The targeted audience will see the test list. 
2. Determine the display interval of the campaign using the Day, Past week, or Session option, combined with the numerical selector.   
3. Click Save step. 
   The When to display the personalization block is folded.

7. Specific options

Replicate targeting option

Definition

The Replicate Targeting option enables you to copy the targeting configuration of a sub-test (for a Multivariate Test), a page (for a Multipage Test or a Multipage Personalization), or an experience (for a Multi-experience Personalization) and to paste it into another sub-test(s) or scenario(s).

This option is available in the targeting step and can be useful for Personalizations with multiple scenarios, or Multipage Tests and Multivariate Tests with multiple sub-tests. 

It saves you from having to configure targeting independently for each scenario and each sub-test and saves you time.

⚙️ Configuration

To use the Replicate Targeting option, you must first configure targeting for at least one sub-test/page/experience. It can be any sub-test/page/experience.

To replicate one or several sections of this sub-test/page/experience to at least one sub-test/page/experience, select the sections of the current sub-test/page/experience you want to copy. 

You can replicate the Who, Where, and How sections (you can find these in our Targeting guide). You can also select all sections if you want to replicate the whole targeting configuration of your current sub-test/page/experience.

If a section is made of several criteria, you cannot select individual criteria. The entire section will be replicated. 

Then, select the sub-test/page/experience into which you want to copy the selection and click Apply.

If the sub-test/page/experience you want to replicate your selection to already has some targeting configured, the previous configuration will be overwritten and replaced with the new one. 

You can then edit any section of any sub-test/page/experience to fit your needs. 

Good to know 💡

From the dropdown menu, you can change the reference sub-test/scenario from which you want to replicate the targeting section(s). 

The Replicate Targeting option is available for the following campaign types:

• Multipage Test/Personalization: Usually, the Who (segment of visitors) and How (triggering rules) sections should be the same for all pages. Only the targeted pages (Where) differ. We recommend configuring the Who and How sections on the first page before replicating them directly on all pages. Then, you can configure the Where independently for each page.
• Multivariate Test: The Targeting configuration must be the same in all sub-tests. We recommend configuring Targeting in the first sub-test and replicating it directly in all sub-tests.
  
• Multi-experience Personalization: Usually, the Where and How sections should be the same in all experiences. Only the visitor segment (Who) must differ. We recommend configuring targeting for the Where and How as well in the first experience and replicating them directly in all experiences. Then, you can configure the Who independently for each experience.

🗒 Use cases

Let’s say you plan to display a promotional message on the homepage, the product pages, and the cart page for clients who purchased at least 5 times in the past year (20% discount) and for clients who purchased fewer than 5 times in the past year (15% discount).

In this case, your Personalization campaign is made up of two experiences: 

• First, create a Multi-experiences Personalization with two experiences. 
  
• Then configure the Targeting for the first experience as follows:

1. 1. 1. Who: Purchase Frequency > visitor has purchased at least 5 times within the last 365 days
         
      2. Where: is > http://yourwebsite.com/homepage | is > http://yourwebsite.com/product  | is > http://yourwebsite.com/basket
         
      3. How: Any time

• Then, click Replicate Targeting from the current experience (Experience 1) and select the Where and How sections. Select the second experience (as you only have two experiences) and click Apply. 
  
• Go to Experience 2 with the dropdown on the top of the targeting page and configure the Who section: Purchase Frequency > visitor has purchased fewer than 5 times within the last 365 days. 
  
• Click Save.

Add to Targeting

With the idea in mind to constantly improve the user experience, AB Tasty now offers an option that will help you set up your campaign more efficiently. You can now choose a specific element within the WYSIWYG/contextual editor, and directly use it in the targeting step of the campaign setup.

⚙️ Configuration

Using the WYSIWYG/Contextual Editor

AB Tasty's WYSIWYG/Contextual editor enables you to design and create your own user experiences using AB Tasty widgets, your custom widgets, or the WYSIWYG interface and its contextual menus.

As you are in the Editor step, you can use the contextual menu of the editor to directly set a page element as a “where” condition, avoiding back-and-forth between both campaign steps.

To do so, in the Editor step, select the page element to be set as the “where” condition and click the Add to targeting option to send your element’s URL and CSS selector to the Where section of the Targeting step. 

As soon as you click the Add to targeting option, the element configuration will automatically be sent and saved in the Targeting step. 

A window will appear, allowing you to do one of the following: 

• Continue editing your variation(s).
  You will then still be able to review your targeting configuration later on, in the Targeting step. 
• Go to the Targeting step page and start reviewing it.

Good to know 💡

Depending on the type of campaign you are setting up (test or personalization campaign), the Editor step will come before or after the Targeting step. 
When configuring a personalization campaign, you start with the Targeting step to define precisely the audience you would like to target. In this case, if you configure the "Where"section first and then use the Add to targeting option in the editor, you will erase your previous configuration and replace it with the newly created one. A window will appear asking you to do so. If you accept, you will need to go back to the Targeting step to review the new configuration.

To the Targeting Step

As you are in the Targeting step, you will be able to retrieve the information you have sent and saved from the editor through the Add to targeting option. The Where section is unfolded to let you review these two newly added configuration elements (URL and CSS selector).

Two elements are configured:

• The URL: you should retrieve the URL that was previously declared in the Main Information step (and that you worked with in the editor). If you want to change it, then you will need to enter another URL in the dedicated field and save the Targeting step by clicking Save step. 
• The CSS selector of the element that has been selected in the editor.