Identifying your users is a critical part of your Chameleon installation. Without that, Chameleon Experiences will not display to users. To identify users you must send a unique ID for each logged-in user. You can learn more about installing Chameleon from this article.


Quick access


How can I check if my users are identified?

To ensure you're set to display Experiences to your end-users, there are a few ways you can see whether they are identified in Chameleon. Let's go through the steps you'll want to check:

Data being received correctly

Check in your Chameleon Dashboard's Installation page that a green banner is displayed indicating that data is being correctly received. This does not prove that users are being identified correctly but does indicate that the user identification method is being called.

You can also double-check this per domain from the 'Verify installation' tab of the same Installation page:

Here, you test each domain to check whether Chameleon receives data correctly.

Check the Chrome extension

If there are issues with your installation, the Chameleon Chrome Extension will notify you of any errors that need your attention. Click to open it in your product and review whether any messages show up, like the one below.

This message indicates that you are on a domain or subdomain that does not have Chameleon installed, and you should check that in the 'Verify Installation' tab.

If no error shows up you can review the user identified by Chameleon on the underlying page. If this is not you - the person logged into the application, then this can indicate a problem.

Check console data

Opening the browser console and running chmln.data.profile will bring up data about the user that is currently logged in and being identified. If this returns an error message, then users aren’t being identified on the page.


Common issues

Here are some of the most common reasons when user identification breaks or is not successful:

Users are not being identified on single-page applications (SPAs)

User data is sent to Chameleon when it is available on a web page/application. For some apps, this data is loaded after the page loads and is sent to Chameleon after a small delay.

To get around this, you can get the engineers on your team to call the chmln.identify() method, and send that data to Chameleon as soon as the page is loaded.

Users are not being identified or re-identified when a page is being loaded

Data on a web page should be sent immediately after the page is loaded. This is most likely caused by an issue with how Chameleon has been installed. We recommend involving your engineers to make sure that Chameleon is being loaded as soon as the page loads, including when it is reloaded.

👉 Learn more about how to install Chameleon

Anonymous users not being identified

When installing Chameleon, we ask developers to identify users by their unique ID. For users who don’t have a logged-in identity (e.g. visitors), we recommend generating a unique ID and storing it in a cookie, which will then be read afterward.

Please note that identifying anonymous users to Chameleon will have an impact on your MTU count, as each anonymous user is counted as an additional user.

👉 Learn more about how to show Experiences to anonymous users

User ID isn’t the same as seen in your tech stack or other integrations

You should have a single unified user ID that can be used across different integrations and is common across all apps.

👉 Have any questions or issues? Review the best way to get help.


Learn More

Did this answer your question?