Multi-Unit Franchise Call Tracking: One Stack Across Locations You Own

If you own several franchise units and your dashboards still argue about which store “got” the call, you don’t have a media problem yet — you have a tracking stack problem.

I’ve sold franchise units myself and I’ve helped a lot of multi-unit operators (typically 2–10 locations) clean up call attribution for local service demand. The pattern is familiar: corporate co-op reports look fine, Google Ads shows “calls,” LSA shows “leads,” and your P&L still can’t say which unit and which channel booked the job.

This playbook is the operator call-tracking layer — shared vs per-location numbers, dynamic number insertion (DNI), LSA vs PPC call pools, CRM fields that survive handoffs, a weekly scoreboard, and co-op data hygiene. It is for multi-unit franchisee operators buying customer / local service leads.

It is not bid strategy or creative (that’s our multi-unit franchise advertising playbook). It is not LSA eligibility, verification, or profile ops (see Google LSA operations across several locations). And it is not franchisor development capacity planning — that closer-bandwidth piece is franchise lead capacity planning, a different audience.

Why Multi-Unit Call Attribution Breaks First

Multi-unit call attribution breaks because shared numbers, mixed call pools, cross-unit handoffs, and co-op reports all land in one bucket. Until each call carries a unit and a source, no dashboard can tell you which location and channel booked the job.

When Unit A and Unit B sit in the same metro, four tracking failures get smashed into one shrug:

1. Shared vanity numbers on the website, GBP, and truck wraps with no source tags.
2. Pool mixing — LSA platform numbers, PPC call extensions, and organic DNI all dump into one CRM “Phone” bucket.
3. Handoff amnesia — Unit A answers, Unit B fulfills, both claim the sale (or neither does).
4. Co-op contamination — corporate or DMA reports get pasted into your unit P&L as if they were your local paid outcomes.

You don’t fix that with a better keyword list. You fix it with a one-stack tracking design every unit can run the same way.

The One-Stack Rule: Same Definitions, Unit-True Numbers

The one-stack rule is simple: every unit uses the same definitions and CRM fields, but each unit keeps its own tracking numbers and phone identity. Shared definitions make units comparable; separate numbers make them attributable.

The organizing rule I use with multi-unit owners:

Share definitions. Separate identity.

Share across units	Keep unit-true
What counts as a “qualified call” (duration, intent, not spam)	Tracking numbers / pools mapped to unit
CRM field names and disposition list	Landing page / GBP phone where brand allows
One-lead / one-credit rule	Answer ownership and overflow path
Weekly scoreboard columns	Budget and capacity ceilings
Recording / consent language standard	Hours and staffing

If Unit 3 invents its own “lead” definition, your portfolio dashboard is fiction. If every unit shares one phone number, your portfolio dashboard is also fiction — just a prettier one.

For broader consolidate-vs-separate decisions (accounts, geo, floors), stay on the multi-unit advertising page. This article stays on calls and attribution.

Shared Vs Per-Location Tracking Numbers

There is no universal winner. There is a default that fails less often for 2–10 units.

Default I recommend: per-location (or per-unit × channel) tracking numbers, with a small shared pool only where the agreement or brand directory forces a single NAP (name/address/phone).

Pattern	When it works	How it breaks
One shared number for all units	Tiny portfolio, central dispatch that tags unit in CRM on every call	Attribution collapses the week dispatch is busy
Per-unit primary + channel pools	Most 2–10 unit operators	Admin overhead if you never document the map
Per-unit × channel (PPC, LSA, organic, offline)	You actually reallocate budget by unit and channel	Too many numbers if nobody owns the spreadsheet

Practical minimum:

• One primary tracking number per unit for organic / GBP / site (confirm NAP rules with your franchisor).
• Separate PPC call pool per unit (or per campaign group that maps cleanly to a unit).
• Separate LSA pool per unit — LSA already thinks in location-true leads; don’t launder it into the PPC pool.
• Offline / wrap / print: either a dedicated offline number per unit or a tagged vanity that still lands in that unit’s CRM row.

Confirm with your franchisor: whether tracking numbers are allowed on the website and Google Business Profile without breaking directory NAP standards. Local listing hygiene still matters — see local franchise marketing if GBP is an afterthought.

Dynamic Number Insertion (DNI) Without Lying to Yourself

DNI swaps the visible phone number based on how the visitor arrived (paid search, paid social, organic, direct). Used well, it attributes website callers to channel. Used badly, it creates three new problems:

