Before publishing your Experience, it's important to ensure it looks and behaves exactly as you intend. You can simulate how your Experiences will display to your users in a few different ways to test them.
ℹ️ This article presumes you've created a Chameleon account, downloaded our Chrome Extension, and built your first Experience.
When configuring your Experience in the Builder, you can quickly jump to Preview mode to check how it behaves and displays. Hit "Preview" at the bottom of the Builder, or in the Builder's Top Bar, and this will take you out of the editing mode.
In Preview mode, you can see how your Experience triggers and interact with it just as your users would.
Preview mode is the quickest and easiest way to see how your Experience displays and behaves. All configurations (such as the buttons, dismiss, triggers, etc.) will behave as for end users. Here are some helpful things to check for:
Does the full Experience flow look as you intended, with the right copy and design?
Is it easy and enjoyable for a user to progress through your Experience?
Are Experiences located on the correct pages and positioned as you desired?
Do Experiences appear in the correct order, and can you navigate easily?
Experiences will only show when the Display criteria are met (correct URL and any element match, or trigger that you have set). In the Topbar, you'll see notifications if the Experience is not configured to show on the current page, or if any URL or element rule is preventing it from displaying.
ℹ️ In the case of Tours spanning across pages, users will only be redirected if you configure the Step button to launch a specific URL or click an element.
Once you have thoroughly checked that your Experience is working correctly, you can publish and test it live in your product. This can help you evaluate your audience targeting and the overall user experience across all Experiences you have live.
ℹ️ The Chameleon code snippet must be installed on your site before you can publish. You can do this directly using JavaScript, or via our integration with Twilio Segment, or Freshpaint. Explore the different options for installing Chameleon.
In the Dashboard, open your Experience and go to the audience settings.
Select "Just Me" as the target Segment. This dynamic audience shows the Experience only to you.
Publish your Experience and open the URL where it should appear.
Verify that it triggers, displays, and behaves correctly.
Once you are happy with everything, update the audience to your real target Segment and click "Apply Changes".
⚠️ Recurrence settings affect testing: If your Experience is set not to repeat, you will only see it once. To see it again, clear your user history (see below) or temporarily set Recurrence to "Every time."
💡 You can group your domains into Environments and publish to your staging domain first to test before pushing to production.
If your Experience is set not to repeat, Chameleon stores your completion history and will not show it to you again. To reset and test from the beginning:
Press the refresh icon next to your user profile.
You can now see your published Experiences as if you were a new user.
ℹ️ Clearing user data does not delete the user entirely. The user attribute "First Seen by Chameleon" is not reset.
Once you're happy with your Experience, you can also get some second opinions from your teammates. To do this, follow these steps:
Invite them to your Chameleon account.
They will receive an email with a verification link. Once they click that and sign in to chameleon.io, they will be considered another Admin user. They will then be able to use the Chameleon Builder wherever the Chameleon code snippet is installed.Update your Experience's target audience
Change your target audience from Just Me to Chameleon Admins, and "Apply the Changes" to your Experience. This will mean that the live version will only go to teammates who are logged into chameleon.io.
ℹ️ Only team members who are added to your account AND have logged in and viewed your Experiences in the Builder will show as Admins. You can target other team members who are not using Chameleon actively as described below. 👇
To share an Experience more broadly with anyone at your company, you can define an audience that targets your team members based on their email domain. This will enable it for everyone who has an email address with the same domain as yours.
👉 For this to work, you must be sending the email as a user property as part of your Chameleon installation. Learn how to do that here.
ℹ️ You can also share Tours via a unique URL that launches them. This requires that the first Step of your Tour has a URL that can be loaded. This may be more complicated if you have dynamic components (such as user ID or account name). Learn how to handle this here.
Once you've tested and you're happy with how the Experience triggers, looks, and behaves, then you can set the right target audience and Apply Changes to your live Experience.
💬 Having issues while testing? If you run into any problems during testing, Copilot can help. Ask Copilot any questions about your setup, and it will suggest fixes and point you to relevant resources to get things working.
👉 Explore different ways for segmenting your users and targeting Experiences.