Pulse · Growth
Home Funnel Admin Permissions Reports

Sign in to Pulse

Enter your email — we'll send a magic link, no password needed.

Link sent to . Check your inbox.

Access pending

You're signed in, but your account isn't on the Pulse allowlist yet. Ask vamsee@scalability.club to add you in tasks.members.

Sync status

Metabase → Supabase pipeline
Loading…
View sync detail
SourceLast sync (IST)Last batchSync IDStatus
Loading…
Delivered orders
—
 
Winnable demand
—
interim proxy: >15s cancels + assigned
Capture of winnable
—
delivered ÷ winnable demand
Median fulfillment
—
assigned → delivered

Order funnel

the master view: every broadcast order → shown → accepted → fulfilled
Loading…
Standardized definitions
Total ordersEvery network order broadcast to Bounce in the period (by created time). Includes orders that cancel in seconds.
Shown to ≥1 rider≥1 order-ping logged for the order. Measures pings actually sent, not eligibility. The ping feed can lag the order feed by a few days — check Sync status before reading the latest period.
AcceptedA rider was assigned to the order (assignment observed in order states — same definition as the accept-rate panels).
FulfilledOrder reached state DELIVERED.

Fleet overview

every week on record — the scope bar above drives everything below

Weekly trend

Monday–Sunday · every complete/in-progress week on record
WeekRiders engagedRiders w/ orders% zero ordersMedian ordersOrders/login-hrTotal ordersAvg drop km
Loading…
Active riders
—
 
Utilization
—
% of engaged fulfilling ≥1 order
Orders / active rider
—
delivered ÷ active riders
Accept rate
—
pinged → assigned & delivering

Rider funnel

the master view: every engaged rider → online → pinged → accepting → fulfilling
Loading…
Standardized definitions
Total ridersRiders engaged: any session or ping recorded in the period.
Online ≥ x minTotal online duration in the period ≥ the cutoff (paired online/offline events from rider sessions). Cutoff selectable above.
Got ≥1 pingReceived at least one order ping. The ping feed can lag the order feed by a few days — check Sync status.
Accepted ≥1Accepted at least one order (pinged → assigned & delivering — same definition as the accept-rate panels).
Fulfilled ≥1Delivered at least one order in the period.

Rider engagement

who showed up, how long they stayed online, what they carried

New vs. old riders

tenure ≤7d vs >7d since first session
SegmentRiders% zero ordersMedian ordersMean ordersMean pingsMean login hrs
Loading…

Login-hour split

Rider-days, by daily login duration
Login hoursRider-days% zero ordersMedian ordersMean ordersOrders/login-hr
Loading…
Orders/login-hr flat across buckets = day-level averages are skewed by hours logged in, not by rider productivity.

Orders/hr by drop distance

Rider-days with ≥1 order, by avg drop distance
Drop distanceRider-daysAvg login hrsAvg ordersOrders/login-hr
Loading…

Overall

weighted average across every active pilot rider, pre → post — the headline trend

Orders per hour

Cancelled-after-assignment %

Delivery distance (km)

Notification burst %

Combined summary

Loading…
PeriodLogin hrsAssignedDeliveredOPHMkt OPH Cancel %Mkt Cancel %KmMkt KmBurst %Mkt Burst %
Loading…

Rider level

pick a rider for their individual day-by-day and pre/post numbers
Zone / activated
—
 
Post OPH vs marketplace
—
 
Post cancel % vs marketplace
—
 
OPH change, pre→post
—
 

Day-by-day

rider vs marketplace (trimmed 10–90%ile average), all available data since 7 days before activation

Orders per hour

Cancelled-after-assignment %

Delivery distance (km)

Notification burst %

Overall

7-day pre vs post window vs marketplace

OPH & cancellation %

Delivery distance & burst %

Day-level detail

live from Supabase — refreshes automatically every ~20 min
DatePhaseLogin hrsAssignedDeliveredOPHMkt OPH CancelledCancel %Mkt Cancel %KmMkt KmAccountPingsBurst %Mkt Burst %
Select a rider…
Pre/Post = 7 calendar days (IST) around each rider's zone activation date. Marketplace = trimmed average of all active riders that day (values between the 10th and 90th percentile). Delivery km = pickup→drop route length.