Build it with AI
Build a dashboard around the moments where visitors become leads and customers.
Create a conversion view across traffic, landing pages, forms, qualified leads, meetings, and revenue.
Introduction
What a conversion dashboard has to hold.
Most teams end up with a conversion dashboard the same way: analytics showing sessions and form fills, and a CRM showing deals, with nothing joining them. Measuring each step separately is fine while one person owns the whole path. It fails when the steps have different owners, because each can show their step is healthy and the compound number still falls.
The funnel is measured in two halves that never meet, so the biggest leak is the one between them. There is no cohort that follows the same people across every step, no visibility of elapsed time between steps, and no way to tell a drop caused by fewer arrivals from one caused by worse conversion.
What follows covers building a conversion dashboard: the records it holds (sessions, landing pages, form submissions, qualification outcomes, meetings, and revenue), the systems it reads (GA4 and HubSpot), and what it does not fix.
The problem
Every step is measured and the leak is still invisible.
Analytics tools measure sessions and lose the person at login or at the CRM boundary. CRM reports start at the lead and cannot see the four page views that preceded it. The funnel breaks at exactly the seam between them.
The records are sessions, landing pages, form submissions, qualification outcomes, meetings, and revenue, and the authoritative copy of most of them already lives in GA4 or HubSpot. The landing page reports a 12% conversion, the CRM reports 80 leads, and multiplying the step rates gives a number that does not match either.
The cost is not the inconvenience: pages are optimised for form fills that never become anything.
You're likely here because
- Each step looks healthy and the end-to-end number is falling
- The funnel is measured in two halves that never meet, so the biggest leak is the one between them.
- When it is wrong, pages are optimised for form fills that never become anything
What gets built
Launch builds it, Grow operates it.
Built in Launch
- • Funnel visualization
- • Page performance
- • Conversion cohorts
Operated through Grow
- • Lead qualification
- • Scheduling
- • Attribution
Systems it reads
- • GA4
- • HubSpot
- • Google Calendar
The record model
What a funnel step has to record.
- Entry cohort
- The period a person entered, not the period a step was measured in. Step rates measured over periods are computed on different populations and will not multiply out.
- Person identity across the boundary
- Set at identification and back-applied to the earlier anonymous session. Everything end to end depends on this and it fails for cross-device journeys.
- Join rate
- The share of journeys that survived identification. It is the honest bound on every figure downstream and belongs on the chart rather than in a footnote.
- Step timestamp
- Each step, so elapsed time between them can be a distribution rather than an average. Most recoverable leaks are delays, and averages hide them.
- Step owner
- Because a leak attributed to a step nobody is accountable for is information without a consequence.
- Entry source
- So a fall in end-to-end conversion can be distinguished from a change in the mix of who arrived, which is more common than a genuine conversion change.
- Consent state
- Since consent-rejected journeys break the identity chain, and their share needs to be visible rather than silently excluded.
How it runs
From step metrics to a continuous path.
Step 01
Describe what a conversion dashboard has to do
Define the funnel as one path a single person travels, not as a sequence of independently measured steps. That distinction is what makes a conversion dashboard different from a set of charts.
Step 02
Connect the systems of record
Analytics supplies the pre-identification steps, the CRM supplies everything after, and the calendar supplies whether the meeting happened. The join across the identification boundary is the hard part and the valuable part.
Step 03
Build the operating surface
A cohort-based funnel with conversion and elapsed time at each step, drill-through to the individuals at each stage, and the unjoinable share shown explicitly.
Step 04
Start narrow
The single step where the largest absolute number of people are lost, instrumented as a cohort with elapsed time. One step understood beats six steps counted.
Step 05
Route the exceptions
A step whose conversion moves outside its normal band surfaces with the cohort attached, so investigation starts from the affected people rather than from a percentage.
Step 06
Measure conversion from submission to qualified conversation, by landing page
Track end-to-end conversion by entry cohort, with volume alongside. Step rates without cohorts cannot distinguish a conversion problem from a mix change, and mix changes are more common.
Implementation path
Instrumenting a funnel you can actually act on.
- 01
Define the funnel steps as events a single person triggers, and check that the identity linking them survives the login or form boundary. If it does not, that is the first build.
- 02
Baseline end-to-end conversion by weekly cohort for the last quarter, not step rates. The cohort view frequently shows the fall started earlier than anyone thought.
- 03
Instrument elapsed time between steps as well as conversion. Most funnel leaks that matter are delays rather than refusals, and delay is invisible in a conversion rate.
- 04
Publish the unjoinable share with every figure, so nobody builds a quarter of decisions on a funnel whose join rate is 70%.
- 05
Build the narrowest useful version first: the join from form submission to qualified opportunity, for one campaign.
- 06
Defining the steps as events a single person triggers and checking that identity survives the login or form boundary is the first week, and if it does not survive, that is the build. Cohorting the last quarter retrospectively is quick once identity works and usually reveals the fall started earlier than anyone thought. Elapsed-time instrumentation follows.
- 07
After cohorted conversion and elapsed time are live, add segment-level funnels for the two or three entry sources that behave differently. Session recordings or interviews come next — the dashboard produces the question and cannot answer why.
Controls
Controls that matter.
Control 01
Cohort-based reporting rather than period-over-period step rates, since mix changes otherwise present as conversion changes
Control 02
Person-level drill-through scoped by role, because a funnel joined across the identification boundary is more identifying than either source
Control 03
The join rate published alongside every conversion figure, as the honest bound on what the number can support
Examples
Three leaks that become locatable.
The healthy steps and the falling total
A cohort following the same people through every step exposes that the mix of arrivals changed, which no combination of independently measured step rates can show.
The four-day gap
Elapsed time between form submission and first contact, measured as a distribution rather than an average, locates a leak that conversion rates alone present as a lead quality problem.
The drop that started three weeks ago
Weekly entry cohorts move the detection point earlier than a month-over-month comparison, which is usually the difference between fixing a regression and explaining a quarter.
How it goes wrong
Three ways funnel analysis misleads.
Each step is measured over the month and the multiplied rates do not match the end-to-end number.
Cohort the funnel. Period-measured steps count different people at each stage, which makes the arithmetic wrong in a way that looks like a data quality issue and is actually a modelling one.
Twelve steps are instrumented and each week produces a precise attribution of a loss to a step nobody owns.
Fewer steps, each with an owner who can act. Resolution without accountability generates reports rather than changes, and the reports get longer every week.
Weekly step movement is reacted to at a volume where most of it is noise.
Below a few hundred completions per period, read direction over quarters. Reacting to weekly movement at low volume produces changes whose effects cannot be distinguished from the noise that prompted them.
Limitations and considerations
What conversion data cannot explain.
- Conversion data locates where people leave and is silent about why. The dashboard produces the question; interviews, session recordings, and sales conversations produce the answer.
- Cross-device and consent-rejected journeys break the identity chain for a meaningful share of users. That share is the bound on every end-to-end figure and belongs on the chart.
- Small volumes make step-level movement mostly noise. Below a few hundred completions per period, read direction over quarters and resist reacting to weekly movement.
- If one person owns the whole path end to end, they already know where people leave. If identity cannot survive the login boundary for policy or technical reasons, build the pre- and post-identification halves honestly as two funnels rather than one joined one that is quietly 60% guesswork.
- Connector coverage varies: GA4, HubSpot, Google Calendar are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
FAQ
Build a conversion dashboard with AI: common questions.
Why do our funnel numbers never multiply out?
Because each step is measured over a period rather than over a cohort, so the people counted at step three are not the people counted at step one. Cohorting fixes the arithmetic and usually changes the conclusion.
How do we track people across the login boundary?
Through an identity that is set at identification and back-applied to the earlier anonymous session. It works for the majority of journeys and fails for cross-device ones, which is why the join rate has to be published rather than assumed.
What is the most common leak?
Elapsed time between a form submission and a human response. It rarely appears in a conversion dashboard because it is a delay rather than a refusal, and it is usually the largest single recoverable loss on the path.
How many steps should the funnel have?
Few enough that each has a clear owner who can act on it. A twelve-step funnel produces precise attribution of a loss to a step nobody is accountable for, which is information without a consequence.
What should the first version contain?
The join from form submission to qualified opportunity, for one campaign. Everything else waits until that one is genuinely used.
How will we know whether it worked?
Measure conversion from submission to qualified conversation, by landing page against the baseline taken before anything changed.
Start with ARIA
Ask ARIA to build it.
Describe the website, application, workflow, or operating surface you need. ARIA plans, connects, builds, tests, and keeps refining it — inside the permissions you set.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Build a conversion dashboard around the process you actually run.
Cohort the funnel, measure elapsed time as well as conversion, and publish the join rate beside every figure.