1. Session pollution — a prospect sees a PPC number on Monday, Googles the brand Tuesday, calls the organic number, and PPC still “won” in someone’s head.
2. NAP flicker — if DNI rewrites the GBP-matching number on every page view, you can create listing inconsistency. Keep a stable primary for footer/GBP alignment where brand rules require it; use DNI on dedicated landing pages when allowed.
3. Missed mobile — click-to-call on Maps/GBP bypasses your website DNI entirely. Those calls need their own mapping (often the unit primary or an LSA/GBP-associated number).

Operator rules that keep DNI honest:

• DNI is a source tag, not a unit resolver. Unit still comes from landing page, geo, or agent selection.
• Never let DNI overwrite the CRM’s unit field after a human has assigned the job.
• Test with a burner phone: paid landing → number A; organic homepage → number B; GBP → number C. Write the three results on the unit matrix.

Universal: Call-recording consent varies by state. If recording is on, use a clear announcement and get counsel to review all-party-consent exposure when calls cross state lines. Don’t improvise this.

LSA Vs PPC Call Pools (Tracking Only)

Keep LSA calls and PPC calls in separate number pools for each unit. Mixing them makes it impossible to see what each channel actually costs per booked job.

Keep this section narrow on purpose. LSA setup, eligibility, and profile ops live on the LSA multi-location playbook. Here you only need pool discipline.

Pool	What it should prove	Do not do
LSA per unit	Cost and booked rate of LSA leads for that unit	Merge LSA calls into the PPC “Calls from ads” story
PPC per unit	Cost and booked rate of Search/call-extension callers	Use one blended PPC number for every unit in a metro
Organic / site DNI	Non-paid web callers	Treat unpaid branded callers as “PPC wins” because they saw an ad last week
Offline	Wrap / print / referral phone demand	Dump offline into “Google” because the CRM default source is Google

One-lead / one-credit still applies: if LSA at Unit A produces the call and the customer books at Unit B, Unit A owns the lead-cost conversation; Unit B owns the job. Both dashboards claiming the sale is how operators fight instead of reallocate.

CRM Fields That Survive Handoffs

Make unit, source, disposition, fulfilling unit, and credit unit required fields in your CRM. Required fields are the only ones that survive a busy week and a job that moves between locations.

If the field isn’t required, it won’t survive a busy Saturday.

Minimum CRM schema for multi-unit call tracking:

Field	Why it exists
unit	Which P&L owns the outcome
source	LSA / PPC / organic / offline / referral / co-op (separate!)
campaign or pool_id	Ties to the tracking number / ad group
call_duration	Supports your qualified-call definition
disposition	Qualified / booked / spam / out-of-area / duplicate / employee
booked_job (Y/N + date)	The number that actually matters
fulfilling_unit	When answer unit ≠ fulfill unit
credit_unit	Who gets marketing credit under your one-lead rule
co_op_flag	Marks corporate/DMA traffic so it never mixes into local P&L

Handoff rules worth writing down:

1. First agent to save unit + source locks those fields unless a manager override exists.
2. If the job moves units, update fulfilling_unit — do not silently rewrite credit_unit.
3. Spam and employee calls get dispositions the same day so they don’t inflate “leads.”
4. Duplicates: one primary record; secondary calls link to it. Two open leads for one household is how both managers claim victory.

The Weekly Scoreboard: Unit × Channel → Booked Jobs

The number to manage weekly is booked jobs and cost per booked job by unit and channel, not raw call volume. A one-page scoreboard with the same definitions every week keeps that honest.

If your weekly meeting is “how many calls did we get?”, you’re managing the wrong number.

Run a one-page scoreboard every week — per unit and rolled up:

Metric	What it tells you
Qualified calls (your definition)	Real demand
Answer rate during open hours	Ops health
Booked jobs from calls	Outcome
Cost per booked job by channel (LSA pool / PPC pool / organic / offline)	Where the next dollar goes
Share of calls missing unit or source	Tracking debt
Co-op / brand-fund calls (separated)	Hygiene — not your local CPL story
Overflow / misroute count	Routing quality

Keep media tactics on the advertising playbook. The scoreboard’s job is attribution honesty: which unit and which pool booked work.

A healthy pattern I look for: booked rate stable while you reallocate flex budget toward the units and pools that convert — without “averaging away” a dying unit by blending it into a portfolio CPL.

Co-Op And Brand-Fund Data Hygiene

Multi-unit operators routinely paste corporate reports into local decision sheets. That’s how you fund the wrong unit.

Separate three money stories:

