FAQ

In the Kameleoon app

In the left sidebar in the Kameleoon app, click Installations > Project. You will find your Sitecode on your project card.

In the Chrome extension

You can also find your Sitecode on the Dashboard of our Chrome extension.

Click the + icon to add inserts to customize your dashboard. Add the Site Code insert.

You can edit anything in an online experiment; however, we don't recommend it.

Any change will disrupt the interpretation of your results, making them less reliable.

If you want to avoid these complexities and still make changes, we recommend the following approach:

1. Stop the experiment (if you want to).
2. Duplicate the experiment.
3. Edit is as you wish.
4. Launch the new experiment.

By following these steps, you can ensure your results remain reliable.

The duration of an A/B experiment depends on the kind of experiment and its traffic

Suppose you have an experiment where the first visitors to the variation convert. You will quickly see how effective the experiment is, although this result is rare.

Often, the conversion rate does not significantly change right after launching; however, if you keep your experiment running long enough, the variation will be seen by many visitors, and the results will be significant.

Note: If you are using Google Analytics or Kameleoon's internal reporting tool, Kameleoon will automatically measure your experiment's significance the significance according to the goals you set. For more information, refer to our article about Statistical significance.

You can also estimate the duration of your experiment during its finalization. To learn more about estimating an experiment's duration, refer to this article.

A/B testing derives its primary data from the traffic your website receives. Therefore, keep these numbers in mind:

• Below 10,000 monthly visitors, it is difficult to perform effective A/B tests, other than a few use cases (for instance, on a landing page).

• From 10,000 to 200,000 monthly visitors, A/B testing is possible, but experiments will often take time to give results.

• From 200,000 to 1 million monthly visitors, your traffic is large enough for A/B testing. You might still have difficulty with some less frequented pages, though (at the end of the conversion funnel, for example).

• Above 1 million monthly visitors, traffic is rarely an issue.

Kameleoon and its interface are available in English, French, or German.

Your browser's language is used by default. If your browser language is unavailable in Kameleoon, English is used instead.

In the Kameleoon app

To change the language in your Kameleoon App:

1. Click your profile icon in the top-right corner > Language

2. Choose your language and click Confirm.

Click the parent selector icon, then use the drop-down list to select an element.

When you select an element, click the ellipsis (...) on the left of the hierarchy panel. A list appears, it contains:

• The selected element, highlighted in green.

• The children elements, above the selected element on the list.

• The parent elements, below the selected element on the list.

A/B experiment

An A/B experiment allows you to make variations of one or several pages.

For instance, an A/N experiment can measure the performance of product page A versus product page B.

With an A/B experiment you can only change one element per page (for example, the text in an "Add to cart" button) to know if the modification impacts conversion rate. If you change multiple elements, you cannot know the impact of those changes individually.

Multivariate test

A multivariate test (MVT) lets you change several elements of a page and analyze which combination leads to the most conversions. For example, you can test multiple versions of an "Add to cart" button with two versions of color and two versions of text to find which is most effective.

To create your first MVT with Kameleoon, please read our article Creating a Multivariate test (MVT).

You can disable the Kameleoon editor shortcut in your app.

Disable the shortcut

1. Click Admin > Projects.
2. Click Configuration on a project's card.
3. Click Experiment.
4. Toggle the switch beneath Editor launching to OFF
5. Click Save to save your changes.

Launch Kameleoon without the shortcut

Once you've disabled the shortcut, add ?kameleoon=true. For example, your URL will become https://www.website.com/?kameleoon=true.

If a visitor to your site has an ad-blocking service or browser extension enabled, Kameleoon assets may be blocked. Extensions such as AdBlock Plus, uBlock, or Ghostery are known to block Kameleoon, preventing it from running.

If you believe a significant portion of your visitors use ad blockers, Kameleoon offers a premium option to use a custom domain, which helps bypass detection by ad blockers. Learn more about enabling a custom domain.

Note: If you are using an ad blocker yourself, you may experience issues accessing the Kameleoon app, as some of our own resources might also be blocked.

AdBlock can create problems in the Graphic editor. We recommend disabling AdBlock before accessing Kameleoon.

Disable AdBlock

1. Go to the site you want to launch the experiment on.
2. Click the AdBlock icon. The icon is located in the upper-right corner of your browser, where extensions are displayed. It will be in the upper-left on Safari.
3. Click Don't run on pages on this domain.
4. Click Exclude in the window that opens.

Disable Adblock Plus

