How does call tracking actually work?
Dynamic number insertion: the tracking script swaps the displayed phone number per visitor session, so when the call arrives, the platform knows which session - and therefore which source, campaign, and page - produced it. Calls forward to the firm's real line; the measurement rides on the swap. Two properties follow immediately: the swap must fire on every template where a number renders (headers, footers, attorney bios, location pages), and the number pool must be large enough for concurrent visitors, or sessions share numbers and attribution quietly randomizes.
What is different about law firms?
The call content. A prospective client's first call describes their legal situation - which makes recording, transcription, and retention decisions matter more than in most industries. The working posture: decide recording policy with the firm's ethics counsel (consent-to-record rules vary by state, and two-party states are unforgiving); scope any recording to intake staff lines rather than attorney lines; set retention deliberately; and treat transcripts as sensitive intake data, not marketing exhaust. A call-tracking vendor is a vendor receiving prospective-client communications - select and contract with it accordingly.
The disposition rule: a call tracking setup that counts calls but not outcomes measures phone noise. Intake must mark each tracked call - not reached, not a case, consultation set, retained - or the attribution rewards whatever makes phones ring, including the wrong cases in the wrong jurisdictions.
What are the recurring setup failures?
| Failure | Symptom | Fix |
|---|---|---|
| Partial swap coverage | Direct and organic calls attributed to "none"; a template renders the static number | Runtime check of every template for swap firing |
| Pool exhaustion | Attribution scrambles during traffic spikes | Pool sized to concurrent sessions; verify at peak |
| Listings mismatch | Tracking numbers pasted into directories and profiles wreck consistency and pollute source data | Static primary number everywhere off-site, except deliberate per-listing tracking lines |
| No consent gating | The swap script and its cookies run before consent where consent is required | Gate like any other tag; verify both states on the wire |
| Numbers recycled hot | Calls from old ads land on another campaign's line | Cooling periods on released numbers |
How should calls join the ROI pipeline?
The call record carries session source; intake carries disposition; the matter record carries the fee. The join is the same one described in the marketing ROI guide - the call is just the noisiest entry point, which is why disposition discipline matters most here. A firm that can produce "retained matters by campaign, including phone-first matters" has finished the assignment; a firm that can produce only "calls by campaign" has counted rings.
Build, buy, or bundle with the agency?
Buy the platform; own the account. Call tracking bundled inside an agency's own account is attribution the firm cannot audit and loses in a breakup. The platform choice matters less than three contract points: the firm owns the numbers and data, recording policy is configurable to the firm's ethics posture, and the data exports cleanly to whatever intake and reporting stack the firm runs.