Analytics
The Zuno Engineer App uses two analytics platforms to track user behaviour and app usage: Firebase Analytics (screen views, button presses, app lifecycle events) and PostHog (job acceptance/decline, availability, product applications).
New product analytics go to PostHog. The Firebase stream is legacy, kept for the historical funnels built on it.
What We Track
These platforms capture events when engineers interact with the app, helping us understand how the app is used and identify areas for improvement.
Screen Views
We track when engineers view key screens in the app:
| Event | Screen |
|---|---|
s_homescreen | Home/job offers |
s_daily | Daily diary view |
s_weekly | Weekly diary view |
User Actions
We track important actions engineers take:
| Event | Action |
|---|---|
job_accepted_success | Engineer accepted a job |
job_accepted_failure | Job acceptance failed |
job_declined_success | Engineer declined a job |
job_declined_failure | Job decline failed |
b_accept | Tapped accept button |
b_invoice_share | Shared an invoice |
b_ETA_shared | Shared ETA with customer |
availability_add_success / availability_remove_success | Updated availability |
product_application_submission_success | Submitted a product application |
App Lifecycle
| Event | Description |
|---|---|
app_in_foreground | App was opened |
app_in_background | App was minimised |
screenshot_detected | Engineer took a screenshot |
Event Context
Events include relevant context such as:
- User ID - Which engineer performed the action
- Job details - Job ID, type, and whether it's a regional offer
- Timestamps - When the action occurred
Accessing PostHog
PostHog dashboard: eu.posthog.com (requires team access)
From the dashboard you can:
- View event trends over time
- Filter events by user or job
- Build funnels to understand user journeys
- Create cohorts for analysis