With Chameleon, you can display Experiences in multiple domains and subdomains. This comes in handy when you want to control your product updates through your deployment process, and you can target multiple Environments differently.
To use this feature, you'll just need to install the Chameleon code snipped on your additional domains and subdomains.
You can use the same Chameleon snippet on all of your domains and subdomains. There is no separate domain-specific configuration required. 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.
👉 Discover the different options for setting up Chameleon.
In the Dashboard, you'll see your entire list of domains and subdomains, and you can further assign them to Environments (e.g. Staging, Production). An Environment is simply a group of domains that you put together and deliver your Experiences to.
Note: with the Startup and Growth plans you have access to 2 Environments, on the Growth plan you can create 4, while on the Enterprise plan you can create unlimited Environments. Contact us to discuss your plan.
We have this feature for 3 reasons:
To allow you to choose where Chameleon Experiences are shown, (e.g. if some users have unique domains when they use your product).
To allow you to use the Builder on any secure domain (go to any website and create an Experience. You won’t be able to set it live for others without the snippet installed there).
To be able to test Experiences alongside new features before they’re deployed to production or general release(e.g. in a staging or beta environment). You can do this with Environments.
In the Domains tab in your Chameleon Dashboard, you'll see all domains and subdomains with the Chameleon snippet that have user activity.
From the Dashboard, you can easily keep a good overview and manage all domains by moving across Environments, archiving, or restoring them anytime you need to. To edit a domain or a subdomain, click its name in the list and hit the "Edit this Domain" button in the top-right corner.
When editing a domain, you can:
check any archived subdomains and restore them.
archive current active domains or disable them using the toggle.
move domains through Environments.
When you're done configuring your domain click "Exit Edit Mode" to apply your changes.
If you no longer want to show Experiences on a domain, you can archive it and keep it in your account in case you'll want to target it again down the line. 😉
By archiving a domain:
All its subdomains will also be archived.
Chameleon Experiences will no longer show on that domain.
No changes to Chameleon Experiences can be made from that domain.
The Chameleon Builder will still show to admins (but with a message to restore the domain to edit Tours).
All subdomains are turned off when their parent domain is archived. If you archive a subdomain, but the parent domain remains active, entering the Builder through the Chrome extension will reactivate that subdomain.
Active users on domains that are disabled will still be counted towards your account usage. This is because the Chameleon code snippet will still be loaded on these pages and we will continue to receive data about these users you are sending.
👉 Learn how Monthly Active Users are defined for your account and how to stay on top of your users count.
To completely remove Chameleon from a page (incl. preventing users from being counted) please remove the Chameleon code snippet from that specific page. You can also consider limiting who the snippet loads for on any page.
Using Environments you can easily deploy Experiences to a specific set of domains. You can also deploy Experiences to multiple Environments.
You can group domains into Environments or move them from one to another, both on the main Domains page, or by selecting one of the created Environments. Click the "Edit Domains" button and use the Actions menu to change the default Environment, archive, or restore domains.
In Edit mode you can also select the Environment for individual domains or subdomains by clicking on the Environment field.
General Rule: If you set a domain's default Environment, it will be applied to all current subdomains without an Environment set. Any future subdomains that are added will also be set to the default Environment.