Instrument the phone loop
Lead Tracking via API: Capture, Attribute, Route, Measure
A phone lead is a lead your web analytics never sees. Instrumenting the loop takes four stages — capture, attribute, route, measure — and each maps onto a piece of what we run: tracking numbers, routing rules, and call records through the API.
- Four stages, mapped
- CDRs near-real-time
- Keyword-blind, stated
Lead tracking questions
Can the API capture phone leads automatically?
It captures the call data automatically — per-call records for your numbers appear via the CDR area within roughly one to two minutes of each call. Capturing the lead's identity and outcome still happens on your side, in your CRM or workflow.
How are phone leads attributed to campaigns?
By number: each campaign or medium carries a distinct tracking number, so the record of which number was dialled is the attribution. It is campaign-level accuracy — it will not tell you the keyword the caller searched.
Does lead tracking need code from day one?
No — the console reports calls per number with nothing built. The API layer is worth it when you want the call records inside your own stack: dashboards, alerting, CRM joins. Start read-only either way.
Web leads report themselves; phone leads do not. A call that converts a customer leaves no row in your analytics unless the phone loop is instrumented — and instrumenting it is a four-stage job, not a product you buy in one box. This page maps the stages, the pieces of our platform behind each, and the limits that honest planning needs.
Stage 1: capture — a number per lead source
Every lead source that could generate a call carries a distinct tracking number: the website, the campaign, the listing, the print run. Allocation is the whole capture mechanism — the number is the sensor, working network-side with nothing installed. Tracking numbers run from $5 a month per number, searchable on available numbers.
Stage 2: attribute — the number is the tag
When a call arrives, the record of which number was dialled is the attribution: campaign-level, automatic, and honest about its resolution. It answers "which medium produced the lead" completely, and "which keyword" not at all — that higher resolution needs session-level platforms, a different category, per the split in what call tracking software is.
Stage 3: route — the lead reaches a human
Attribution is worthless if the call rings out. Routing rules — overflow, after-hours paths, round-robin — deliver the lead to whoever answers, and the routing discipline that suits lead-handling is in API call routing.
Stage 4: measure — the loop closes in your stack
The CDR area of the API exposes the per-call records — timing, duration, service — within roughly one to two minutes of each call completing. Read them into your stack and join with outcomes: calls per source, conversion per source, cost per phone lead. The starter build is the nightly pull in getting started with the API; the analytics patterns extend it in call analytics through the API.
The limits, stated once
Number-based attribution is campaign-level. The API reads call records — it does not transcribe calls or capture caller identity, which stays with your CRM process. And nothing here places outbound calls or provisions global numbers; the boundary is in telecom API integration. Within those edges, the phone loop becomes as measurable as any form on your website — rates on the pricing page.
The numbers behind the loop
Tracking from $5 a month per number
Per-second call records, console reporting, and an API for the data team.