Analytics · Data-quality dashboard

A dedicated panel measuring how complete new registrations are: the share of new registrants with and without an email, phone, name, age, postal code and ID, plus notification opt-in rates and the registration history by channel.

AreaAnalytics
Routesindex · analytics.dashboards.show
Centre modulesanalytics · crm
Staff levelsas per the dashboard’s role scope
Modelsstats · user
UI labeldashboard.data-quality
Coverage4 use cases · 1 happy · 2 failure

How it works

Deliberately symmetric — for each attribute it reports both the ‘with’ and the ‘without’ figure (e.g. new-registers-with-phone and from-new-registers-without-phone), which makes a gap impossible to overlook. It also combines attribute and consent (new-registers-with-email-and-notifications, new-registers-with-app-and-notifications, new-registers-with-phone-and-notifications), i.e. it measures contactable registrations rather than merely complete ones. changeFilters re-scopes the whole panel and the filter set comes from enums/dashboard-filters.

Use cases

Why someone opens this (4)

  • Setting and tracking a data-quality target for front-desk staff.
  • Proving to marketing how many of the new registrations are actually contactable.
  • Comparing registration quality across channels to find the weak one.
  • Deciding whether to make a field mandatory via center.userRequired.

Path map

flowchart LR
    F(["Data-quality dashboard"]):::feat
    F --> H1["Monthly quality review"]:::ok
    F -.-> X1["Stats request fails"]:::bad
    F -.-> X2["No new registrations in the period"]:::bad
    classDef feat fill:#8a6b10,stroke:#8a6b10,color:#ffffff,font-weight:bold
    classDef ok fill:#e3f1ea,stroke:#0d6b42,color:#0d4a2e
    classDef bad fill:#f7e6e2,stroke:#9a2d1c,color:#6e1f13

Happy paths

Monthly quality review

  1. User opens the data-quality dashboard and sets the period.
  2. Each attribute shows its with/without pair and the contactable combinations.
  3. The registration history by channel identifies where quality drops.
  4. The user tightens center.userRequired for the offending field.

Failure paths

QA checklist

Tick these off while regression-testing this feature. The boxes are plain Markdown, so progress is visible in git diffs.

  • ✅ Monthly quality review
  • ⛔ Stats request fails
  • ⛔ No new registrations in the period

Implementation


Generated from doc/feature-inventory.json · id analytics-data-quality · commit 276788ca6