If you cannot open the Chameleon Builder on your page, the cause is almost always one of three things: the snippet is not installed, you are not authenticated, or your browser is blocking third-party cookies. This article walks through each scenario.
💬 Get instant help with Copilot Not sure where to start? Ask Copilot — our AI assistant can help you diagnose why the Chameleon Builder isn't appearing and walk you through the right fix for your situation. Just describe what you're seeing and Copilot will point you in the right direction.
The first thing to do is to ensure:
You are logged in to Chameleon.
Chameleon is installed on the page you are attempting to use the Builder or you have the Chrome Extension loaded on this page.
If either of these is not true, resolve them first before continuing.
Step 1: Identify whether the issue is installation or authentication
On the page, right-click and select “Inspect Element". Open the Console tab, and type chmln.
Result | What it means |
| The snippet has not been installed on this page |
A result containing | The snippet is installed but you are not authenticated |
Any other error | Your browser may be blocking third-party cookies |
Step 2: Fixing the issue
Your personalised snippet is available on the Installation page in your Chameleon Dashboard. Follow the instructions there to add it to your application.
⚠️ If after installing the snippet you see a console error like Refused to load the script 'https://fast.chameleon.io/...', your application has a Content Security Policy (CSP) that is blocking Chameleon. Read How to add Chameleon to your Content Security Policy (CSP) to resolve this.
Go to your Chameleon Dashboard. If you are redirected to a login page, you are logged out.
Chameleon uses passwordless authentication via a login link sent to your email. Enter your email address on the login page to receive a new authentication link. Open the link and your Dashboard will load.
How to fix a third-party cookie issue
Chameleon requires third-party cookies to be enabled in your browser. This is on by default but may have been manually disabled.
To enable third-party cookies in Chrome:
Go to
chrome://settings/in your browser.Scroll to Privacy and security.
Click Content settings, then Cookies.
Switch "Block third-party cookies" to the off position.
If you know that your application has a Content Security Policy, or you see a CSP-related error in the Chrome Extension or browser console, then Chameleon needs to be added to the list of trusted sources that can run on pages in your application. Learn more here.
If you're still experiencing issues
How to clear the Builder cache
If you are authenticated and the snippet is installed but the Builder still will not open, clearing the Builder cache often resolves it.
Open the browser console and type:
chmln.Editor.Router.navigateBack()
If that does not work, refresh the page. With the Builder closed, open the Application tab in Chrome DevTools.
Under Local Storage, find your app's entry.
Locate the key
chmln:l.C.dand delete it. This clears the Chameleon Builder cache only.Refresh the page and try opening the Builder again.
How to collect information for support
If none of the above resolves the issue, collect the following before contacting support:
Open the browser console before loading the page (open DevTools first, then press Refresh).
Take a screenshot of the console output, scrolled to any errors related to
chmln.Type
chmln.isEditingin the console and note the return value.In the Application tab, check that a
chmln-user-idcookie is present under Cookies.
Still stuck?
If you see a CSP error in the console, read How to add Chameleon to your Content Security Policy (CSP).
If the snippet is installed but users are not being identified, read How to identify your users in Chameleon.
Contact Chameleon support with a screenshot of the console and the return value of
chmln.isEditing.