1. National brand fund / corporate media — not your unit P&L’s local paid outcome.
2. Regional / DMA co-op — pooled; attribute only what your agreement says you can claim.
3. Your local paid + organic — the only story your floor-and-flex budget should optimize.

Operator hygiene:

• Tag co-op and brand-fund sourced calls with co_op_flag (or a dedicated source value).
• Never let co-op CPL “prove” that Unit 2’s local PPC is efficient.
• When corporate sends a blended DMA report, park it in a Co-op tab — not in the unit scoreboard.

Confirm with your franchisor: what local spend counts toward minimums, what reporting format they expect, and who owns customer data for uploads / offline conversions.

Pitfalls That Quietly Wreck Multi-Unit Tracking

1. One Google Ads “call” column for five units — you cannot reallocate what you cannot see.
2. LSA refunds ignored in the CRM — platform lead cost ≠ your booked economics if spam isn’t dispositioned.
3. DNI on every template including legal/NAP blocks — brand compliance risk for a few attribution crumbs.
4. Managers editing source after the fact to protect a pet channel — lock fields; audit overrides.
5. Celebrating call volume while answer rate is red — buying calls into a full desk is the franchisee version of the capacity trap (different audience than franchisor capacity planning, same math instinct).
6. No overflow plan across adjacent units — boundary customers become double-counted arguments.
7. Recording without a consistent disclosure — legal risk is not a marketing KPI, but it ends marketing meetings.

Build This Week: Unit Matrix + Number Map + Scoreboard

Don’t leave tracking as vibes. Build three artifacts:

1) Unit matrix (one row per unit)

Unit	Primary phone	PPC pool	LSA pool	Offline	Landing page	GBP phone rule	Capacity ceiling
Unit 1
Unit 2

2) Number map — every tracking number → unit → source → CRM pool_id. One owner. Update when you swap vendors.

3) Weekly scoreboard — the table above, same definitions every Monday.

That’s the stack: definitions shared, identity unit-true, pools separated, CRM fields that survive handoffs, co-op kept out of your local P&L.

Frequently Asked Questions

Should I use one call tracking account for all my franchise locations?

Usually yes. One account keeps qualified-call definitions, dispositions, and reporting identical across units, which is what makes them comparable. Inside that account, give each unit its own numbers and pools so calls still attribute to the right location.

Should each franchise location have its own tracking number?

For most operators with 2–10 units, yes. A primary tracking number per unit, plus separate PPC and LSA pools per unit, lets you see which location and channel produced each call. A single shared number only works if dispatch reliably tags the unit on every call.

How does dynamic number insertion work across multiple locations?

DNI swaps the phone number shown on your website based on how the visitor arrived, such as paid search or organic. It identifies the channel, not the unit, so the location should come from the landing page, the visitor’s geo, or the agent who takes the call. Test each unit’s pages with a real phone before you trust the reports.

Will call tracking numbers hurt NAP consistency on my Google Business Profiles?

They can if the number on your listing keeps changing or doesn’t match your site. Keep a stable primary number on each Google Business Profile and in your site footer, and use DNI mainly on landing pages. Confirm with your franchisor what numbers are allowed on listings and brand directories.

Is it legal to record calls across my franchise locations?

It depends on the states involved. Some states require consent from everyone on the call, so use a clear recording announcement on every line and have counsel review your setup, especially when calls cross state lines. Check your state’s consent laws before turning recording on.

How do I attribute a call when one unit answers and another unit does the job?

Track the answering unit, the fulfilling unit, and the credited unit as separate CRM fields. Decide in advance who gets marketing credit under a one-lead, one-credit rule, and update the fulfilling unit when a job moves instead of rewriting the credit. That keeps both managers’ reports honest.

What should count as a qualified call for a multi-unit franchise?

Define it once for all units: a real prospect asking about a service you offer in an area you serve, above a minimum duration you choose, and not spam, a vendor, an employee, or a duplicate. Disposition calls the same day so junk doesn’t inflate lead counts. Then measure booked jobs, not just qualified calls.

How do I keep co-op and brand-fund calls out of my local numbers?

Tag co-op and brand-fund sourced calls with their own source value or flag in the CRM. Keep corporate or DMA reports on a separate tab instead of the unit scoreboard. Your local budget decisions should rest only on your local paid and organic results.

Need Help?

If you want a second set of eyes on multi-unit call tracking — number architecture, DNI, LSA vs PPC pools, or a scoreboard your managers will actually use — fill out our Contact Us form.

We can talk through attribution across the units you own without mixing co-op vanity into local decisions, and without turning this into another bid-strategy meeting.