Using Chameleon on multiple domains / sites
You can use the same Chameleon code snippet on all your sites, If you are logged-in then you will be identified as an administrator for your Chameleon account, and see the Chameleon Editor wherever your snippet is installed.
Note: all admin users on your account will have access to the Chameleon Editor and all tours on all sites within your account. You can invite other collaborators here.
To make sure the tours show on the correct sites, you can use the URL matching for each step. To learn more about this, see URL matching.
Using Chameleon on multiple subdomains
You can show Chameleon tours on any domain or subdomain where you've installed your Chameleon snippet. Just make sure that the site uses a secure (https) connection, as this is required to load the Chameleon Editor.
You can control which tours show on which pages using the URL trigger for each step. You can also use wildcards or user variables to match dynamic parts of the URL. Learn more about that here.
We recommend implementing the Chameleon code snippet directly on all your environments (staging and production). Users will not notice this - no tours are published without explicit action from you. Doing so will save you engineering time.
Because Chameleon recently started requiring a secure connection (https), you may need to use a localhost proxy such as ngrok to load Chameleon on locally hosted pages.
You can load the Chameleon Editor on your local computer if you would like to first test locally before deploying to production. To do this, simply add your Chameleon code snippet (available here) locally, then simply reload the page.
The Chameleon Editor should appear. Viewing Tours on a
http://localhost (e.g. "localhost:3008" or "localhost:4000") will be disabled (for security reasons) until you explicitly email us to enable this localhost url and its associated port number.
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." Disable them here.
A note about authentication
To keep you authenticated (to identify you as an admin and show the Chameleon Editor) we store your authentication information in an encrypted, HttpOnly, secure cookie that is and only served to us over a secure connection (https).