Overview
Total Leads
—
Leads over time
Daily lead count (non-bot)
Leads by hour of day
Local time
Leads by day of week
Local time
UTM breakdown
| Value | Leads | Share | Meta OK | |||
|---|---|---|---|---|---|---|
| Loading… | ||||||
Recent leads
Click a row to inspect the exact payload sent to Meta / GA4 / Google Ads and the response
| When | Campaign | Adset | Ad | Device | Meta | GA4 |
|---|---|---|---|---|---|---|
| Loading… | ||||||
/
1
Recent bots
Events flagged as bot/fraud and excluded from leads & metrics. Click a row to inspect why.
| When | Reason | Campaign | Adset | Ad |
|---|---|---|---|---|
| Loading… | ||||
/
1
Tracking health
First-party capture vs pixel. Shows how many lead events you would have lost without server-side tracking.
Real events
—
Duplicates removed
—
ITP recovered
—
Adblock recovered
—
Bots filtered
—
fbp source breakdown
On-page behavior
Paid
All
Organic
Time on page
Active time only: the clock pauses while the tab is in the background.
| Band | Visits | Share |
|---|
Scroll depth
Cumulative: "reached 75%" includes everyone who went deeper.
| Reached | Visits | Share |
|---|
How far down the page
Deepest section that entered the viewport. The row for the plans is the one to
watch: leaving before it and leaving with the price on screen are two different
problems.
| Section | Visits | Share |
|---|
Reading level vs. WhatsApp lead
How much of the page the people who asked for a conversation had read.
| Group | Visits | Median time | Median scroll | Reached plans |
|---|
Reading level vs. checkout click
Same cut against the checkout clicks. A visitor can appear on the engaged side
of both tables; these are two readings, not a funnel split.
| Group | Visits | Median time | Median scroll | Reached plans |
|---|
By device
Read from the user-agent of the visit, the same coarse split the leads table uses.
| Device | Visits | Median time | Median scroll | Reached plans |
|---|