Skip to main content

What does 'users' mean in the context of Unlayer, and how does user counting work?

Danial A K Tareen avatar
Written by Danial A K Tareen
Updated over 3 months ago

Understanding Users and User Counting in Unlayer

Unlayer defines a "user" as any end-user of your host application who opens and interacts with the Unlayer builder. Understanding how users are counted is essential for managing your subscription effectively.

Definition of 'Users'

  1. A user is an end-user (not a developer or admin) who loads the Unlayer builder in your application.

  2. Users are uniquely identified using the user.id field passed in the unlayer.init() configuration.

    unlayer.init({

    user: {

    id: 'user-001', // required for accurate tracking

    name: 'Jane Doe',

    }

    });

    Reference Docs: End-User Identification

  3. Certain internal team roles, like Project Owners, Admins & Members are excluded from the user count. These roles are considered part of your administrative backend rather than active users.

How User Counting Works

  1. Monthly Active Users (MAU): Unlayer counts each unique user.id that opens the builder during your billing cycle.

  2. If you do not provide a user.id, Unlayer will treat all users as a single anonymous user — which avoids overcounting but also disables user-specific features such as user-saved blocks and personalized content.

Impact of Subscription Plans

  • User limits depend on your Unlayer subscription tier. You can reach out to Unlayer Customer Support for more information on this.

  • If your usage exceeds the allowed number of users, you may need to upgrade or adjust your implementation to stay within limits.

Conclusion

Accurately identifying and counting users is essential to staying within your Unlayer subscription limits and avoiding unexpected overages. By consistently passing a unique user.id and understanding how Monthly Active Users (MAU) are calculated, you can ensure fair usage tracking and plan appropriately for growth. For higher user volumes, consider upgrading to a plan that supports your scale.

Did this answer your question?