With Chameleon, you can display Experiences in multiple domains and subdomains. This comes in handy when you want to test your in-app Experiences in a staging Environment, before publishing to a production one; or when you have multiple products with different domains. Already using URL rules? Also, welcome 3-click domain management!
To manage multiple domains in Chameleon, you'll just need to install the Chameleon code snipped on your additional domains and subdomains. Learn more about installing Chameleon in different Environments.
Availability & Usage
🔐 Startup: 2 Environments
🔐 Growth: 4 Environments
🔐 Enterprise: unlimited Environments
📍 Ready to use in Tours, Tooltips, Microsurveys, Launchers
📩 Contact: to discuss your plan needs
📺 You can watch the video below to quickly learn how to manage Environments and publish Experiences to specific domains and subdomains.
Note: This video does not show the latest version of our product. We will soon update all our videos to fit our new style and improvements. 😊
🎓 An Environment in Chameleon is a group of domains and subdomains that you put together and deliver your Experiences to.
By configuring Environments, you're able to effectively target your Experiences to specific groups of domains or subdomains, and easily move them across your deployment pipeline.
Controlling the domain where an Experience shows up is useful in various cases:
To choose where Chameleon Experiences are shown, (e.g. if some users have unique domains when they use your product).
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 test Experiences alongside new features before they’re deployed to production or general release(e.g. in a staging or beta environment). You can easily do this through Environments.
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).
With this feature, you'll have the Staging and Production Environments created by default, and depending on your plan, you'll be able to add more. You can do so from the "Add Environment" button on the top right side, or from the Environments dropdown when managing your domains.
Next, you will assign a name and a description to the Environment you want to add. We suggest you keep in mind your team's naming conventions and goals, for better visibility of your efforts.
Any additional Environments you create will have a new color automatically assigned to them, but you can change the color and initials anytime. Finally, you can add specific domains to your new Environment.
If you've reached the Environments limit on your account, get in touch with us to review your plan and make sure it meets your needs.
In the Domains tab in your Chameleon Dashboard, you'll see all domains and subdomains with the Chameleon snippet with user activity.
Here, you can keep an overview and manage all domains easily. Glance at the different Environments your domains and subdomains are assigned to and ensure the most relevant ones stay active. Use the column headers to quickly sort your list out 😉
To edit your domains hit the "Enter Edit Mode" button in the top-right corner of your domains list, or on a selected Environment. Now, you can change the assigned Environment, and archive or restore archived domains. When you're done configuring your domain hit "Exit Edit Mode" to apply the changes.
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.
ℹ 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.
To see and edit subdomains click on a domain and hit "Enter Edit Mode", to see the archive option and disable the toggle. Clicking the ellipsis button will show you any archived subdomains and the archive domain option.
ℹ By default, all domains will have at least one subdomain, and that can be a representation of the top-level domain where there aren't any others.
💡 When selecting an Environment, Chameleon will generate a unique ID for it in your URL and you can grab that and share it with that specific Environment filter applied.
If you no longer want to show Experiences on a domain, you can archive it and keep it in your account in case you 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).
When archiving domains, Chameleon will bring up a list of any Experiences that will be impacted by this, so you can review and ensure you're not taking away essential guidance.
To restore archived domains to their prior state and allow Experiences to be displayed there again, you can use the "Unarchive" option for individual domains, or the "Restore" option, under the Actions menu.
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 toward 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 your users.
👉 Learn how Monthly Active Users are defined for your account and how to stay on top of your user count.
To completely remove Chameleon from a page (incl. preventing users from being counted) remove the Chameleon code snippet from that specific page. You can also consider limiting who the snippet loads for on any page.
ℹ Domains with no Environment (s) assigned will display all Experiences, even those assigned to specific Environments.
If an Experience is assigned to an Environment and you have domains assigned as "None" in the Environment (i.e. - no Environment assigned), this Experience will show on all domains with "None" as the domains are not restricted by an Environment tag.
The Environments feature is also visible on the Analytics tab of each Experience, so you can easily update this if you need to.
When you move a domain or subdomain to a different Environment, the analytics will stay the same. We are working to implement separate analytics, but meanwhile, you can use our API call to reset the user history for everyone using the Experience in that Environment.
Once you have your Environments set, you'll be able to publish any Experience within one, the other, or all domains. You can do this during your Experience configuration from the Dashboard. Choose the Environment (s) where you want to publish your Experience from the drop-down menu and you're done!
ℹ By default, your Experience will be shown on 'All Domains' (where Chameleon is installed). Note that this is different from 'All Environments' which may not include all domains and subdomains with the Chameleon code snippet.
👉 You can still use URL rules to further trim down where your Experiences display if you need that extra precision
You can easily Deactivate or Archive multiple Experiences at once, by applying a filter that shows you all your Experiences within a specific Environment. Then you can select them and click the "Bulk Actions" dropdown to access these options.
