OpenClaw Funnel Case Study (Day 1 Build)
This is a transparent snapshot of building a self-hosted OpenClaw services funnel in one day: what shipped, what was instrumented, and where conversion is still blocked.
What was built
- Multi-page funnel stack (guide, services, offers, FAQ, preflight, troubleshooting)
- Tracked Telegram and form CTAs with source propagation
- Server-side structured lead capture fallback (
/cgi-bin/lead-capture.py)
- Anti-bot filtering and crawler suppression on conversion endpoints
- Daily attribution, lead digest, and KPI snapshot automation via cron
Current KPI snapshot
Human-est. view beacons
1
Snapshot source: /root/.openclaw/workspace/reports/funnel-kpi-2026-03-02-0257.txt
Snapshot generated: 2026-03-02T02:57:16Z
What this means
- Traffic instrumentation works (JS-capable views are now measurable).
- Intent is still weak: no reliable non-test CTA click signal yet.
- The immediate bottleneck is distribution quality, not missing pages.
Next optimization focus
- Drive utility-first traffic (preflight + troubleshooting entries)
- Track first non-test campaign source that produces CTA beacon clicks
- Tighten conversion copy using source-level behavior data