1. Go to the site you want to launch the experiment on.
2. Click the Adblock Plus icon. The icon is located in the upper-right corner of your browser, where extensions are displayed. It will be in the upper-left on Safari.
3. Click Enabled on this site ti disable Adblock Plus on the site you're visiting. The button will change to Disabled on this site.

Web browsers supported by the script

The Kameleoon doesn't support some older browsers. If a visitor is using an unsupported browser, your experiment will not display, and the visitor will see the original page. It will not be detectable by the visitor nor will it directly affect your experiment.

Here are the browsers supported for Kameleoon script:

• Chrome
• Firefox
• Micorsoft Edge
• Opera
• Safari

We ensure compatibility with the last three versions of each browser.

Web browsers supported by the Graphic editor

Here are the browsers supported for the edition and the creation of your A/B experiments:

• Chrome
• Firefox
• Micorsoft Edge
• Opera
• Safari

We ensure compatibility with the last three versions of each browser.

Compatibility with responsive design websites

You can create this type of experiment with Kameleoon using advanced edition functionalities. For an A/B experiment on a website with a responsive design, the main challenges typically involve resizing and repositioning content blocks.

Since pages are displayed based on screen resolution or device, you must be careful when moving elements in your experiments. Additionally, heat maps cannot be used, as there is no fixed frame on the page.

Kameleoon offers some advanced functionalities to move elements and avoid issues.

When your webpage loads, the original page may display briefly instead of the variation. this issue is called the flicker effect or flickering.

Why does it happen?

Flickering happens because the time it takes for the JavaScript engine to process the page.

Elements in an A/B experiment are changed according to the order indicated in the JavaScript code created by the testing tool. Consequently, if the Kameleoon script loads after the webpage, the variation will load last, leading to flickering.

How to avoid flickering

Kameleoon’s engine is designed to limit flickering; therefore, you are unlikely to encounter it.

However, we recommend integrating the Kameleoon JavaScript code as high as you can on the HTML page, ideally right after the <head> element to ensure Kameleoon loads first.

Kameleoon is completely JavaScript and does not use jQuery. There won't be any conflict if you are using jQuery on your website.

However, Kameleoon uses the Sizzle library which is the CSS selector engine of jQuery. You can use it when you create your experiments.

When you create a segment, you can use "AND" or "OR" to define them.

Definitions

‘AND’ corresponds to a simple addition: condition A and condition B must be reached to activate the personalization.

‘OR’ means that only one of the conditions must be reached: either condition A or condition B must be reached to activate the personalization.

The Narrow this condition option corresponds to the mathematical parentheses.

Examples

Condition A and condition B = both conditions must be reached

Condition A and condition B and condition C = all three conditions must be reached

Condition A or condition B = at least one of the conditions must be reached

Condition A or condition B or condition C = at least one of the conditions must be reached

Condition A and condition B or condition C = Condition A and one of the two other conditions must be reached

(Condition A and condition B) or condition C = Condition A and B must be reached, or only Condition C must be reached.

For more information on setting up conditions in segments, refer to the Create a segment article.

Kameleoon allows you to target visitors based on geolocation data.

On average, the accuracy of this geolocation is as follows:

• Country: 99.8% accurate ;
• Region: 80% accurate;
• Town: 68% accurate within a 50 kilometer radius.

Please note that:

• Accuracy will vary depending on the country and type of device used by your website's visitors.

• IP geolocation will always be more accurate for broadband IP addresses than on cellular networks (mobile devices).

• Fewer countries are available for IPv6 IPs, so the IP geolocation won't provide accurate results when that's the case.

For more information on setting a condition's weight, refer to the Create a segment article.

Kameleoon bills your account on an annual basis based on the average number of monthly users who visited your site or application in the past 12 months.

Kameleoon has a native consent management and therefore only collects data from users who have given their consent. Learn more about Kameleoon’s consent management policy.

If your website experiences bot traffic, we recommend excluding it from your campaign results. Learn more about it here.

Users are only counted once, even if they are bucketed into different experiments or feature flags across devices.

Web Experimentation

Users are measured based on cookies. A cookie is a file placed in a browser that contains an anonymous unique identifier, called the Kameleoon visitorcode, randomly assigned to a user. This ID is used to identify a browser. A visitorcode is stored for 365 days on the user's browser.

Feature Experimentation

Refer to this FAQ in our developer documentation for more information on how Kameleoon counts and tracks unique users in Feature Experimentation.

Kameleoon experiments and personalizations are powered by data collected via a first-party cookie.

They're not affected if cookies are disabled, as they don't rely on third-party data sources.

By safeguarding our unique visitor ID in a first-party cookie, we guarantee that each visitor consistently experiences the same variant in a given experiment, which ensures accurate results and delivers a seamless and personalized user experience.

