Build a full-funnel dashboard

The first job is getting every team to use the same meaning for each stage, because a dashboard is only as trustworthy as its definitions. "Signup" can mean someone who submitted a form, confirmed an email address, or created a workspace. "Customer" can mean someone who started a trial, paid once, or holds an active subscription today. If marketing and finance count differently, the dashboard becomes one more number to argue about.

Kite proposes definitions based on what your tools actually record. Say your app keeps users in a Supabase table and your workspaces in another. Kite might notice that people who create their first project within a day of signing up tend to stay, and propose that moment as your activation stage. It writes each definition in plain language, names the tool that counts it, and states which date a person is counted on, such as the day they signed up or the day they first paid.

Your team reviews the list and changes anything that doesn't match how you run the business. Kite saves the agreed definitions in your team's knowledge base, so every later chart, report, and question uses the same meaning of "activated" or "customer."

Each stage of the funnel is counted by the tool your team already trusts for that stage. Kite reads that tool directly through its own connection, so you don't need a data warehouse or an export pipeline first.

Here is where each stage usually comes from:

• Visits and traffic sources come from Google Analytics 4 or PostHog web analytics. Kite reads sessions and users by channel, source, campaign, and landing page. If Kite hosts your website, it uses its own built-in analytics instead.
• Signups come from your product analytics or your product database. Kite can count a signup event in PostHog, or write its own query against the users table in Supabase.
• Activation comes from the event or table row that matches your agreed definition, such as a first project created or a first teammate invited.
• Leads and opportunities come from HubSpot. Kite reads contacts and their properties, plus deals and the stages in your pipelines.
• Paying customers and revenue come from Stripe. Kite reads customers, subscriptions and their status, trials, and payments, and reports revenue separately for each currency you sell in.

When a stage could come from two places, Kite names the one it chose and why. Stripe is usually the record for revenue even if your CRM also tracks deal amounts, because Stripe shows what customers actually paid.

A funnel can be measured in two ways, and Kite tells you which one each part of your dashboard uses. The first way counts each stage over the same period, such as visits, signups, and new customers in October. The second way follows one group of people through every stage, such as everyone who signed up in October, to see how many of them went on to pay.

Following the same people is more useful, and it depends on your tools sharing an identifier. Stripe usually stores each customer's email address, and so do HubSpot and your product database, so Kite can match a signup to the Stripe customer who paid. When your app or CRM also records where each person came from, such as a HubSpot contact's original source or a signup source column in Supabase, Kite can carry that channel all the way to revenue.

That is where the dashboard changes decisions. A LinkedIn campaign might bring in twice as many signups as your webinars, while webinar signups become paying customers at three times the rate. A count of signups alone would have pointed you at the wrong channel.

When two tools share no identifier, Kite compares their totals over the same period and labels that part of the dashboard as a period comparison. It also tells you which field to start saving, so the next month's numbers can follow people end to end.

Related How-to pages

• How to see which signups become paying customers with Stripe: Match each signup to its Stripe customer to get your real signup-to-paid rate, broken down by plan and by month.
• How to see which campaigns and landing pages lead to Stripe customers with Google Analytics: Join the campaign and landing page behind each signup to the customers who paid, so the revenue stage of your dashboard can be split by channel.

Kite builds the dashboard as live charts, tables, and single-number tiles that fetch current figures from your connected tools each time someone opens them. The dashboard shows today's numbers, not the numbers from the day Kite built it, and nobody has to paste anything in.

A typical full-funnel dashboard includes:

• a funnel chart with the count at each stage for the period you choose
• the conversion rate between each pair of stages, compared with the previous period
• the same funnel broken down by channel or campaign, so you can see which sources produce customers and not just visits
• the time it takes people to move between key stages, such as from signup to first payment
• revenue from new customers, by plan

Kite can combine numbers from several tools inside one chart. The conversion rate from signup to paid, for example, takes its signups from PostHog or Supabase and its customers from Stripe, and Kite calculates the rate each time the chart loads. Every chart also carries the figures Kite measured when it built it, so the chart still shows useful numbers if a connection lapses.

The charts appear in your conversation with Kite in the web app, and in Slack they arrive as native Slack charts and tables. They can also be pinned to the dashboard for the marketing goal they belong to, where they keep refreshing. When leadership wants a page they can open from a link, Kite can publish the dashboard at a stable web address that only people at your company can view, and update it on a schedule.

A dashboard only helps if someone reads it, and Kite reads yours every time it changes. It compares each stage with the previous period, checks whether a change is real or a tracking problem, and explains what moved in plain language.

You can agree on a regular summary, such as every Monday morning in your team's Slack channel or by email. The summary names the stage that changed most, the likely cause, and what Kite proposes to do about it. Kite can also keep a standing watch on a number in PostHog, Google Analytics, HubSpot, or Stripe and tell your team when it moves past a threshold you set, such as daily signups falling well below last week's average.

The point of the dashboard is the work it leads to. If visits are steady but fewer people sign up, Kite looks at the pages those visitors land on and proposes changes to test. If signups are healthy but few reach activation, it looks at onboarding and the emails new users receive. If trials convert but customers leave after the first month, it checks which channels those customers came from. Kite uses the same agreed definitions to measure whether the change worked.

Related How-to pages

• How to see which product behaviors lead to paid customers with PostHog, Stripe: Compare what paying customers did during their trial with what everyone else did, which is how you find the activation moment worth putting on your dashboard and improving.