Skip to content

Usage, the MAU cap and your data

This page covers how Beekon Cloud counts monthly active users, how the MAU cap works, and how your data is kept, erased and exported. In the console, these are the Usage page and the user and project pages.

A monthly active user (MAU) is each distinct user id your app set in the SDK, or the device when a location carries no user id. The count is per calendar month (UTC). This is the number Beekon bills: with the next backend release, the organisation’s plan includes a number of MAU per month across all its projects. See Billing: plans, MAU and invoices.

The console shows this month’s MAU in three places:

  • the Monthly active users meter at the foot of the task bar: the count, the cap when set, and the days until the month resets;
  • the Monthly active users figure on the Overview, with a projection for the month’s end;
  • the Usage page, with earlier months and the cap.

User ids and device install ids are counted in one space, so never set a user id that is equal to a device’s install id. If one ever matches, Beekon counts the two as a single monthly active user. Use your own account ids (for example user_8341), not install ids.

The cap. A project can have a monthly MAU cap: a whole number, 1 or more. Owners and admins set, change or remove it on the console’s Usage page (Set a cap…, Change cap…, Remove cap…). The cap alerts; it never stops usage. How it works:

  • Past the cap, new monthly active users are still admitted and counted, and billed like any other. Nothing is refused and nothing is discarded; uploads go on exactly as before.
  • The count the cap is checked against is refreshed every 15 minutes.
  • The meter warns from 80% of the cap and when the cap is passed, and the status pill then reads Over cap. The Usage page and the Overview say the project is over the cap until the month resets or the cap is raised.
  • With a cap set, the project produces billing.usage_threshold events at 50%, 80% and 100%; the 100% event is the over-the-cap alert. Subscribe to them on the console’s Webhooks page or with the Webhooks API.
  • A change reaches the alerts within a minute. Removing the cap stops the alerts until a cap is set again; it changes nothing about who is counted.

See how the platform handles your data.

  • How long locations are kept: the Locations page and Project settings › Data retention say, for example “Locations are kept for 90 days”. The window is set by your plan; locations from the current calendar month are kept at least until it ends. To change it, ask your Beekon contact.
  • Erase a whole project: Erase project… in Project settings (owners only). It deletes all of the project’s data and revokes its keys. The monthly MAU totals are kept as anonymous counts for invoicing.
  • Erase one end user: Erase user… on the user’s page in the console (Users, owners and admins), or from your backend with DELETE /v1/users/{user_id}. It cannot be undone. Erasing a user also removes them from the monthly active users of the current month and of any earlier month whose locations are still kept; the count drops at the next usage refresh. Months frozen because their locations have passed the retention window do not change. The count the cap’s alerts are checked against does not go down: the user stays counted towards the cap until the month ends.
  • Export one end user’s data: Export data on the user’s page in the console (owners only) downloads it as one NDJSON file: their locations (gated and set-aside ones included), trips and trip events, and geofence events.
  • Erase or export one device (install_id): there is no console button or API endpoint yet. Ask your Beekon contact, or reach us through getbeekon.com, with the project and the install_id. See Beekon Cloud.