Identifying your users is a very important step in getting Chameleon up and running. Your users have to be identified by Chameleon for Experiences to be seen by users on your app.
Checking the Chrome extension
Clicking on the Chrome extension and seeing this “Viewing as” section means that Chameleon is identifying users on your page.
Run chmln.data.profile in the browser console
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.
Here are some issues you might encounter when trying to identify your users:
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.
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.
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 MAU count, as each anonymous user is counted as an additional user.
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.