It is possible to use Chameleon on all your sites. To do so, 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.

💡 Keep in mind that users from all domains will start adding to your MTUs count.

Using Chameleon on multiple domains and subdomains

You can show Chameleon Experiences on any domain or subdomain where you've installed the Chameleon snippet. Just make sure that the site uses a secure (HTTPS) connection, as this is required to load the Chameleon Builder.

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.

You can control which Experiences show on which pages using the Environments feature from the "Domains" page under Settings from your Chameleon Dashboard.

Here you can add domains and subdomains to specific Environments and control where you want to show each Experience.

💡 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.

Note: 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.

Installing locally

You can load the Chameleon Builder on your local computer if you would like to first test it locally before deploying it to production. To do this, you will add your Chameleon code snippet locally and reload the page.

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".

A note about authentication

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).

Know more

Did this answer your question?