For the complete documentation index, see llms.txt. This page is also available as Markdown.

MAU (monthly active users)

What counts as a monthly active user in Jimo, what does not, where to read your count, and how to keep it close to your real users.

A monthly active user (MAU) is a unique user who loads a page of your app where Jimo is initialized, counted once per calendar month. The Adoption Suite is billed on this count, so knowing what adds to it is the best way to keep it equal to your real users.

What counts

A user counts as soon as the snippet initializes on a page of your app. With Force Identify on, the snippet does not initialize before it receives an identify call, so the user counts only from that call.

Three cases side by side. An identified user on a laptop, a phone and a tablet counts as 1 MAU. An anonymous visitor on the same three devices counts as 3 MAU. A page where Jimo is not initialized counts as 0 MAU

One count per user per month

A user who opens ten pages, or comes back every day, counts once in the month. The count starts again with each calendar month.

Anonymous visitors, once per device

Without an identify call, Jimo cannot recognize a returning person. Each new device, browser, or cleared cache counts as a new user.

Your own team

Internal users, QA and demo accounts count like any user: Jimo does not know they are internal. You can keep experiences away from them with a segment, but they still count.

Impersonation sessions

When your support staff log in as a customer and the identify call runs, the session counts as that customer.

Staging and production of the same project

Both count toward the same project's MAU.

What does not count

Pages where Jimo is not initialized

A page without the snippet, or excluded with manual initialization, adds nothing. It also shows no experience.

Sessions blocked by Force Identify

With Force Identify on in Installation, Jimo starts only after an identify call, so no anonymous session ever reaches the count.

Force Identify off: the page loads, the snippet initializes and the visitor counts as MAU, identified or anonymous. Force Identify on: the snippet waits for the identify call, then initializes and the user counts

Keep MAU close to your real users

Lever
Effect
Where

Identify every logged-in user

One person is one MAU, whatever their devices

Force Identify, if every user is logged in

No anonymous MAU at all

Manual initialization

Jimo loads only on the pages where experiences live

No identify during impersonation

Staff sessions do not land on customer profiles

Publish to named environments

Developers on localhost do not see experiences

Read your count

Your MAU for the current month is on the Billing page of the project settings, in the MAU for the current month block: the count against the limit of your plan, then the anonymous share, for example 1,298 / 50,000 MAU - 76 anonymous (6%). A large anonymous share usually means the identify call is missing on some pages, or runs too late.

Settings, Billing, MAU for the current month: the count against the plan limit (A) and the anonymous share (B)

Numbers that are not your MAU

Identified users from Jimo SDK, in Users & Segments, counts every user ever identified in the project, since the start. It only grows, so it is usually higher than one month's identified MAU. A segment such as "last activity in the past 30 days" uses a rolling window, while MAU follows the calendar month, so the two rarely match exactly.

MAU follows the calendar month, a last-activity segment a rolling 30 days, and Identified users from Jimo SDK everything since the project started

When you reach your limit

Jimo alerts you as the project approaches and reaches its MAU limit.

  • Users beyond the quota do not see your experiences. Once the limit is reached, a new active user of the month does not see them.

  • Users already counted keep seeing them as usual. Users counted within the limit this month see your experiences as before.

The Billing screen says the same: "If you reach the limit, new active users will not view your experiences. Users active this month can still view them."

To raise the limit, move to the next tier of the Jimo pricing: pick a higher tier yourself with the MAU stepper in Settings > Plan, or ask support from the chat. See Plan and billing.

Verify

Log in to your app on a second browser with the same account: the MAU count does not move. If the count and its anonymous share grow instead, your identify call is not running.

Go further

Next page: Notifications and account settings

Last updated