You can use Chameleon on all your sites with no separate configuration required. Simply use the same Chameleon code snippet you installed initially on any additional domain or subdomain. All domains can be easily managed through your Chameleon Dashboard.
When a new domain sends Chameleon data (because the snippet is installed there and some user activity took place), you will be able to create Experiences and set them live.
Availability & Usage
📍 Ready to build Tours, Tooltips, Microsurveys, Launchers
📈 Users identified on all domains impact MTUs count
How to install across domains
You can display Chameleon Experiences on any domain or subdomain where you've installed the Chameleon snippet. As an administrator for your Chameleon account, you'll be able to use the Chameleon Builder wherever your snippet is installed.
ℹ️ Make sure that the site uses a secure (HTTPS) connection, as this is required to load the Chameleon Builder.
👉 Discover the different options to install Chameleon.
Managing Your Domains
Automatic domain additions
The domain of any page where Chameleon is loaded is automatically added to your saved domains list.
Domains are also added when you load the Chameleon Builder via the Chrome Extension.
Creating environments
Group your domains into Environments from the Domains page in your Dashboard. This enables better control when publishing Experiences live.
Security measures
If you install Chameleon on a domain different from your email domain, it will be automatically disabled. You should manually enable it in your Environments. The same applies to new subdomains added to already-enabled domains. This ensures better security and prevents malicious 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 directly in all your Environments (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
You can load the Chameleon Builder on your local computer to test before deploying to production. Add your Chameleon code snippet locally 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'.