Skip to main content
The Analytics page gives you a full picture of how your Bondify authentication is performing over time. Whether you are monitoring a product launch, investigating a drop in logins, or simply keeping tabs on growth, the dashboard surfaces the numbers that matter most — without any additional instrumentation on your end. All metrics update automatically as sessions flow through your projects.

​
Metrics at a glance

The four summary cards at the top of the page give you an instant health-check for the selected time window:
MetricWhat it measures
Total sessionsThe number of authentication attempts initiated — every time a user is sent a Bondify auth request, regardless of outcome.
Confirmed sessionsThe number of sessions that ended in a successful Telegram confirmation from the user.
Unique usersThe count of distinct Telegram IDs that completed at least one authentication in the period. Useful for measuring real user reach.
Conversion rateThe percentage of total sessions that ended in a confirmation (confirmed_sessions ÷ total_sessions × 100).

​
Charts

​
Daily sessions chart

The line chart plots sessions (total attempts) and confirmed logins side-by-side for each calendar day in the selected range. Use this view to spot trends — a widening gap between the two lines indicates more users are starting but not completing the flow.

​
Conversion funnel

The donut chart breaks every session down into four terminal states:
StateMeaning
RequestedSessions initiated (the top of the funnel).
ConfirmedSessions where the user approved the auth request in Telegram.
ExpiredSessions that timed out before the user responded.
CancelledSessions explicitly rejected by the user or cancelled by your server.
Review the funnel alongside your logs to identify the specific friction point that is costing you conversions.

​
Filtering analytics

Use the controls in the top-right corner of the page to focus your view:
  • Date range — choose 7d, 14d, or 30d rolling windows. Longer windows are available on higher plans (see below).
  • Project filter — if you have more than one project, select a specific project from the dropdown to isolate its metrics. Leave it set to All projects for an aggregate view across your account.

​
Plan limits and data retention

The date range you can query depends on your Bondify plan:
PlanAnalytics history
Starter7 days
Pro90 days
BusinessCustom retention
Upgrading your plan unlocks historical data going forward from the upgrade date. Past data that fell outside your previous retention window cannot be recovered.

​
Analytics API response

When you query the Bondify analytics endpoint, the response object contains the same fields powering the dashboard: 
{
  "total_sessions": 1024,
  "confirmed_sessions": 861,
  "unique_users": 740,
  "conversion_rate": 84.1,
  "daily": [
    {
      "date": "2025-01-15",
      "sessions": 120,
      "confirmed": 98,
      "unique_users": 87
    }
  ],
  "funnel": {
    "requested": 1024,
    "confirmed": 861,
    "expired": 97,
    "cancelled": 66
  }
}
FieldTypeDescription
total_sessionsnumberTotal auth attempts in the period.
confirmed_sessionsnumberSessions successfully confirmed.
unique_usersnumberDistinct Telegram IDs that authenticated.
conversion_ratenumberPercentage (0–100) of sessions confirmed.
daily[]arrayPer-day breakdown of sessions, confirmed logins, and unique users.
funnel.requestednumberTotal sessions initiated (mirrors total_sessions).
funnel.confirmednumberSessions confirmed by the user.
funnel.expirednumberSessions that timed out.
funnel.cancellednumberSessions rejected or cancelled.
A low conversion rate usually means users are not completing the Telegram confirmation step. The most common causes are an inactive bot or an unreachable webhook URL. Open the Logs page, filter by expired or cancelled sessions, and verify that your bot is online and your webhook endpoint returns 200 OK.

Projects

Create and manage the projects whose sessions feed into these analytics.

Logs

Drill into individual sessions to understand exactly where users are dropping off.