With Chameleon, you have full control over how, where, and when your Experiences appear. 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.


Note: with the Startup and Growth plans you have access to 2 Environments, while on the Enterprise plan you can create unlimited Environments. Contact us to discuss your plan.


Quick access


A Chameleon Environment is a group of domains or subdomains to which you can deliver Experiences.

With Environments, you can always make sure your Experiences are seen by the right users. This is very useful when building features that you want to move from a Staging domain to a Production one. Or when you have multiple web pages that cater to different audience groups.


Publishing your Experience to an Environment

To help jumpstart your Chameleon flow, here is the step-by-step process to adding Experiences to an Environment.

You can access and manage Environments from the "Domains" section under Settings from the Chameleon Dashboard. With this feature, you'll have the Staging and Production Environments created by default.

If you want to create a new Environment, you can do so from the "Add Environment" button on the top right side.

Next, you will assign a name and a description to the Environment you want to add.

🎯 Any additional Environments you create will have a new color automatically assigned to them, but you can change the color and initials anytime. Use them strategically to help you stay organized. 😉

Once you have your Environments set, you'll be able to publish any Experience within one, the other, or all domain groups. 😉 You can do this during your Experience configuration from the Dashboard after you style it. Choose the Environment (s) where you want to publish your Experience from the drop-down menu and click Done.


Managing your domains with Environments

With Chameleon Environments, it is easier than ever to control where your Experiences are displayed. Already using URL rules? Also, welcome 3-click domain management!

If you want to move your domains from one Environment to another, go to the Domains page, scroll down to Manage Domains, and click on "Edit Domains".

You can select multiple domains and subdomains and click on "Actions". Now, you can change the default Environments, Archive them, or Restore them if they were previously archived. When you're done, click on "Exit Edit Mode". Easy-peasy!

environments bulk actions for domain & subdomain management

When managing Experiences, if a new subdomain is detected and the parent domain is assigned to an Environment, the new subdomain will also be assigned to that environment.

This way, you can fast-check the different deployment domains for all your Experiences. Also, anytime you want to adjust where your Experiences show up, you can do it quickly and precisely.

👉 Learn more about managing your domains with Environments from this article.

The Environments feature is also available from the Analytics tab of each Experience. Always know where the Experience is set to show up and quickly 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.


Deactivating all Experiences from an Environment

You can do this by applying a filter that shows you all your Experiences within a specific Environment. Then you can select them and click on the "Actions" button. This way, you can apply bulk actions, including Deactivate, to your Experiences, for fast and complete management.

💡 You can still use URL rules to further trim down where your Experiences display if you need that extra precision.

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.


Need more?

Did this answer your question?