Dashboards & Analytics · Lead Quality

Lead Quality Tag Distribution View

A distribution view that shows how lead quality tags break down by source and over time, so the team can see whether channels are sending good leads or just volume.

Start a ProjectAll Case Studies
4 to 7 days
build time
4
outcomes
5
stack tools
6
build steps

Built with real HMX dashboard tool paths

Supabase PostgresSQL view (tag distribution)Next.js 16 server componentsMetabase (read-only BI)Vercel hostingSupabase PostgresSQL view (tag distribution)Next.js 16 server componentsMetabase (read-only BI)Vercel hosting

01 // Outcomes

Outcome signals

Tag
distribution overall and per source
Quality mix
shown beside raw channel volume
Trend
of lead quality over time
Flagged
untagged leads kept out of the buckets

Case architecture

Lead Quality Tag Distribution View Architecture

6 nodes
the quality-tag field and
a view returning tag
Supabase Postgres
SQL view
Review Queue
Dashboard Action
  1. 01the quality-tag field and

    A distribution view that shows how lead quality tags break down by source and over time, so the team can see whether channels are sending good lead...

  2. 02a view returning tag

    Build a view returning tag distribution overall, per source, and per time window.

  3. 03Supabase Postgres

    Supabase Postgres contributes the trusted model for Lead Quality Tag Distribution View so metrics are defined before they are visualized.

  4. 04SQL view

    Compute a quality mix per channel so volume and quality sit next to each other.

  5. 05Review Queue

    When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

  6. 06Dashboard Action

    Tag distribution overall and per source; Quality mix shown beside raw channel volume; Trend of lead quality over time; Flagged untagged leads kept...

Problem

The operating gap

Quality tags get applied to leads but never aggregated, so 'is this source sending us good leads or junk' stays a hunch — high-volume channels look great until you realize most of their leads are tagged low quality.

Build

What gets built

A read-only view that aggregates quality-tag distribution overall, by source, and over time, with a quality mix per channel so volume and quality are visible side by side. It reads the existing tag field and turns tag soup into a comparable distribution — and flags untagged leads so the picture is honest.

Build steps

How it ships

Lead Quality Tag Distribution View uses a reporting model and review layer for Dashboards. A distribution view that shows how lead quality tags break down by source and over time, so the team can see whether channels are sending good lead... The architecture connects the quality-tag field and, supabase postgres, sql view, and dashboard action with an explicit control path.

  1. 01Confirm the quality-tag field and its allowed values, and how untagged leads are represented.
  2. 02Build a view returning tag distribution overall, per source, and per time window.
  3. 03Compute a quality mix per channel so volume and quality sit next to each other.
  4. 04Render a distribution view with a per-source quality breakdown and a trend over time.
  5. 05Flag untagged leads explicitly so they are not silently treated as a quality bucket.
  6. 06Document the tag meanings so quality reporting stays consistent.

Stack

Tools and layers

  • Supabase Postgres
  • SQL view (tag distribution)
  • Next.js 16 server components
  • Metabase (read-only BI)
  • Vercel hosting
  • Inputs layer: Confirm the quality-tag field and its allowed values, and how untagged leads are represented.
  • Transform layer: Build a view returning tag distribution overall, per source, and per time window.
  • Metrics layer: Supabase Postgres contributes the trusted model for Lead Quality Tag Distribution View so metrics are defined before they are visualized.
  • Visualization layer: SQL view (tag distribution) handles refresh, review, or reporting delivery while a read-only view that aggregates quality-tag distribution overall, by source, and over time, with a quality mix per channel so volume and quality a...
  • Action layer: Tag distribution overall and per source; Quality mix shown beside raw channel volume; Trend of lead quality over time; Flagged untagged leads kept...

Data flow

  1. 01Confirm the quality-tag field and its allowed values, and how untagged leads are represented.
  2. 02Build a view returning tag distribution overall, per source, and per time window.
  3. 03Compute a quality mix per channel so volume and quality sit next to each other.
  4. 04Render a distribution view with a per-source quality breakdown and a trend over time.
  5. 05Flag untagged leads explicitly so they are not silently treated as a quality bucket.
  6. 06Document the tag meanings so quality reporting stays consistent.

Controls

  • Quality tags get applied to leads but never aggregated, so 'is this source sending us good leads or junk' stays a hunch — high-volume channels look...
  • A read-only view that aggregates quality-tag distribution overall, by source, and over time, with a quality mix per channel so volume and quality a...
  • When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

Research basis