Chameleon can be installed on all your sites with no separate configuration required. The same Chameleon code snippet you installed initially works on any additional domain or subdomain. All domains can be managed through your Chameleon Dashboard.
When a new domain with the Chameleon snippet installed generates user activity, that domain becomes available for creating and deploying Experiences.
Availability & Usage
📍 Ready to build Tours, Tooltips, Microsurveys, Launchers
📈 Users identified on all domains impact MTUs count
Installation Process
To display Chameleon Experiences on any domain or subdomain, you need to install the Chameleon snippet on each site. As an administrator, you can use the Chameleon Builder on any site where the snippet is installed.
Security Requirement: The site must use a secure (HTTPS) connection to load the Chameleon Builder.
👉 Discover the different options to install Chameleon.
Managing Your Domains
Automatic domain additions
Domains are automatically added to your saved domains list in two ways:
When Chameleon loads on a page with that domain
When you load the Chameleon Builder via the Chrome Extension on that domain
Creating environments
You can group your domains into Environments from the Domains page in your Dashboard. This enables better control when publishing Experiences.
Security measures
Chameleon implements security measures to protect your account:
If you install Chameleon on a domain different from your email domain, it will be automatically disabled
You must manually enable new domains in your Environments
This also applies to new subdomains added to already-enabled domains
These measures prevent unauthorized domains from being added to your account
Targeting specific pages
You can use rules to further specify where your Experiences display if you need extra precision.
Implementation Best Practices
We recommend implementing the Chameleon code snippet in all your Environments (both staging and production). This approach:
Remains invisible to end-users (Experiences aren't published without your explicit action)
Saves engineering time
ℹ️ All admin users on your account will have access to the Chameleon Builder on all sites within your account. You can invite other collaborators here.
Setting up locally
To test Chameleon before deploying to production, add your Chameleon code snippet to your local development environment and reload the page.
ℹ️ Chameleon servers must initiate communication with your machine to load the Builder, settings, and Experience data.
HTTPS requirements for local development
For security reasons, Chameleon only loads on secure HTTPS connections. To create HTTPS connections locally, use one of these methods:
Create an HTTPS certificate for your local environment using a tool such as mkcert for OSX (separate instructions available for Windows)
Use a reverse proxy such as ngrok to load locally hosted pages on an HTTPS domain
Use a Flag in Chrome to force a local domain to be considered secure
Chrome cookie settings
Due to recent Chrome updates, you may need to disable the Chrome flags "SameSite by default cookies" and "Cookies without SameSite must be secure."
How authentication works
To identify you as an admin and display the Chameleon Builder, authentication information is stored in an encrypted, HttpOnly, secure cookie that is only served over a secure connection (HTTPS).
You can open any Experience and test it out in the Builder:
press 'Shift' 3 times in a row
enter the Experience ID into the text input that opens on your screen
press 'Enter'
The Builder will load your Experience, and to exit the dialogue just press 'escape'.