The Monitor group of the task bar holds the pages you watch the project from. They are read-only for every role, except device commands and erasing or exporting a user.
Coming soon. Today each device and user page has its own map, and Locations shows each location on a map in its details panel.
Locations
Section titled “Locations”Every stored location in the chosen time range, newest or oldest first, 50 to 500 a page (100 by default). The page also says how long the project keeps its locations, for example Locations are kept for 90 days, or Locations are kept until deleted. When the range reaches back past that, a banner says Locations before time were deleted and the range starts there.
| Control | What it does |
|---|---|
| Daily totals | Tiles above the table, by UTC day, for ranges up to 92 days: Accepted, Gated, Low accuracy, Implausible speed, Mock location and Devices sending (the most in one day). Choose a gated total to list those locations, or a day’s bar to narrow the range to that day. |
| Update | Moves the end of the range to now. |
| Filters | Device, User, travel mode (Any travel mode, or Still, Walking, Running, Cycling, Driving, Unknown; see Location mode) and status: Accepted (the default), Accepted and gated, Gated: low accuracy, Gated: implausible speed or Gated: mock location. Clear filters removes them all. |
| The 24-hour limit | A filter by device, user, travel mode or gate reason covers at most 24 hours. With a wider range the page asks you to Narrow the range to 24 hours. |
| Columns | Picks the table’s columns, each shown with its API field name. Reset columns restores the default set. |
| Auto-refresh | Off by default. When on, checks every 30 seconds for locations newer than the range and offers ↑ 12 new locations since 14:05 · Show them. |
| Jump to time… | Moves the page to a time inside the range. |
| Copy link / Export | The current view; the current page as CSV or JSON. To fetch more, use GET /v1/locations. |
A gated location passed the SDK’s own time-and-distance gate but failed a server check (low
accuracy, implausible speed or a mock location). It is stored and flagged, not dropped, and its
Flags cell reads Gated · low accuracy. The thresholds are
the Filters in Remote config. See
gated locations. A
Self-reported: low accuracy tag is different: it is the device’s own
opinion of the fix (the location’s quality), not the
server’s decision, and the tag shows whatever value the upload carried.
Choosing a row opens its details: the location on a map with its accuracy circle, then Where, When, Device, Movement and power, Flags, any custom fields, and the location id. Filter to this device, Copy link and Copy JSON are at its foot.
Journeys cut from each device’s locations on the server, in the chosen time range. A trip is listed when any part of it falls inside the range. Filter by Device or User (no 24-hour limit) and by Status (Any status, In progress, Stalled or Completed), and sort newest or oldest first. The status filter works in the console: it looks through a few pages of trips for each page it shows, and says how many it looked through. Jump to time… moves the page to a time inside the range. The header notes that trips are Retained with location data: they are kept as long as the locations they were cut from. While activity detection is off, a note says travel mode is reported as Unknown and links to Detect activity in Remote config.
The table shows each trip’s status (In progress, Stalled or Completed), device, user, travel mode, distance, duration, average speed, number of locations and end reason. Columns adds more. The end reasons are:
| End reason | Means |
|---|---|
| Stop detected | Within the stop radius for the stop duration. |
| Data gap | No data within the gap interval. |
| Session change | A new SDK session started. |
| User change | The user id changed. |
| Project change | The project key changed. |
| Stopped by the app | Your app called stop(). |
| Ended after no contact | The device sent nothing for End after no contact. |
See when a trip ends for what each means in the API. An end reason not in this table shows as its API code.
A trip is Stalled when its device has sent nothing for Stall after no contact, or was marked unreachable. The row says No signal since time, the device’s last contact, and its end reason is Not ended yet. A new location moves the trip on again; with no contact for End after no contact (24 hours by default), the server ends it. An in-progress trip with no location for longer than the gap interval, but not yet stalled, says Inactive for time. The radius, duration, gap and the two no-contact times are the Trips settings in Remote config. Auto-refresh is off until you turn it on; when it is on, it re-reads the first page every 30 seconds, so trips in progress stay current.
A trip’s page has its figures (Distance, Duration, Average speed, Max speed, Locations, End reason), the Route on a map coloured by travel mode, its Legs where the mode changes, a Speed chart, Details, Travel mode shares and Locations in this trip. It draws up to 2,000 locations; Load all reads the rest. View locations, Copy link and Export (the trip as JSON, its locations as CSV or JSON) are in the header. The route switches between By travel mode and One colour. When Auto-refresh is on, it re-reads a trip in progress every 30 seconds. A stalled trip shows the banner Stalled · No signal since time with a Trip settings button, which opens the Trips settings in Remote config. See Trips.
Events
Section titled “Events”The project’s events of the last 7 days, in the order Beekon recorded them, oldest at the top;
the page opens at the newest. GET /v1/events and your
webhooks carry the same events. Events are kept 7 days,
so the page has no time range.
- All, Geofences, Trips, Devices and Usage alerts choose the type. Each row shows when it happened (the device’s time), the event, its subject (the fence, the trip, the device or the MAU threshold), the device and the user.
- The event words are Enter, Exit, Dwell, Trip start, Trip stalled, Trip end, Unreachable, Back in touch and Usage alert.
- A geofence event that does not rest on the device’s own locations carries a tag that names its evidence: Drive-through (two locations either side of the fence, none inside, on a fence that counts drive-throughs), Confirmed by the device (the device reported the crossing and a location agreed) or Lost contact (an exit sent when Beekon lost contact with a device inside the fence). Late marks an event of a visit that reached Beekon after it was over.
- A device event’s subject is the device’s model and why, such as Model unreachable · silent while moving (or rest limit, tracking stopped, permission lost), with the last contact under it; Model back in touch says how long the device was silent.
- Find on this page narrows the loaded rows only. Copy link, Export (JSON exactly as served, or CSV) and Auto-refresh (the newest page only) work as elsewhere.
- Oldest, Older, Newer and Newest page through the 7 days.
- Choosing an event opens its details, with links to the fence, trip, device and user, the webhooks that take its type today, the event as JSON, and Copy event id. It never says whether one event was delivered: its link Webhooks › Deliveries opens the Webhooks page, where each webhook lists its Recent deliveries.
Devices
Section titled “Devices”Every device that has synced at least once, by install id, 50 to 500 a page. The status chips filter the list:
| State | Means |
|---|---|
| Online | A location in the last 24 h, and no issue. |
| Issues | It can’t send, or its locations are gated or set aside: location permission or location services off, a wrong device clock, locations gated, or Battery Saver / Low Power Mode on. |
| Offline | No location in the last 24 h. |
| New | Registered, never sent a location. |
| Outdated config | Runs an older remote config revision than the project serves. This is a config state, not a device state, so a device can be Online and Outdated config. |
Search matches part of an install id, a model or a user id. The table shows the device, its state and reason, user, last location, locations today (with how many were gated), battery, config revision, platform with SDK version, and reachability.
Reachability is whether the server can still hear from the device (presence): Reachable with Last contact time, or Unreachable with its reason (Silent while moving, Rest limit reached, Tracking stopped or Location permission lost). A health report counts as contact, so the last contact can be newer than the last location. It sits beside the state and never moves a device between the chips. A dash means no contact since presence tracking began.
A device’s page has View locations, View trips, Copy link and Send command in its header, with the device’s Last location under its name, then six figures: Last location, Locations today (with how many were gated), Battery, Queued on device, Set aside · 7 days (locations set aside because the device’s clock was outside the window the server accepts; they are not stored as locations, see Ingest) and Remote config. Below them come today’s locations on the Last known position map with geofences underneath, Locations and filters, Recent trips, Health (as the SDK reports it), Remote config, Commands and Details. A banner names the first thing wrong, for example Location permission is off or The device clock looks wrong when locations were set aside.
The page also shows Last contact under the device’s name and Reachability and Last contact in Details; a stalled trip in Recent trips says No signal since time; and the banner can say Unreachable · reason while the server can’t hear from the device.
Attestation shows whether the install proved it’s a genuine copy of your app: Attested, Not attested, Revoked or Denied, with the Method (Hardware key attestation, Play Integrity or App Attest), for hardware key attestation the Key (Remote-provisioned or Factory), and the dates. Owners and admins can Re-verify, Deny and Clear it (Device integrity). It is hidden on a deployment without attestation.
Send command (owners and admins) sends a command the device runs at its next sync:
- Flush uploads everything queued on the device now.
- Upload logs sends the device’s diagnostic log lines, already redacted (no coordinates, no secrets), optionally between two times. View logs reads them.
Give up after (10 minutes to 7 days, 1 hour by default) sets when an unrun command expires. At most 20 commands can be waiting on a device. See Devices.
Every user id that at least one stored location carries, 50 to 500 a page. A user’s state is the best of its current devices’ states: the chips are All, Online, Issues and Offline. Search matches the start of a user id and is case-sensitive. The table shows each user’s state, devices, last location, the geofence they are currently in, and whether they count in this month’s MAU. A note under the list counts the devices that send locations without a user id, with a link to them in Devices.
A user’s page has their figures (Last location, Currently at, Locations today (UTC), Battery, Stored, MAU), Where they’ve been (one line per device), Trips, Places (their geofence crossings), Devices now, Also used in the last 24 h (devices that sent this id and now send another or none), Sent by your app (the extras on their newest location) and Months in MAU.
- Export data (owners only) downloads everything the project stores under the user id as one NDJSON file: locations, including gated and set-aside ones, trips and trip events, and geofence events. The export is recorded in the audit log.
- Erase user… (owners and admins) deletes the user’s stored locations, trips and geofence events in this project only. Type the user id to confirm; it can’t be undone. Erasing takes about 4 minutes, because it waits for uploads already on their way. The user leaves the MAU of this month and of every earlier month whose locations are still kept, at the next usage refresh, but still counts towards the cap until the month ends. A device that still sends the id adds the user again. See Users and your data.