Testing Mode allows you to evaluate what your users will see by treating you as an end user rather than a Chameleon administrator.
When using Testing Mode, you will only see live Experiences based on your user data and Tour history. This is the most effective way to test your Experiences from a user's perspective.
For a Chameleon Experience to display properly, all of the following conditions must be met:
Snippet Installation: The Chameleon Snippet must be correctly installed on the page.
User Identification: Users must be identified correctly with a unique identifier.
Experience Status: The Experience must be live with all Edits Applied.
URL Matching: The Step URL must match the current page URL.
Element Presence: The Step trigger element or anchor element must be present on the page.
Audience Targeting: The user must be within the selected audience.
Completion Status: If the Experience is set not to recur, the current user must not have completed or exited the Experience previously.
No Blockers: Ad blockers or cookie blockers must not be interfering with the Experience.
During live testing, if you are not seeing the Experience then please troubleshoot with the steps below:
Checking Snippet Installation
To confirm that you have correctly implemented the Chameleon snippet:
Right-click on the page and select "Inspect Element"
Open the Console tab
Type
chmln.data.profile
If you receive an error message such as "Uncaught ReferenceError: chmln is not defined" or "undefined," the snippet has not been implemented correctly.
Verifying User Identification
Ensure that chmln.identify is called with a user ID (uid) each time a logged-in user loads a page.
If chmln.identify is not called, Experiences will not display. You can use the Debugger tool in your console to check this.
Verifying your domain
Check if you have previously disabled the domain, as this will prevent Experiences from showing to users. You can review your domains in the Dashboard under Settings > Domains.
Publication Status
Ensure that your Experience is published and live. To do this, you must first sign up for a paid plan.
For information on testing Experiences without making them live, please see our article here.
Applied Edits
If you have made any changes to your Experience since you last published it, you must Apply Edits for those changes to appear live.
Steps will only show on the URLs they are set to match. Please ensure the URL of your page matches the one set for the step you are trying to preview.
Learn more about that here.
If you used an element to trigger the Step or to anchor the Step to, then this element must be present.
Sometimes the element identified during editing is too specific or does not match exactly with the element on the page, even if they seem similar. This is due to the underlying "HTML structure" and "CSS selectors" used to identify the element. Learn more about how to adjust these here.
If you do not fall in the target Segment or have previously seen the Experience, then you will not see it again.
To circumvent this, you have a few options:
Reset your user history by using Test Mode.
ℹ️ We store data about Experience history both server-side and on local storage. This means that even if you clear your history, the Experience may not show immediately, so please use a fresh incognito tab in Chrome or close Chrome (for your Chrome user persona) and then try again.
Set the Recurrence of the Experience to every time
With Tours, you can use its Tour Link to bypass targeting settings. For this to work, the first Step URL needs to be specifically defined (cannot use wildcards like "*").
Cookie Blockers
Verify that your browser is not blocking 3rd party cookies. For Chrome, you can read about how to manage exceptions (to allow Chameleon to set cookies) in Chrome's documentation.
Ad Blockers
Check if any ad-blocking software is interfering with Chameleon. Try temporarily disabling your ad blocker and refreshing the page to determine if that resolves the issue.
If none of these solutions resolve your issue, then please:
Use the debugger tool: The Chameleon debugger tool can show you the status of an Experience, including whether it's being Rate limited.
Advanced Troubleshooting: For more in-depth problem-solving, check our advanced troubleshooting article.
Contact Support: Email our support team with a screenshot or video of your app with the JavaScript console open (and scrolled to any errors related to
chmln).
ℹ️ Chrome now requires the Developer Console to be open while the page is loading to access variables, so please open the console and reload the page to see any potential errors.