It is possible to use Chameleon on all your sites with no separate configuration required. You just need to use the same Chameleon code snippet you used to install it in the first place on the additional domain or subdomain. And you can easily manage these in 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
You can show Chameleon Experiences on any domain or subdomain where you've installed the Chameleon snippet. If you are logged in, you will be identified as an administrator for your Chameleon account and you will be able to use the Chameleon Builder wherever your snippet is installed.
ℹ Just 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.
ℹ The domain of that page is also automatically added to your saved domains list. Domains are also added when you load the Chameleon Builder on any page by clicking the Chrome Extension.
Group your domains into Environments from the Domains page in your Chameleon Dashboard. Here you can add domains and subdomains to specific Environments and this enables better control when you publish Experiences live.
ℹ If you install Chameleon on a domain that's different from your email domain, it will be automatically disabled, and you should manually enable it in your Environments. The same goes for new subdomains that you add to already-enabled domains. This is to ensure better security and that no malicious domains get added to your account.
💡 You can still use URL rules to further trim down where your Experiences display if you need that extra precision.
We recommend implementing the Chameleon code snippet directly in all your Environments (staging and production). Your end-users will not notice this, as Experiences are not published without explicit action on your part, and you will save precious 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.
You can load the Chameleon Builder on your local computer if you would like to test it locally before deploying it to a live production environment. To do this, you will add your Chameleon code snippet locally and reload the page.
ℹ Chameleon servers need to initiate communication with your machine to load the Builder, settings, and Experience data.
For security reasons, Chameleon can only be loaded on secure HTTPS connections. To load your local sites on an HTTPS connection, you will need to use one of two strategies:
Create an HTTPS certificate for your local environment using a tool such as mkcert for OSX. See instructions here for Windows environments.
Use a reverse proxy, such as ngrok to load your locally hosted pages on an HTTPS domain.
Use a Flag in Chrome to forcefully consider a local domain as secure.
Lastly, due to a recent update in how Chrome handles cookies, you may need to disable the Chrome flags "SameSite by default cookies" and "Cookies without SameSite must be secure".
To keep you authenticated (to identify you as an admin and show the Chameleon Builder) we store your authentication information in an encrypted, HttpOnly, secure cookie that is only served to us 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'.