Here is the complete list of data collected by Kameleoon.

When landing on your website, a visitor's browser must download your site's code, including the Kameleoon script. Page loading time is impacted by the code's length and the number of external resources to download (for example, images, CSS, and scripts). Caching reduces the loading time during subsequent visits: the website's code and all static resources are downloaded and put in the browser cache to improve performance.

Caching therefore improves the user experience. But there is a downside: if Kameleoon's script changes (for example, if you have launched a new experiment), old visitors who have already started their visit on your website (and already downloaded the previous version of the Kameleoon script) won't see the new experiment yet.

To avoid this problem, there is a flag in the Kameleoon script, Cache Expiration (TTL: Time-to-live), that asks a browser to take a new version of the script every 1.5 hours: the script embeds its own expiry date.

Note: Sometimes, even though there is a TTL in place, a browser can decide to ignore it (this is often the case on mobile browsers as they want to optimize performance). It depends on each browser's policy.

Bots are software applications that run repetitive, automated tasks over the internet. This behavior may impact your experiment and personalization results, as bots don't behave like real visitors and inflate your site's volume of traffic, effectively biasing your conversion metrics. Therefore, removing bot traffic from your campaign results is essential to make your data more accurate.

Kameleoon has two methods for excluding bot traffic from your campaign results:

• Kameleoon detects known bots and spiders with the IAB/ABC International Spiders and Bots List and do not count them in our analytics.

• Kameleoon uses proprietary internal algorithms to detect bot traffic on websites, and automatically filter these bots out of your campaign results. When building a visit from visitor events, Kameleoon rejects a visit if it is an outlier (for example, bot, troll, tracker bug). Kameleoon considers a visit an outlier if at least one of the following conditions is met during a visit:

  • Number of events > 10,000
  • Duration > two hours

Server-side experiments are more vulnerable to bot traffic. You must pass the user agent to be filtered by Kameleoon when running server-side experiments. Please refer to the SDK documentation for the correct implementation. No additional code is required to enable bot filtering for client-side SDKs, as the Kameleoon SDK automatically includes the user’s user agent in the outbound request.

To activate bot filtering:

1. Click Admin > Projects.
2. Navigate to your project's Configuration page.
3. In Advanced settings, toggle Enable bot filtering to ON

To learn how to install and use the Kameleoon Chrome extension, refer to this article.

You may notice data discrepancies between Kameleoon's results and a third-party reporting tool regarding your split URL experiment's traffic distribution.

There are a few reasons for this discrepancy:

• The Kameleoon tag is not installed on variation B of your experiment. This problem is common. The Kameleoon snipped must be installed on the new page (URL B) of your website so Kameleoon can track visits and conversions. Note that you may notice some visits to variation B even though Kameleoon is not installed on page B. These visits occur because Kameleoon tries to send the tracking call before redirecting to page B, so all visits counted on variant B are actually tracking calls from page A.

• The bounce rate metric could also cause traffic distribution discrepancies. In a split experiment, when a visitor has been bucketed into variation B, Kameleoon either sends the tracking data from the original page before redirecting the visitor to page B or when the visitor lands on page B. So, if your bounce rate is high, you could see significant discrepancies between Kameleoon and your reporting tool's results.

• If your consent policy is set to “Required”, you must follow these guidelines to have accurate metrics for your experiment. You can compare the number of visits you have in your third-party reporting tool for variation B with the number of visits you have for URL B, independently of your experiment. You should get approximately the same numbers, assuming visitors cannot access URL B without going through the experiment first.

You may encounter this issue if you installed the Kameleoon snippet with the Cross-Domain tracking option, which requires your main domain to host a static resource (an iFrame).

How does the Kameleoon iframe work?

The Kameleoon iFrame ensures data continuity and consistency when moving between different subdomains. This consistency is accomplished by delegating reading and writing information in localStorage (in the domain where the iFrame is deployed) to the iFrame.

As the local storage is specific to a single domain, the iFrame allows Kameleoon to read the Kameleoon data stored in your main domain's local storage, which helps keep track of the same visitor without making extra server calls and impacting your website's performance.

More detailed documentation on this subject

To secure our iFrame, we have implemented the following three measures:

• Restriction of access to identified domains: Only the domains specified in the allowedDomains variable (in the iFrame code) are authorized to request the iFrame. The Kameleoon iFrame can only load and execute code on the list of domains you allow in the iFrame file.

• Restricting access to identified sitecodes: Only a Kameleoon engine with the specified sitecode (in the iFrame code) can request the iFrame.

