Analytics
Last 30 days. Funnel first and traffic last, because GA4 will happily show sessions rising while zero calls get booked.
Funnel
Read top to bottom. Everything above the last row exists to produce the last row.
- 4
Touches out
Posts and emails that went out under someone's name.
- 250.0%
Clicks
Only clicks on links minted through /r/<slug> are visible here.
- 125.0%
Replies
Inbound replies and DMs, not clicks.
- 3300.0%
Booked
Calls on the calendar.
- 266.7%
Held
Calls that actually happened.
- 2100.0%
Held with an ICP-fit contact
The north-star metric. Everything above exists to produce this row.
100% of booked calls trace back to a touch.
By angle
Which argument produced held calls, which is what next week's plan should be built from.
| Angle | Out | Held | Held, ICP |
|---|---|---|---|
| the commercial case for narrowing scope | 1 | 1 | 1 |
Search Console opportunity finder
Queries people search and do not click, or that rank just off the first page. Pushing one into the angle bank is what makes this screen produce work rather than decorate one.
No Search Console snapshots yet
Attach a Search Console rail account with the site URL in its external reference, then run a snapshot. Nothing is queried live — the screens read stored rows.
Rail accountsTraffic
Last on the page on purpose. This is a footnote to the funnel, not a headline.
No GA4 snapshots yet
Attach a GA4 rail account with the property id in its external reference, then run a snapshot.
Rail accountsEverything here reads stored snapshots. Nothing re-queries Google on render, which is why the page is fast and why history survives a credential expiring. The health strip shows whether the nightly job is still running.