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 production or manage multiple products with different domains.
To manage multiple domains in Chameleon, you'll just need to install the Chameleon code snippet on your additional domains and subdomains. Learn more about installing Chameleon in different Environments.
Once you have this setup, you'll have complete control over where your Experiences show up. This makes it easy to keep your staging and production environments organized, test new features safely, and ensure the right users see the right guidance at the right time 🕰️.
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.
With Environments, you can:
Target Experiences to specific groups of domains or subdomains
Move Experiences easily across your deployment pipeline
Test new features before production deployment
Control which domains display specific Experiences
Use the Builder on any secure domain for Experience creation
Common use cases for Environment control
Selective Experience display: Choose specific domains where Chameleon Experiences appear (useful when users have unique domains)
Builder access: Use the Builder on any secure domain to create Experiences (note: you cannot set Experiences live without the snippet installed)
Staging and testing: Test Experiences alongside new features before production deployment in staging or beta environments
How to Set Up Environments
Chameleon automatically creates Staging and Production Environments. Based on your plan limits, you can add additional Environments as needed.
How to add new Environments:
Navigate to your Chameleon Dashboard
Click on 'Settings' and then 'Domains'
Click the "Add Environment" button in the top-right corner
Assign a descriptive name and description to your new Environment
Choose a color and initials for easy identification
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 can view all domains and subdomains that have the Chameleon snippet installed and show 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 😉.
Editing Domain Settings
You can edit your domains directly from your Domains page, as long as the domain is assigned to an Environment.
Click on the 'Edit' button by the side of your Environment to enter Edit Mode 😄:
When editing a domain, you can:
Check archived subdomains: View and restore previously archived subdomains
Archive active domains: Archive current domains or disable them using the toggle
Move domains between Environments: Reassign domains to different 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.
Managing Subdomains
By default, all domains have at least one subdomain, which can represent the top-level domain when no other subdomains exist.
Accessing and editing subdomains:
Click on a specific domain name
Click "Enter Edit Mode" to access editing options
Use the toggle to disable subdomains
Click the ellipsis (three dots) button to view archived subdomains and archive options
💡 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.
How to restore archived domains
Individual domains: Use the "Unarchive" option for specific domains
Multiple domains: Use 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 (including 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.
👉 Tip: 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.
