Wondering why your Experience is not showing up as expected? You can use Chameleon's Debugger tool in the browser console to get detailed information using one of our two commands.
It will show you if the user is in the target audience for that Experience, if the Experience is being Rate Limited, and more. Use this to quickly track and solve issues and fast-track your Experiences to success.
Simply provide the command with the ‘Experience ID’ found in the URL of the Dashboard, chmln.debug('629f6c73f4ac75001836b38q') or run the command by itself to see details for all Experiences, chmln.debug().
Availability & Usage
🔐 Available for all plans
📍 For accurate display info on Tours, Tooltips, Microsurveys, Launchers
⚙️ Use from your browser console
Start by opening your browser console. To open it in most browsers, right-click your app and go to "inspect", and then click on the "console" tab. The shortcut for Chrome on Mac is cmd+opt+J.
Once you have the console open, you can run debugger commands there.
ℹ The debugger has two commands available, depending upon what stage of loading Chameleon has been completed: chmln.debug() or chmln.Snippet.debug().
Click on the Console tab to start adding commands. You'll type in either chmln.Snippet.debug() or chmln.debug() next to the blue carrot (>) and press enter.
We recommend starting with chmln.Snippet.debug() to test if Chameleon has been installed correctly and that the Snippet is working properly.
If this debug message returns a positive message, such as "Chameleon loaded, User profile loaded," then proceed to use chmln.debug() to test Chameleon Experience status.
When you run chmln.debug() you will see a list of all the Experiences that have been published in your account. Click the arrow > next to an Experience to see details on its display state, what segment is used for the Target Audience, and which step it's on.
You can debug a specific Experience, by including its ID in your debug call. Such as chmln.debug("60cb861eb6ef93001b8d731e").
You can grab the Experience ID directly from the console from the drop-down menu of the Experiences listed in the console.
Or you may find the Experience ID in the Chameleon Dashboard. When you open an Experience's page you will see its ID from the URL, for example, app.chameleon.io/tours/629f1bdd19fc2d00136ca576.
The full list displayed when you run is of all published Experiences. If you do not see it listed, please open the Experience in the Dashboard to get the Experience ID and then run the command for that Experience. Most likely, the Experience isn't published and you'll see a message like this.
While you're in the dashboard, you can also see the state of your Experience. If you do not see the green "Live" badge next to the title, this also tells you that it isn't published and shown live to other users.
Now that you've gotten the results of your Experience, here's more information about what each message means. If you expect an Experience to display but it isn't, this will help you figure out how to resolve that.
Error phrase | Explanation | How to resolve |
Chameleon not loaded | Chameleon has not been installed or initialized correctly. | Review Chameleon's install documents and ensure both the Chameleon snippet and identify commands are installed correctly. |
User profile not loaded | No user has been identified to Chameleon, or the user profile has failed to load. | Review Chameleon's install documents and ensure the identify command is installed correctly. |
Chameleon is disabled | Chameleon's | Check to make sure the elusive setting is enabled for the expected users. |
Domain disabled | The current domain has been disabled. | Enable the domain on the domains page. |
Chameleon Cleared | Chameleon was initialized, and then | Talk to your development team to make sure that |
Something unique went wrong | Something that's not obvious went wrong. | Contact Chameleon Support for more help. |
More Messages
The errors below are self-explanatory and usually very easy to resolve when seen. But we are here to help out if you have any questions. We will also update this article with additional context.
Current user UID "[uid]" is within the Target Audience, Experience can be displayed to you when all conditions are met and no other Experience is showing.
Current user UID "{uid}" is not within the Target Audience, Experience will not be displayed to you.
Current user UID "[uid]" started this Experience but is no longer within the Target Audience. After it is exited or completed it will not show again.
Control group test being run on this Experience, Current user UID "[uid]" is not in the test group and will not see the Experience.
Control group test being run on this Experience, Current user UID "{uid}" is in the test group and can see the Experience when other conditions are met.
Current user UID "{uid}" is within the Target Audience, but Control group test being run on this Experience, Current user UID "{uid}" is not in the test group and will not see the Experience.
Current user UID "{uid}" is within the Target Audience, Experience can be displayed to you when all conditions are met and no other Experience is showing.
Current user UID "{uid}" is in the test group and can see the Experience when other conditions are met.
Current user UID "{uid}" is not within the Target Audience, Experience will not be displayed to you.
Experience would be able to display here, but is rate limited. (See your Rate Limiting page in the Dashboard, and learn more here).
Completed Survey, but finishing extra comments or thank-you.
Experience was recently triggered by an action on a previous Experience, short-link URL, or a call from the API.
Experience can be manually started by an action on an Experience, short-link URL, or a call from the API.
Experience has been Completed.
Experience has been Exited.
Experience is not displayed but will reappear based on next recurrence setting.
Experience has been Exited and will reappear after snooze time period ends.
Experience queued to be shown after other Experience(s) finish.
Experience\'s URL Rules do not apply to the URL of the current page.
Experience\'s selected anchor element is not on the current page.
Experience\'s trigger element/icon is either not on the current page or is on the page but has not been interacted with yet.
Experience has a Timed Delay set, and that time has not expired yet.
Experience requires a selected element to be present on the page, still checking for the element.
Experience required a selected element to be present, the time has expired and element was not on the page.
Experience requires a selected element to be absent from the page, timer still counting down before checking.
Experience requires a selected element to be absent from the page, the time has expired and element was still on the page.
[Experience] Title: "[name]" is being displayed on the page.
There is no published (aka live) Experience with ID '[uid']. Open the Experience from the Chameleon Dashboard, confirm the ID at the end of the URL, and also that the Experience is live.
If you're seeing a Launcher and the status is blank, the Tours inside may be unpublished.
Now displaying, no other Experiences can Display.
ℹ Note you'll also see if your Experiences are not displaying because of a Smart delay (because the user has interacted with another Chameleon Experience before on the same session, or because of the built-in 60-sec delay) or if it's waiting on the Timed delay to end (and another Experience is displayed instead).
📩 If you need any further help feel free to contact us with questions.