---
title: "Why don’t visitor counts in my Funnel always match visitor counts in the page leaderboard?"
description: "If you’re seeing a mismatch between Funnel step counts and visitor counts in the Pages leaderboard, here’s why."
url: https://help.knotch.com/en/articles/111-why-don-t-visitor-counts-in-my-funnel-always-match-visitor-counts-in-the-page-leaderboard
collection: "Funnels"
updated: 2025-07-21
language: en
---

# Why don’t visitor counts in my Funnel always match visitor counts in the page leaderboard?

If you’re seeing a mismatch between Funnel step counts and visitor counts in the Pages leaderboard, here’s why.

Funnel steps in Knotch One are designed to reflect **sequential behavior**—so a user must complete each step **in order** and **after** the previous one to be counted. This logic can sometimes cause Funnel counts to look **lower** than what you see in the Pages leaderboard.

* * *

### Why is there a difference?

The Funnel engine does **not use overlapping logic** between steps. Specifically, we do **not** use “greater than or equal to” (>=) logic to determine progression.

So if you build a Funnel like this:

-   **Step 1:** All visitors to the site
    
-   **Step 2:** Page A
    

And a user’s very **first** page view is **Page A**, but they **never visit Page A again**—they will be counted in Step 1, but **not** in Step 2.

Why? Because the funnel is looking for a **Page A view that occurred after Step 1**. Since that visit was part of their entry (Step 1), and they never returned to Page A, they don’t qualify for Step 2 in the funnel.

* * *

### What about the Pages leaderboard?

The **Pages leaderboard** doesn’t apply the same sequential logic. It counts **all visitors** who viewed Page A during the timeframe—**regardless of order or sequence**.

This is why the visitor count for Page A in your Funnel **may be lower** than in the Pages section.

* * *

### Key takeaway

Funnels measure **ordered progression**.  
Leaderboards measure **total engagement**.

If you’re analyzing Funnels, ensure each step truly reflects **subsequent behavior** to avoid confusion around counts.
