Blog · Board and management reporting
A user funnel measures how a defined group progresses through recorded website or product stages. Learn how to choose the counting unit, compare mature cohorts, and reconcile conversion and drop-off from an event-summary export.
A user funnel measures how a defined cohort progresses through recorded website or product stages, using the same identifiers and observation window throughout. It tells you which transition needs investigation, provided the counts represent ordered actions by the same users rather than unrelated activity totals.
Start with a business question: do new purchasing users reach the action that makes an account useful? A website funnel might follow account creation, verification, a catalog search, and a saved purchasing list. Those are recorded user actions, not sales representatives moving opportunities through a CRM.
Choose one stable, de-identified user identifier. An account shared by several purchasing employees is a different unit from an individual user. If the business question concerns account adoption, build an account funnel rather than adding user counts and calling them companies.
Also distinguish users from events. One employee might search the catalog repeatedly. That activity belongs to one user at the search stage, regardless of how many searches occurred. Google's documentation distinguishes total, new, active, and returning users; those labels refer to different measures and should not be treated as interchangeable export columns (Google's user metrics guide).
For each stage, record the qualifying action, the identifier, and the deadline. State whether a user must complete every earlier stage in order. In a closed funnel, later activity does not qualify someone who never met the starting condition.
Google's funnel exploration documentation distinguishes open entry from closed entry and explains how specified event sequence affects inclusion. You need the equivalent definitions in your supplied export even when the analysis is performed elsewhere.
For the example below, a fictional US industrial supplier sets these rules:
| Stage | Qualifying record | Counting rule |
|---|---|---|
| Account created | First account creation timestamp | One distinct user in the signup week |
| Verified | Verification timestamp | After creation, within seven elapsed days of signup |
| Searched | First qualifying catalog search timestamp | After verification, within the same deadline |
| Saved list | First saved purchasing-list timestamp | After the qualifying search, within the same deadline |
Treat intervening actions as permitted. A person can browse help between verification and searching without leaving this funnel. A search recorded before verification does not qualify unless a later search meets the sequence rule.
The product funnel analysis guide applies this framework specifically to signup-to-activation diagnosis. Commercial handoffs between marketing, sales, and customer success belong in revenue operations metrics.
Bring an event-summary CSV containing the de-identified user ID, signup timestamp, cohort week, qualifying stage timestamps, and export cutoff. The person preparing the file must preserve missing timestamps as missing. A blank cannot prove that an action never happened outside the recorded system.
Compare users who signed up in the weeks beginning September 7 and September 14, 2026. Extract the file on September 28, after everyone in both weekly cohorts has had the full seven-day observation window. Include only actions completed within each user's individual deadline, even if later actions are already visible in the file.
The resulting counts are:
| Signup week beginning | Created | Verified | Searched | Saved list |
|---|---|---|---|---|
| September 7, 2026 | 240 | 180 | 120 | 72 |
| September 14, 2026 | 300 | 210 | 126 | 63 |
| Total | 540 | 390 | 246 | 135 |
Stage conversion = Users reaching the next stage / Users reaching the preceding stage
Overall conversion = Users completing the final stage / Users entering the first stage
Apply those divisions to the counts, retaining unrounded values for calculations and displaying percentages to one decimal place:
| Cohort | Created to verified | Verified to searched | Searched to saved | Created to saved |
|---|---|---|---|---|
| September 7 | 180 / 240 = 75.0% | 120 / 180 = 66.7% | 72 / 120 = 60.0% | 72 / 240 = 30.0% |
| September 14 | 210 / 300 = 70.0% | 126 / 210 = 60.0% | 63 / 126 = 50.0% | 63 / 300 = 21.0% |
| Combined | 390 / 540 = 72.2% | 246 / 390 = 63.1% | 135 / 246 = 54.9% | 135 / 540 = 25.0% |
Combined conversion divides combined counts. Averaging the displayed cohort percentages would give each cohort equal weight despite their different sizes.
Subtract adjacent counts to get users who had not reached the next qualifying stage by their deadline:
| Cohort | Not verified | Verified, no search | Searched, no saved list | Saved list | Reconciled entrants |
|---|---|---|---|---|---|
| September 7 | 60 | 60 | 48 | 72 | 240 |
| September 14 | 90 | 84 | 63 | 63 | 300 |
| Combined | 150 | 144 | 111 | 135 | 540 |
The check is 150 + 144 + 111 + 135 = 540. Each user occupies exactly one terminal bucket at the deadline. Also test the underlying records: every saved-list user must appear among qualifying searchers, and every searcher among verified users. Matching aggregate totals alone cannot prove those memberships.
If the export contains only summary counts, ask its owner to confirm the sequence and deduplication rules. An analyst cannot reconstruct ordered individual journeys from four independent event totals. Preserve the definitions alongside the file; analytics data portability explains why exported figures need their meaning attached.
The later cohort's overall conversion fell from 30.0% to 21.0%, a decline of 9.0 percentage points. Every transition weakened, so there is no basis for blaming only the final action. Review verification delivery with the account operations owner, catalog access with the website owner, and list-saving feedback with the product owner.
The analyst owns count reconciliation. The product or website owner owns the stage definition and investigation. Customer support supplies evidence about the reasons people stopped. Compare acquisition source and account type before interpreting the cohort difference as an effect of a recent change.
Covirage is not affiliated with Google.
Upload a prepared event-summary file or Google Sheet with stage definitions and a consistent observation window. Covirage maps the columns, and its tools compute and check the cohort counts, conversion rates, and reconciliations; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See sales insights for the business questions those file-based comparisons support.
Count distinct users when the question concerns how people progress. Repeated actions by the same user should not create additional people in a stage. Event counts answer an activity question and can exceed the number entering the funnel. Label the counting unit explicitly.
An open funnel allows entry at later stages. A closed funnel requires entry at the first stage. Choose the rule before comparing periods, because later entrants can change stage counts without representing progression by the original starting cohort.
It shows where recorded progression stopped under your rules. It does not establish the reason. Investigate the affected stage with support feedback, permission checks, and a review of event completeness before deciding that the interface or offer caused the difference.