• Prefixed local storage: The iFrame (and Kameleoon at large) can only read and write entries prefixed with "kameleoon". No other data can be read or written.

The data collected by Kameleoon is of a non-personal nature in accordance with current regulations. Please read the exhaustive list of this data

Kameleoon offers consent management that can be adapted to all needs and ecosystems via a dedicated API and adjustable behavior in case of unknown consent. More documentation on this subject

How to resolve the "Refused to display..." issue

The X-Frame-Options HTTP response header can be used to indicate whether a browser should be allowed to render a page in a frame, iFrame, embed, or object. Sites can use this capability to avoid click-jacking attacks by ensuring their content is not embedded in other sites.

For more details, please follow the Mozilla developer documentation.

To enable cross-domain tracking, the Kameleoon iFrame must load on all your domains, so you cannot set an X-Frame-Options response header.

Also note that you can secure the iFrame by providing a restricted list of domains (for example, your domains and subdomains) that can call the iFrame. This list must be provided inside the static iFrame file that will be hosted on your site.

You may encounter the "Refused to load the script https://xxxxxx.kameleoon.eu/kameleoon.js because it violates the following Content Security Policy directive" issue.

This may be because of your website's Content Security Policy.

Fixing this issue

If your website restricts the loading of resources (scripts, images, media, CSS) via the standard Content-Security-Policy (CSP) HTTP header, you must update your site's CSP to allow Kameleoon resources to load. You can find the full list in our developer documentation.

To activate cross-device history reconciliation:

1. Click Settings > Custom data > New custom data.
2. Follow the usual steps, and click Next.
3. Toggle Use this custom data as a unique identifier for cross-device matching to ON.
4. Click Create.

Kameleoon is available in English, French, and German. By default, Kameleoon uses the same language as your browser; however, you can change the application's language at any time.

For more information, refer to the How do I change the app's language? FAQ.

It is highly unlikely that the Kameleoon script with conflict with any other script on your website.

Kameleoon is completely JavaScript and does not use jQuery, so there won't be a conflict if you use jQuery on your site.

Additionally, Kameleoon operates independently of server-side development languages and doesn't use global JavaScript variables, minimizing the risk of incompatibilities.

If you launched an experiment but cannot see the changes, follow these recommendations to ensure your experiment is set up correctly.

Note: There is a delay between the launch of an experiment in Kameleoon and its visibility on your site. It can take up to ten minutes for the experiment to go online.

Check if Kameleoon script is updated on your computer

When you launch an experiment, Kameleoon updates its script to ensure it contains the new data. The script loaded in your cache might not be updated. To check if it is, open a web console in your browser (with F12 on PC or CMD+ALT+I on Mac) and enter Kameleoon.API.experiments.getAll(). This command will list every experiment running on your website.

If your experiment is not on this list, empty your cache to force your browser to load the latest version of the script. Find out more in our developer documentation.

Ensure you are not on the reference variation

You can force a variation to display on your machine.

Check your experiment's targeting criteria

You may not be targeted by your experiment's targeting criteria. To check if you fulfill all criteria, open a web console in your browser (with F12 on PC or CMD+ALT+I on Mac) and enter Kameleoon.API.experiments.getAll(). This command will list every experiment running on your website. If your experiment is not on the list, there is a problem with targeting. Find out more in our developer documentation.

Note: You should launch a simulation to check if your experiment is set up correctly. Read this article about the simulation panel's Targeting tab for more information.

Why disable the script?

• If you attach significant importance to your website's performance and wish to limit loading times as much as possible.
• If you don't use Kameleoon continuously.

Disabling the script

1. Navigate to your project's Configuration page (Admin > Projects > Configuration).
2. Click Actions in the top-right corner of the page > Disable.
3. Click Confirm to confirm your choice.

You can follow the same process and click Enable to re-enable the script on your project.

Disalbing the script on a specific URL

To disable the Kameleoon script on a website, you can use a specific URL parameter. Add ?kameleoonDisabled=true to the end of the website's URL. This parameter prevents Kameleoon from loading on that page.

If you can't log in to Kameleoon or the Graphic editor, it's usually related to the Block third-party cookies option available in browsers, as Kameleoon requires a session cookie hosted on our domain.

This option must be disabled when you launch the Graphic editor. To disable Block third-party cookies:

1. Open your browser's Settings.
2. Navigate to Privacy & security > Third-party cookies.
3. Ensure Allow third-party cookies is enabled.

Note: Third-party cookies are usually automatically blocked in private/incognito mode.

These cookies must be enabled for you to log in to your Kameleoon account:

• refresh-token
• kameleoonSessionId
• access-token
• expiration-access