Jimo’s subscription plans are based on the number of Monthly Active Users (MAU), which represent all unique users detected by Jimo who can interact with experiences and be tracked by success metrics.
MAU (Monthly Active Users) refers to the total number of unique users who visit a page where Jimo is active within a one-month period. This metric is crucial because it determines which users can access Jimo experiences and be tracked within analytics. If your MAU cap is reached, additional users will not see Jimo at all.
⇒ You can check your current MAU from the Billing page of your Jimo project settings.
Jimo offers different MAU tiers from less than 2500 (default) to more than 50000 (custom plan). To see exact pricing for your MAU range, please contact support.
How MAU is Counted?
MAU represents the number of unique users who visit a page where the Jimo snippet is loaded and initialized.
If a user visits multiple pages with Jimo active, they are counted only once within the 30-day period.
MAU tracking resets at the beginning of each new month.
Users must be counted in MAU to view experiences or be tracked by Jimo.
What Happens When You Reach Your MAU Limit?
If your MAU reaches the limit defined in your subscription plan, new users beyond the cap will not be counted, and Jimo will not load for them. This means:
They will not see any Jimo experiences (tours, surveys, banners, etc.).
They will not be included in Jimo analytics and tracking.
MAU limitations
Excluding Internal Users from MAU
Jimo does not differentiate between internal and external users when calculating MAU. This means internal team members interacting with your platform will contribute to the MAU count.
While it is not possible to exclude specific users, you can optimize MAU usage by controlling where Jimo is loaded with Manual Initialization and assure you the Identification is done.
Anonymous Users and Their Impact on MAU
If a user is not identified (i.e., they have no unique user ID assigned), they are classified as anonymous. This means:
Every time they access your platform from a new device or after clearing cookies, they will be counted as a new user.
This can artificially increase the number of MAU, potentially impacting your subscription tier.
Reducing MAU with Manual Initialization
One way to manage MAU is by enabling Manual Initialization of Jimo. This allows you to control where Jimo loads, reducing unnecessary MAU counts.
How Manual Initialization Helps
✅ Pages where Jimo is not initialized will not count toward MAU.
❌ However, Jimo features such as changelogs and experiences will not be available on these pages.
To ensure accurate MAU counting, it is important to properly configure . If Jimo cannot assign a unique identifier to a user, they will be counted as a new user each time they visit from a different device or after clearing their cookies/cache.
To avoid this, ensure that is properly implemented in your Jimo setup.
To implement manual initialization, refer to our guide: