What Multi-Location PI Firms Get Wrong About Attributing Leads to the Right Office

Here is how most multi-location PI firms find out their attribution is broken: the managing partner asks why the new office costs twice as much per case as headquarters. The marketing director pulls six months of data. The numbers look plausible — until you realize every location tag, every spend allocation, every vendor tie-back is built on assumptions that stopped being valid the moment a second address opened.

Attribution errors at one office are manageable. At two or more, those same errors compound into structural problems that corrupt every performance comparison you run. Here are the five most common mistakes — and what each one costs you in distorted decision-making.

Mistake 1 — Attributing the Lead to Where the Attorney Is, Not Where Intake Happened

This is the most common mistake — and the most insidious, because it seems logical. A lead comes in, gets signed, and is assigned to an attorney at the satellite office. Most CRM setups tag the case to the attorney's location, not the intake location.

The problem: marketing spend is incurred where leads are generated and processed, not where attorneys sit. If your location tag reflects attorney assignment rather than intake origin, your cost per case by location is wrong from the start.

The fix: add an explicit intake location field to every lead record at first contact, separate from the case assignment location. These two fields often match. When they don't, it matters.

Mistake 2 — Booking All Vendor Spend to the Headquarters Location

When the marketing director sits at headquarters and processes vendor invoices, the path of least resistance is to book all spend to the headquarters cost center. Every accounting system makes this easy. It is also deeply wrong the moment you have more than one office.

Consider a vendor delivering 400 leads per month — 150 to Location 1, 160 to Location 2, 90 to Location 3 — on a $45,000 monthly invoice. That spend should be allocated proportionally. Book it entirely to Location 1 and that office's cost per case looks catastrophically high. Locations 2 and 3 show zero acquisition cost for those leads. Neither reflects reality.

Firms that catch this problem are usually staring at 12 to 24 months of corrupted location-level financials. The correction is painful. Build location-level spend coding into your financial system before the second office opens — not after 18 months of bad data.

Mistake 3 — Using a Shared Phone Number Across Locations Without Call Routing Attribution

Many multi-location PI firms run a single toll-free number in all their advertising and route calls to whoever is available. Operationally convenient. For attribution, a disaster.

If a vendor generates a lead from the Houston market and the call routes to a Dallas intake specialist because Houston was busy, that lead should still be attributed to Houston — that is the market the vendor was serving and the spend was allocated to. But if the only location data in your system is the intake specialist's office, it gets tagged to Dallas.

The solution: market-tagged phone numbers — distinct tracking numbers per market connected to a call attribution system like CallRail, with the market tag passing through to the CRM record. Not complex to implement, but it requires deliberate setup before the problem starts.

Mistake 4 — Treating a Centralized Intake Team as “No Location”

Some multi-location firms centralize intake — all calls go to one team, regardless of which market the lead originated from. The temptation is to tag those leads as “corporate” or leave the location field blank.

This destroys location-level reporting. A lead generated by a Dallas market campaign and processed by a centralized intake team should still carry a Dallas market tag. Centralized intake is an operational layer. The market the lead was generated in is the relevant attribution dimension for marketing performance analysis.

Build market attribution into the lead record from the source — the campaign, the tracking number, the vendor contract — not from the intake operational layer.

Mistake 5 — Comparing Location Performance Without Controlling for Vendor Mix

This one is an analysis error more than an attribution error, but it corrupts multi-location decision-making in the same way. A location running on premium exclusive leads will show higher cost per lead and lower cost per signed case than a location running shared aggregator volume. Comparing those two offices on cost per case without flagging the vendor mix difference is comparing apples to tractors.

Document the vendor portfolio composition for each location alongside the performance metrics. When you present a monthly location comparison to the managing partner, vendor mix context is not optional detail — it is what makes the numbers mean something.

The Cost of Getting Attribution Wrong

Attribution errors at the location level compound in ways that are hard to untangle. A marketing director working from six months of corrupted location data has been making vendor budget decisions, coaching intake staff, and recommending market expansions based on numbers that do not reflect reality. Depending on firm size and error severity, those decisions may have cost $50,000 to $150,000 in misallocated spend.

The firms that get multi-location attribution right treat the infrastructure decisions — location tagging, spend allocation methodology, phone number tracking — as non-negotiable requirements before the second office opens. Not cleanup projects after 18 months of bad data.

If your firm already operates multiple locations and you recognize these patterns, start with an attribution audit — not a new reporting tool. Understand what data you actually have and where the gaps are before building on top of a broken foundation.

RevenueScale is built for the attribution complexity of multi-location PI firms. Book a demo to see how the platform handles lead-to-location tagging, market-level spend allocation, and the cross-location reporting that drives better marketing decisions.