If you have ever sat on a marketing call where someone said "I think the form is broken" and nobody could prove it either way, this product is for you.
CloseTrace is a multi-tenant session capture, replay, and lead-recovery platform. One snippet, one dashboard, one source of truth for the visitor journeys your sites generate. Our tagline says it plainly: trace visitor journeys, close more leads.
Why we built it
Most marketing teams we worked with had four or five tools doing the work of one:
- a tracker shipping events to one warehouse
- a replay tool with its own login
- a heatmap tool that expired data after 90 days
- a CRM that only knew about people who clicked submit
- a homemade webhook that fell over every other Friday
None of them agreed on what a "session" was, and none of them could answer the simplest question: "why did this visitor leave?"
We built CloseTrace to give you one honest answer to that question, on every site you run, without rebuilding your stack.
What you get on day one
Drop in a single <script async> snippet and you immediately get:
- Session capture — pageviews, clicks, scrolls, and form interaction in one timeline
- Session replay — watch the visit, frame by frame, powered by rrweb
- Lead recovery — visitors who started typing in a form and never submitted
- Heatmaps — click and scroll density, normalized by viewport
- Funnels — drop a 3-step funnel definition in, watch it backfill from real data
No rebuild. No deploy. No new SDK to learn.
The differentiator: lead recovery as a first-class object
Most session replay tools track form interactions as events. CloseTrace treats half-typed forms as durable lead-draft objects — name, email, phone, message, the field where they bailed, the time they spent on each input, and a one-click jump back into the source replay. Your best leads never click submit. We help your team act before the trail goes cold.
What we deliberately did not build
- We are not an ad platform. There are better tools for remarketing pixels and attribution models — we make those tools work better by handing them clean session data.
- We are not a chatbot. We show you who started typing and never finished. What you do with that information is your call.
- We are not a CDP. We give you the session truth and an operational workspace to act on it.
What's next
Over the next few weeks we will be writing about the things we learned building this — the performance contract for the tracker, the multi-tenant schema decisions, why we picked Postgres over a columnar store, and the boring infrastructure that makes it all work.
If any of that sounds interesting, subscribe to the blog or start free.