Brainforge Knowledge

phoenix_posthog_dashboard_organization

3 min read

Phoenix / PostHog — dashboard organization (one-pager)

Client: Default · Product: Phoenix · Tool: PostHog
Purpose: Map existing insights (Nandika) into four dashboard categories and list gaps to build.
Sources: knowledge/clients/unassigned/transcripts/2026-03-23_phoenix_product_analytics_dashboard_revi_0c8c4d9d.md, knowledge/clients/default/meeting-notes/2026-03-23_weekly-kick-off-update.md, related Default transcripts on PostHog and cohorting.

1. User Activation — activation metrics, time to value, activation funnels

Include

  • Pixel setup funnel (add domain → copy/continue → test → complete); align instrumentation so post-success dismiss (e.g. cancel after “now set up”) does not count as drop-off.
  • Integration connection funnel (fix Google / Google Meet / Calendar labeling before trusting splits).
  • Custom field creation funnel.
  • Funnel creation insight (low volume acceptable for v1).
  • Dialogue cancellation drop-off (by surface: e.g. force field, cube, pixel, waterfall) — pair with specific funnels as a cross-flow “bail stage” view; supports activation rescue (e.g. CRM onboarding).

Build

  • Time to value: signup → first calendar connected → first queue created.
  • Invite funnel: invite sent → accepted → first meaningful action.

2. User Retention — retention cohorts, retention curves, retention by segment

Include (limited today)

  • Login / logout / calendar connection
  • Signup / return at n-day, return unbounded

Build

  • Cohort retention (user or org), retention curves, retention by segment.

3. User Engagement — engagement metrics, feature usage, session analytics

Include

  • Tables — all event activity: consolidate; hide low-signal actions (sidebar/column toggle, filtering); keep meaningful actions (sync changes, approve changes, create/update view). Template for “is this part of the product getting used” (extend to other features, e.g. routing).
  • Most popular waterfall providers.
  • Field mapping by source (form vs pixel vs enrichment).
  • Team management (invites, role changes) — admin / expansion signals.
  • Org switching frequency (niche; partnerships motion).
  • Configuration-object / core data model activity — prune redundant events over time.

Hide from main dashboards (keep in project if useful)

  • Table submenu “four options” usage.
  • Raw field mapping changes (confusing).
  • Noisy view CRUD chart — replace with consolidated tables view.

Build

  • DAU/WAU/MAU or weekly active orgs; sessions per user/org; session length; optional stickiness (e.g. WAU/MAU).

4. Product Journey — user path and behavior flows

Include

  • Navigation from dock → implement as PostHog User Paths (sequential flows between areas).
  • Dialogue cancellation drop-off (linked or duplicated) for journey debugging alongside paths.

Build

  • User Paths from login, post-activation events, and key modules; optional path/sankey views for enrichment, waterfall, integration flows.

Cross-cutting

  • Data quality: integration + calendar charts — resolve Google vs Google Meet / Calendar duplication.
  • Rollup story: feature engagement dashboards → admin behaviors → higher-level engagement and commercial metrics (separate executive/Omni workstreams).

Last updated: 2026-03-26

Graph View