- Holistic testing: Evaluate the impact of your changes across user journeys that span multiple pages.
- Unified experiment management: Create and manage variations that affect different pages within the same experiment.
- Streamlined workflow: Design variations for multiple pages at once, reducing the need for separate experiments.
- Launch the Graphic editor on all desired pages.
- Design your variations and incorporate changes for each page within the same variation.
- Define the targeting criteria for your multi-page experiment during finalization.
Kameleoon also supports the simultaneous selection of multiple elements on one or several pages. Multiple selection enables efficient edits to elements with identical IDs or classes across multiple targeted pages. For example, you can automatically apply a change to an “Add to Cart” CTA on one page to all other “Add to Cart” CTAs on targeted pages in the experiment.
Target pages according to their URL
Once your variations are complete, click Finalize to proceed to the experiment configuration. In the finalization flow, the Targeting step defines the conditions under which your experiment exposes visitors to your variations. This step contains two sections: Segments, where you build audience conditions such as page URL or device type, and Triggers, where you define when and where the experience fires. This article covers the page-based and entire-site targeting options, which live in the Triggers section.Several pages sharing the same URL
To target several distinct pages by URL:- In the finalization flow, click Target a segment > Create a new segment. The segment creation window opens.
- Double-click the Page URL condition or drag and drop to select it. You can add this condition as many times as you need.
- Indicate the URL or URL fragment you want to target on your website, and specify whether you want to include or exclude it.
A wide range of targeting conditions are available. For more information about targeting conditions, see Manage targeting segments.


- Contains: Runs the test on all URLs containing a URL fragment.
- Corresponds exactly to: Runs the test only on the URL you choose. If your URL contains changing parameters, use the Matches the regular expression option.
- Matches the regular expression: Use this option if your A/B test runs on a group of pages with specific parameters, such as
?x=exemple&y=exemple2.

mywebsite.com/article/january and the parameter x=y.
Among the five following examples, only the first two URLs count toward the A/B test:
http://www.mywebsite.com/article/january?x=y
https://mywebsite.com/article/january?a=b&x=y&c=d
http://www.mywebsite.com/article/january
http://www.mywebsite.com/article/january/?x=y
http://www.mywebsite.com/article/january/monday?x=y
Explanation:
- The third URL does not contain the
x=yparameter. - The fourth URL contains a
/afterjanuary. - The fifth URL has
mondayadded at the end.
Several pages with the same URL fragment
To target several pages that contain the same URL fragment, either build a segment with a Page URL condition set to Contains, or select The URLs containing a specific fragment trigger option in the Triggers section of the Targeting step. For example, to change the color of the add-to-basket button on each of your product pages, where all of the URLs contain one identical fragment, select this trigger option:
/product/ fragment, enter /product/ in this field so the experiment runs only on pages that contain this fragment.
From an element on the page
URL-based targeting doesn’t work in every case. Two common scenarios require a different approach:- All the URLs are different.
- You want to test only the last step of a multi-step process, such as registration or checkout, where every step shares one URL. Targeting that URL would include every step in the A/B test, not just the last one.
- Create a new segment within your experiment.
- Select the Technical category > Element on the page.
- Define the element that must be present on the page to include visitors in the experiment.


For optimal performance, choose an element located near the top of the page when using Presence of an element on the page. Placing the element lower on the page increases the likelihood of flickering, because Kameleoon waits for the element to load before triggering the experiment.
On the whole website
You can also run the experiment on every page of your website. To do so, select The entire site trigger option in the Triggers section of the Targeting step.