Portal analytics and usage

The developer portal reports each application’s hosted usage and Mesh SDK telemetry. All dates are UTC. Your plan sets how far back the portal shows analytics (7, 30 or 90 days, or longer by agreement); older data is not deleted.

OfflineID

Metric	What it counts
Monthly active users	Distinct people who signed in to the application at least once in the current calendar month (UTC), with any sign-in method. Each guest session counts as one user. Shown for the current month whatever range you select. This is the application’s own count, not the bill.
Verified logins	Successful sign-ins in the selected range: email code, Google and Privy. Guest sessions are not included.
Identities issued	OfflineIDs created in the application, all time.

Sign-ins sent with the application’s older proj_ ID count toward the same application as its app_ ID. A person who signs in to two of your applications counts once in each application’s analytics. Billing counts that person once. Billed monthly active users are counted per organization: a monthly active user (MAU) is a unique end user who signs in to any app in your organization at least once in a calendar month (UTC). Each person counts once per month per organization, however many apps, devices or sessions they use, and a guest counts once per install. The per-application figures can therefore add up to more than the organization’s billed figure. See hosted plans and usage. Daily charts end at today. Projected OfflineID usage in Billing is the organization’s monthly active users so far; it is not extrapolated.

Mesh SDK

Mesh SDK numbers come from the telemetry your app uploads after it calls enableTelemetry. Final daily numbers arrive after the nightly rollup; until then Today is provisional. A day that has not been computed is shown as a gap, not as zero.

Metric	What it counts
Sent on first try	Messages a transport accepted on the first attempt. A message held for an offline peer or sent on a retry is not counted here.
Delivered	Messages from your app’s devices that the recipient’s device acknowledged, counted once per message on the sending device, including messages that were held or retried first. Delivered can be higher than sent on first try.
Failed	Failure reports sent by your devices. Mesh SDK versions before 0.27.0 repeat a report on every retry, so apps on those versions show more failures than occurred.
Delivery success rate	Delivered divided by delivered plus failed.
Latency p50 and p99	Time from first send to acknowledgement. Over more than one day, each is the average of the daily values, weighted by deliveries.
Average hops	Devices a delivered message passed through on its way to the recipient, averaged over deliveries. 0 means it was delivered directly.
Mesh relays	Messages devices forwarded for each other over Bluetooth LE or another local transport. Mesh relays are never billed.
Devices charging	Share of active devices that reported charging at some point in the day, averaged across days. Empty when no device sent a battery update.
Country	Cloudflare’s country for the IP address the upload came from. Offline Protocol does not store the IP address, and the SDK sends no location. Unknown means no country was resolved, for example for events stored before country detection was switched on.
Events stored	Telemetry events stored from your devices, which count toward the telemetry meter. Per-minute metric summaries are not counted. A day counts toward billing once the nightly rollup has computed it.

Proof of Location

Metric	What it counts
Verifications this month	Successful onchain location commits in the current calendar month (UTC), counted once per task, so a retried task is billed once. Commits sent with the older `proj_` ID are included. Failed attempts are not counted. This is the number Proof of Location bills.
Verifications per day	Successful commits per UTC day in the selected range, today included.

Billing usage

Billing shows usage for the organization against each plan quota. OfflineID, hosted relay and Proof of Location usage updates every few minutes; Mesh SDK telemetry updates once a day. Hosted relay deliveries count messages carried by the Offline Protocol hosted relay; mesh relays between devices are never metered. See hosted plans and usage for quotas and rates. To see usage or spend by application, choose one product. Each day’s spend for a meter is shared among applications in proportion to their usage of that meter that day.

Start here

Workflows

Examples and integrations

Operate and ship

Developer portal

Support

OfflineID

Mesh SDK

Proof of Location

Billing usage

​OfflineID

​Mesh SDK

​Proof of Location

​Billing usage

OfflineID

Mesh SDK

Proof of Location

Billing usage