Sometimes an Experience isn't displaying as you want it, or your expected behavior doesn't match what you get. 😕
In this lesson, you'll learn how to use the Visual Debugger — and the console commands it builds on — to troubleshoot Experiences, and where to get additional help when you need it.
Use our Debugger tool to troubleshoot Experiences
The Visual Debugger is the fastest way to troubleshoot Experiences — open it from the Chrome Extension with one click, no console access required.
💡 All diagnostics run locally in your browser and will not affect your application or other users.
Prefer the console? The classic commands (chmln.debug(), chmln.Snippet.debug()) still work. See the Console commands quick reference.
Running the Visual Debugger will show you results that you can easily act upon. For example, if the user is in the Target Audience for that Experience, if the Experience is being Rate Limited, and more. You can easily resolve these and move on. 🙂
👉 How to use:
Click the Chameleon Chrome Extension icon in your browser toolbar.
Click "Open Debugger."
The Debugger side panel opens on the right side of your browser.
The Debugger works on any page where Chameleon is installed. It shows all your Experiences grouped by status and explains — in plain English — why each is or isn't showing.
Step-by-Step Debugging Process
Step 1: Test Chameleon Installation
Start by running chmln.Snippet.debug() to verify that Chameleon has been installed correctly and that the Snippet is functioning properly.
Look for positive confirmation messages such as "Chameleon loaded, User profile loaded" to confirm successful installation.
Step 2: Test Experience Status
If Step 1 shows successful installation, go ahead and run chmln.debug() to test your Chameleon Experience status.
This command will show you:
Complete list of all Experiences published in your account
Expandable details - Click the arrow (>) next to any Experience to view specifics
Display state information - Shows current status of the Experience
Segment details - Displays which Segment is being used
Step information - Indicates which step the Experience is currently on
Step 3: Debug Specific Experiences
You can focus your debugging on a particular Experience by including its ID in your debug command.
Use this format: chmln.debug("60cb861eb6ef93001b8d731e") where you replace the ID with your specific Experience ID.
Read How do I debug my Experiences? for a full explanation of each status message and how to resolve the issue.
🎓 To learn more about Troubleshooting Experiences read these articles:
Always here when you need us
We get that it's not always easy to solve issues on your own. We are here to help you get unstuck and move forward. 🙌 A good place to start is the Get Help page, where you can also Report an Issue or Request a Review, aside from having access to our helpful resources.
And remember, if you need us we are just an email away. 😉
👉 You've almost reached the end of the Chameleon 101 Course but just begun your Experience-delivery proficiency.