Analytics — The Judge Tool

Development Velocity

Items completed per session, derived from git history and PR merge data.

Total Items

5.2

Avg / Session

Peak (Mar 8)

-28%

Growth (last 3 vs first 3)

Mar 6

Scaffolding

—

Mar 8

Full app build

PR #1

Mar 9 AM

Judge flow + security

PR #2, PR #3

Mar 9 mid

Box distribution

PR #4

Mar 9 PM

Organizer UX

PR #5

Mar 10

A11y + security + tests

PR #6

Mar 11

Docs + E2E + refactor

PR #7, PR #8

Mar 13

Tech page v1

PR #9

Mar 16

Tech page overhaul

PR #10

Average: 5.2 items/session · Peak: 12 items (Session 2) · 9 sessions total

Product Metrics

What we track and what we plan to track. 2 active, 4 planned.

Page Views

Tracking

Track which pages judges, captains, and organizers visit most frequently.

Google Analytics 4 wired via NEXT_PUBLIC_GA_MEASUREMENT_ID. SPA-aware pageview tracker fires config events on route change. Priority pages: /judge, /captain, /organizer/competition.

User Identity

Planned

Associate analytics events with roles (judge, captain, organizer) without PII.

Use role + anonymized session ID. Never log CBJ numbers or names to analytics.

Feature Adoption

Planned

Measure which features are actually used during live competitions.

Key features: comment cards (toggle rate), correction requests (frequency), score audit (organizer usage)

Engagement Depth

Planned

Track session duration and actions per session by role.

Judges should have short, focused sessions. Organizers need sustained attention. Captain sessions are event-driven.

Performance Metrics

Tracking

Core Web Vitals (LCP, FID, CLS) and API response times.

Health endpoint measures DB latency (target <500ms). Vercel Analytics provides CWV. Server actions need timing instrumentation.

Click Tracking

Planned

Track key interaction patterns: score picker usage, navigation flows, error states.

Priority: score picker (which scores are most common), correction request flow (abandon rate), category advancement (time between)

Key Questions

Product questions we need to answer, how to measure them, and where the data lives.

Product Questions6 questions

How long does it take a judge to complete one box?

high

Measure time from ScoreCard creation (appearance phase) to final submission. Target: 2-4 minutes per box. Break down by: appearance-only phase vs taste/texture phase.

Data source:ScoreCard.appearanceSubmittedAt → ScoreCard.submittedAt timestamps

What percentage of scores require correction?

high

Count CorrectionRequests / total ScoreCards per competition. Healthy rate is <5%. Higher suggests UI confusion or unclear scoring criteria. Track by category (Brisket historically hardest).

Data source:CorrectionRequest count vs ScoreCard count, grouped by CategoryRound

Are comment cards useful or friction?

medium

Compare competition outcomes with commentCardsEnabled on vs off. Measure: judge session duration, comment card completion rate, organizer toggle frequency. If >30% judges skip optional fields, simplify the form.

Data source:CommentCard completeness rate, Competition.commentCardsEnabled toggle history

How many judges struggle with the setup flow?

high

Track progression through the 4 setup phases (not-registered → awaiting-table → pick-seat → ready). Measure: time in each phase, drop-off between phases, support requests. Target: <3 minutes from login to ready.

Data source:Phase transition timestamps (localStorage events + CompetitionJudge.hasStartedJudging)

Is the organizer dashboard efficient?

medium

Measure clicks-to-complete for key organizer tasks: advancing a category, reviewing box distribution, checking results. Compare time-on-page between the old single-page layout and the new tabbed structure.

Data source:Page view sequences, time-on-page for /organizer/* routes, category advancement timestamps

What's the peak concurrent user count?

low

During active judging, all 24 judges + 4 captains + 1 organizer are concurrent (29 users). Monitor: API response times under load, DB connection pool usage, any 500 errors during scoring rounds.

Data source:Health endpoint polling, Vercel function logs, Supabase connection metrics

Analytics Platform

Google Analytics 4 — Active

Pageviews and sessions tracked on both the app (app.thejudgetool.com) and the marketing site (www.thejudgetool.com). App uses a Suspense-wrappedPageviewTracker so client-side navigations fireconfig events. No PII — CBJ numbers and names never leave the server.

TrackingPageviews · Sessions · Traffic sources

Open GA4

Complementary Platforms (not yet added)

PostHog

Event funnels, session replay, feature flags. Adds what GA4 doesn't cover.

Vercel Analytics

Core Web Vitals — zero-config add-on if we want CWV tracking.

Mixpanel

Alternative to PostHog — stronger funnel analysis, generous free tier.