This page is a cheat sheet for every browser console command used to inspect and debug Chameleon Experiences. All commands are temporary — they run only in your current browser session and have no impact on other users or your account.
Lots of info about what Chameleon is doing behind the scenes in your app is available with a few browser console commands.
These are temporary commands run just within your browser, and will not impact your application permanently or for any other users. To clear these commands you can simply refresh the page.
ℹ️ Open your browser console with cmd + opt + J (Chrome on Mac) or ctrl + shift + J (Chrome on Windows), or right-click anywhere on the page → Inspect → Console tab
Console Commands
Installation and setup
Command | What it does | When to use it |
| Checks whether the Chameleon snippet is installed and running correctly. Returns a confirmation message if successful. | First step when Experiences are not showing at all. Also useful on localhost. |
| Returns the user profile object. If this is not | Check whether |
| Returns all user properties Chameleon has received for the current user. | Compare against your Segment rules to verify property names, values, and data types. |
| Returns all company-level properties Chameleon has received. | Debug company-based targeting rules. |
Experience status
Command | What it does | When to use it |
| Lists all published Experiences in your account with their current display status. Expand any entry with | General starting point when you don't know which Experience is causing the issue. |
| Shows the detailed status of a specific Experience, | Primary debugging command when you know which Experience is not behaving as expected. |
| Returns a simple list of all published Experience names. | Quick check to confirm an Experience is published and visible to the snippet. |
| Returns the name of the Experience that is currently running or waiting to display. | Identify which Experience is currently active when you can't tell from the UI. |
Audience targeting
Command | What it does | When to use it |
| Lists every published Experience alongside | Find which Experiences the current user qualifies for, or confirm an audience rule is matching/not matching as expected. |
URL matching
Command | What it does | When to use it |
| Lists every published Experience alongside | Debug URL matching for all Experiences at once, especially useful in single-page applications. |
Experience history and state
Command | What it does | When to use it |
| Lists every Tour the current user has interacted with and its state: | Check whether a user has already seen a Tour and what state it was left in. |
User properties and account data
Command | What it does | When to use it |
| Returns all user property names that have been sent to your Chameleon account (across all users, not just the current one). | Confirm a property name exists in your account before using it in a Segment rule. |
Session management
Command | What it does | When to use it |
| Clears all currently active Chameleon Experiences from the page for the current session. Does not affect other users or account settings. | Dismiss an active Experience during testing without reloading. Also called on user logout in single-page application implementations. |
| Forces a specific Experience to show immediately, bypassing audience targeting and URL rules. | Test an Experience's display without meeting all the display conditions. Useful on localhost or staging. |
How these commands relate to each other
When troubleshooting a specific Experience that is not showing, run these commands in order:
chmln.Snippet.debug()— confirm installationchmln.data.profile— confirm user identificationchmln.debug("EXPERIENCE_ID")— check URL rules, audience, element, and rate limitchmln.data.profile.attributes— verify the property values Chameleon has for the current user
Still stuck?
💡 Tip: If you're working through these commands and want a faster path to answers, try Copilot — it can help you interpret debug output and suggest next steps based on your specific setup. Sometimes a quick question gets you unstuck faster than running through every command manually.
For a guided walkthrough of the Debugger and how to read its output, read How to use the Debugger Console tool.
For step-by-step diagnosis of a specific problem, start at Why isn't my Experience showing?

