Chameleon's pricing is linked to the number of end-users (your product's users) as that directly impacts our cost basis (via the number of API calls made).
Our Free and Startup plans are directly proportional to these users, while our Growth and Enterprise plans offer larger buckets of usage, to give you room to expand.
You can view our pricing plans and use the slider to estimate your cost below:
Used for accounts created after March 28, 2021.
MTUs are all unique users identified by Chameleon (from any source) on a 30-day basis. This includes users who visit your app and are identified by Chameleon, via the chmln.identify call, or users added manually.
It is not simply just the number of users that saw an Experience or those in any target audience, but all users that Chameleon identifies with a unique user ID.
The MTU count includes:
Users identified as part of installing the Chameleon code snippet into your application (using JS).
Users identified to Chameleon via Segment (including data sent from the client-side and server-side) even if they do not visit your application/load any pages from your product.
Users identified to Chameleon via another integration or via webhooks, API etc. (again, even if they do not visit your application.)
Unique users are identified by their unique ID sent to Chameleon. This means that a user could visit your application from different browsers/devices/locations etc. but would only be counted once.
The period of tracking MTUs is the previous 30-day period; this means that we don't aggregate ALL users historically, unlike some other applications, but focus on users that have the potential to benefit from Chameleon tours.
Upon your billing date, we will count the maximum number of MTUs in the prior period (month or year) and charge accordingly. If you have any questions about billing feel free to email us.
Used for accounts created before March 28, 2021.
MAUs are all unique user profiles sent to Chameleon (from your product/client-side, i.e. JS snippet or Segment/Freshpaint client-side API calls) from your account within the last 30 days.
This includes all unique users that load any page on which Chameleon is installed in the previous 30-day period.
If you install Chameleon on your marketing site or send anonymous users as unique IDs then these will also be counted separately. We recommend making sure you only install Chameleon where you intend to show Chameleon Experiences.
If you don't already know your product's MAUs, you can find this from your analytics solution (such as Google Analytics, Mixpanel, Amplitude, Heap etc.) by looking for unique users that loaded a page in the previous month. You could also ask your developer to obtain this information from your database.
Within Google Analytics:
Head over to your Google Analytics account
Ensure you're loading the correct project (in the top left) -- use the project for the application where you'll be installing Chameleon (i.e. not for your marketing site)
Within the 'Audience' section, select 'Active Users'
Check the '28 Day Active Users' data-set (this will be a close approximation to your monthly active users)
ℹ If you don't have a project for just your application, then an alternative way to find this information is by going to Behavior > All Pages, then searching for the most visited page in your product, and evaluating the total unique users in the previous month. Read this StackOverflow answer for more info.
Chameleon can count your users once you have successfully installed the Chameleon code snippet. You can then view your count from your Chameleon Dashboard:
How can sending data to Chameleon impact MTUs?
In some cases, non-app visits or sending additional data to Chameleon can impact MTUs. Here are a few common scenarios and how they can impact your MTUs:
Sending segments/cohorts via integrations
When syncing audiences from other integrations (e.g. Mixpanel, Amplitude) Chameleon will update existing user profiles (based on their UID) and this will not add new MTUs to your account. Consider this as updating existing user profiles, rather than adding new ones.
ℹ The number of users showing exported within your integration dashboard and showing as matching within Chameleon may vary if some users have not been seen since Chameleon was installed and did not identify them (therefore Chameleon has not "seen" these users and will not have those in the database.)
ℹ In the case of CDPs, like Segment, for Chameleon to identify users you'll have to ensure that the analytics.identify() call is ran. You can also use this call to "turn off" Chameleon for your marketing site for example: analytics.identify(userId, traits, { integrations: { Chameleon: false } }). You can also add additional filters in Segment to ensure you're only sending the data you want to Chameleon.
CSV imports
With CSV imports, only the users who are identified by Chameleon will be tagged and counted toward your MTUs. For example, if you upload a CSV with 300 users and only 50 are identified by Chameleon, then only those will be counted.
👀 Careful when leveraging CSV to update user properties - ensure you pick the email to map properties for existing (already identified) users. If you map to the UID Chameleon will update existing properties AND create new user profiles for new ones.
Via API
If you send data to Chameleon via our REST API this counts as introducing new users to Chameleon. Each user will have a UID assigned and will be added to your total MTU count, even if they never visited your app or haven't visited in the last 30 days.
👀 Careful to not send to Chameleon user profiles/data from users that do not exist in your app, such as from your marketing website. Those users will be considered for your MTU count, despite Chameleon not being installed on your marketing website.
👉 Read how to limit your Chameleon installation to a subset of users.