# Performance West — TODO / Backlog

## Analytics / Umami
- [x] **Fix Umami Goals and Funnels "Something went wrong"** — RESOLVED 2026-06-13.
      Root cause: the saved Goal and Funnel reports were created in an older umami
      version and stored `parameters` in a pre-v3.1.0 shape. umami 3.1.0's
      funnelReportSchema / goalReportSchema reject the old shape (HTTP 400 ->
      client shows "Something went wrong").
        - Funnel old: {urls:[...], window, dateRange:{startDate,endDate}}
          v3.1.0 needs: {startDate, endDate, window, steps:[{type:'path',value,filters:[]}]}
        - Goal old: {dateRange:{...}} (no type/value)
          v3.1.0 needs: {startDate, endDate, type, value}
      Fix: migrated the two saved reports in the umami DB to the v3.1.0 schema
      (urls->steps, lifted dateRange to top-level dates, set goal type=url/value).
      Verified: the funnel route now returns 401 (auth-gated, schema valid) instead
      of 400; underlying data exists (3,195 -> 86 on the compliance funnel paths).
      NOTE: running v3.1.0 = latest; the "Failed to find Server Action ... older/
      newer deployment" log lines are unrelated stale-browser-cache noise.

## Analytics / Umami — Goals & Funnels coverage (2026-06-13)
- [x] **Added Goals + Funnels for DOT/Trucking, CRTC, and Healthcare/NPI** (previously
      only FCC was tracked). Created in the umami DB with the v3.1.0 schema:
        Funnels: DOT/Trucking (/tools/dot-compliance-check -> /order/dot-compliance),
                 CRTC/Canada (/services/telecom/canada-crtc -> /order/canada-crtc),
                 Healthcare/NPI (/tools/npi-compliance-check -> /order/npi-revalidation).
        Goals:   DOT (/order/dot-compliance), CRTC (/order/canada-crtc),
                 Healthcare (/order/oig-sam-screening).
      Paths chosen from real 45-day traffic (CRTC 701 + 285 order, DOT 616 + 320 order).
      All pass v3.1.0 schema validation. Tune the exact goal/funnel paths in the UI
      as needed.
