When Two Units You Own Compete in the Same Zips: A Multi-Unit Geo Playbook

If you own two (or five) franchise units that sit near each other, Google will happily let both of them bid into the same household. That isn’t “market share.” That’s you paying twice for one customer — and then arguing about who “owns” the lead.

I’ve sold franchise units myself and I’ve cleaned up a lot of multi-unit Google Ads and LSA setups where Unit A and Unit B were quietly taxing the same ZIPs. This playbook is only about that problem: radius and ZIP fencing, exclusive vs intentional overlap, brand vs non-brand geo splits, shared negatives, LSA/Ads double-tax, and internal lead-ownership rules.

For account structure, budget floors, creative, and brand-fund mechanics, use multi-unit franchise advertising — don’t rebuild that overview here. For LSA ops across several locations (profiles, disputes, budgets), see Google LSA operations for several locations. This article is the geo conflict slice: how to stop your own units from competing in the same auction for the same household.

Audience note: this is multi-unit franchisee customer-demand geo — not franchisor development capacity. If you’re matching franchise buyer lead volume to closers, that’s a different desk (franchise lead capacity planning).

Diagnosing Self-Competition Before You Touch a Fence

Your units are competing if both target the same keywords in overlapping locations and you see rising CPCs, your own ads in auction insights, or CRM duplicates in the ZIPs between them. Confirm it with data before redrawing any maps.

Don’t redraw maps until you’ve proven the tax is real.

Signals I look for when two of your units share a metro:

1. Same keywords, overlapping location targets in two campaigns (or two accounts) — classic auction self-competition.
2. Impression share / auction insights that keep surfacing your other unit’s ads as “competitors.”
3. Call or form volume that spikes in the seam ZIPs while both units’ CPCs climb.
4. CRM duplicates — same phone or address credited to Unit A and Unit B within days.
5. LSA leads and Google Ads leads for the same household in the same week (double-tax across products).

Separate four problems that operators mash into one bad phrase:

Problem	What it actually is
Auction self-competition	Two of your campaigns bidding the same intent into overlapping geo
Territory compliance	Agreement limits on where you may advertise (even between units you own)
Attribution ambiguity	Same household, two tracking numbers, unclear credit
Operational fit	Drive time / staffing decide which unit should fulfill — media should follow that

A customer walking into Unit B instead of Unit A is still your customer. What you fix is the auction tax and the ownership fight — not “cannibalization” as a vague brand fear.

Quick diagnostic checklist (one afternoon):

• Export location reports (or ZIP performance) for both units for 30–60 days.
• Highlight ZIPs where both spend and both convert.
• Pull auction insights / search terms for shared brand and non-brand queries.
• Count CRM duplicates and “wrong unit answered” tickets in the seam.
• Confirm whether LSA service areas overlap the same seam ZIPs as Ads.

If the seam is thin and CPC is stable, you may not need a hard exclusive fence. If the seam is fat and you’re double-paying, fence first — creative later.

Radius and ZIP Fencing Rules That Actually Hold

Give each unit an exclusive core of ZIPs or a polygon, exclude the other unit’s core from non-brand campaigns, and write down a rule for the seam. In dense metros, ZIP or polygon targets hold better than radius.

Quick terminology: most operators need geo-targeting (radius, ZIP, city, polygon, location exclusions). Geofencing usually means ads to devices that enter a drawn polygon (often a competitor storefront). Useful sometimes. Not your default tool for splitting two units you own.

Rules I use when fencing adjacent units:

1. Map the agreement first. Advertising territory ≠ delivery territory ≠ “wherever Google thinks people search.” Confirm with your franchisor in writing where Unit A may advertise vs Unit B.
2. Prefer ZIP or polygon over pure radius in dense metros. Circles overlap by design. Territory lines usually don’t.
3. Core vs halo. Give each unit a core (exclusive ZIPs / tight polygon) and a controlled halo (shared or intentional overlap) if you want intentional competition for overflow.
4. Exclusions beat hope. Explicitly exclude the other unit’s core from Unit A’s non-brand campaigns. Hoping Smart Bidding “figures it out” is how you keep paying twice.
5. Match presence, not ego. If Unit A’s GBP, landing page, and phone all say one address, don’t let Unit B’s ads own that ZIP without a routing plan.
6. Revisit after every unit open / remodel / hours change. Fences rot when operations change and media doesn’t.

Fence type	Best when	Watch-outs
Radius	Rural / clear drive-time bubbles	Circles overlap in suburbs
ZIP lists	Agreement is ZIP-defined	Seam ZIPs still need a rule
Polygon	Odd-shaped territories	Maintenance cost; keep a source-of-truth map
Location exclusions	You own both sides of the seam	Miss an exclusion and self-competition returns

Practical default for two nearby units you own: exclusive cores + documented seam rule (exclusive to closer unit, or intentional shared with ownership rules below). Don’t leave the seam undefined.

Exclusive Geos vs Intentional Overlap — When Each Wins

Exclusive geos win when the agreement requires them, when both units are busy, or when you see frequent double credits. Intentional overlap works only when one unit needs overflow help and there is a written routing and credit rule.

Not every overlap is a mistake. Some are a strategy.

Force exclusive geos when:

• The agreement forbids advertising into the other territory (even if you own both).
• Both units are at capacity and you’re burning cash on CPC inflation.
• CRM shows frequent same-household double credits and staff fights.
• Brand terms are expensive and both units are bidding them into the same ZIPs.
• Drive time clearly favors one unit for a ZIP (15 minutes vs 40).

Allow intentional overlap when:

• One unit is capacity-constrained and the other can take overflow with a written routing rule.
• You’re testing a shared-metro brand campaign with unit-level routing after the click/call.
• The seam ZIP is low volume and fencing cost (missed demand) exceeds auction tax.
• Corporate requires a DMA-level brand presence and local units split fulfillment downstream.

Situation	Default geo stance
Dense metro, two stores 10–20 min apart, both healthy	Exclusive cores + thin intentional halo OR exclusive everything
One unit new / ramping, one mature	Protect mature core; let new unit own its core; shared halo only with routing
Units 40+ minutes apart	Per-unit exclusive geos — overlap rarely worth it
Agreement says “no advertising into Unit B territory”	Exclusive — period

Write the decision down. “We’ll just see who converts” is how both managers claim the same lead and neither fixes the fence.

Brand vs Non-Brand Geo Splits

Brand and non-brand should not share the same geo logic.

Brand (your franchise name / unit name variants):

• Often belongs in a tighter geo — people searching the brand already know you; don’t spray brand bids into a ZIP you can’t serve well.
• If corporate runs national brand, confirm whether local units may bid brand at all.
• When two of your units bid brand into the same ZIP, you are almost always overpaying for navigational demand.

Non-brand (category / service / “near me” intent):

• This is where self-competition hurts most: generic intent + overlapping radius = pure auction tax.
• Fence non-brand aggressively by core ZIP / polygon.
• Shared negatives (next section) matter more here than on brand.

Campaign type	Geo stance I default to
Brand — Unit A	Unit A core (+ tiny halo if intentional)
Brand — Unit B	Unit B core
Non-brand — Unit A	Unit A core; exclude Unit B core
Non-brand — Unit B	Unit B core; exclude Unit A core
Shared brand (rare, intentional)	Metro/halo with post-click unit routing and one-lead/one-credit

If you must run a shared brand campaign across units you own, pair it with per-unit phones / landing paths and an ownership rule. A blended brand campaign with two managers and no routing is a dispute factory.

Shared Negative Lists (And What Must Stay Unit-Local)

Consolidate what benefits from shared volume. Separate what is locally determined. Negatives are usually shared; geos and budgets stay per unit.

Share across units (one maintained list):

• Junk intent (jobs, DIY, wholesale, competitor brand names you’re not allowed to bid, irrelevant services).
• Franchisee-vs-franchisor confusion terms if your category attracts “buy a franchise” searches you don’t want on local customer campaigns.
• Misspellings and known money-wasters discovered in any unit’s search terms.

Keep unit-local:

• Geo exclusions tied to the other unit’s core.
• Local competitor names that only matter near one store.
• Offer / service negatives that only one unit doesn’t sell.

Operating habit: one owner updates the shared negative sheet weekly from all units’ search-term exports. Five managers editing five copies is how Unit A blocks a term Unit B still burns money on.

For the broader consolidate-vs-separate matrix (budgets, creative, tracking), stay on the multi-unit advertising playbook — here we only care that shared negatives + exclusive cores kill most self-competition without rebuilding the whole account.

LSA and Google Ads Double-Tax on the Same Household

Local Services Ads and Google Ads can both charge you for demand from the same ZIP — and if two of your units both run LSAs into that ZIP, you can pay three ways for one household.

This section is not full LSA setup. For multi-location LSA operations, use the LSA several-locations guide. Here we only cover geo / lead-ownership collision with Ads.

Double-tax patterns I see:

1. Unit A Ads + Unit A LSA covering the same core (sometimes fine if you measure incremental; often not).
2. Unit A Ads + Unit B LSA covering the seam ZIP (classic cross-unit tax).
3. Both units’ LSAs with overlapping service areas and no lead-ownership rule.

Geo rules that reduce the tax:

• Align LSA service areas to the same cores you use in Ads — don’t let LSA stay “loose” while Ads are fenced.
• If Ads owns a ZIP exclusively for Unit A, Unit B’s LSA shouldn’t casually cover it unless overflow is intentional and credited once.
• When a household generates both an LSA lead and an Ads call, apply one-lead / one-credit (below) — don’t let both dashboards celebrate.

Channel combo	Risk	Move
Ads Unit A + LSA Unit A, same core	Product double-tax	Measure incrementality; tighten one if CPA stacks
Ads Unit A + LSA Unit B, shared ZIP	Cross-unit double-tax	Fence LSA or Ads; fix ownership
LSA Unit A + LSA Unit B overlap	Self-competition inside LSA	Exclusive service areas or written overflow

Internal Lead Ownership Rules (Who Gets the Lead)

Decide who owns a lead before it arrives: ZIP-based ownership for cores, first valid contact for seam ZIPs, and one credit per household. Put those rules in the CRM as required fields.

Media fences fail if the phone tree and CRM still fight.

Write a one-page ownership policy. Example rules that work in practice:

1. Geo-first: Lead’s ZIP in Unit A core → Unit A credit and fulfillment (unless Unit A is closed / over capacity).
2. First valid contact: If seam ZIP and intentional overlap, first unit to answer on SLA keeps it — other unit does not re-dial the same day to “steal.”
3. One-lead / one-credit: Same phone/email within 30 days = one owner. Second unit can assist fulfillment only with a transfer note — not a second marketing credit.
4. Channel priority (optional): If LSA and Ads both fire, pick a primary credit channel for reporting so you don’t optimize two CPAs for one job.
5. Capacity override: If Unit A is red on answer rate / bookable slots, seam leads route to Unit B and Unit A’s fence or budget throttles until green.

Scenario	Owner
ZIP in Unit A exclusive core	Unit A
ZIP in Unit B exclusive core	Unit B
Seam ZIP, Unit A answered first on SLA	Unit A
Seam ZIP, Unit A missed SLA, Unit B booked	Unit B (note the miss — fix staffing, not the fence alone)
Duplicate form + call same day	First qualified contact’s unit

Put the policy in the CRM as a required field: credited_unit, fulfillment_unit, seam_flag. Dashboards without those fields will keep starting arguments in the Monday meeting.

Weekly Geo Scoreboard

Track core and seam ZIPs separately every week, along with duplicate rate and LSA and Ads overlap. That shows whether the seam is costing you or earning you money.

If your weekly meeting is only CPL by unit, you’ll miss the seam tax.

One-page geo scoreboard:

Metric	Why it matters
Spend + conv in exclusive cores (A vs B)	Are cores healthy?
Spend + conv in seam ZIPs	Is the tax / opportunity concentrated?
% of seam leads with clear credited_unit	Ownership discipline
Duplicate rate (same phone/email, both units, 30 days)	Self-competition residue
Avg CPC brand vs non-brand in seam vs core	Auction inflation signal
LSA leads from ZIPs also paying in Ads	Cross-product double-tax
Answer / book rate by unit in seam	Capacity vs media mismatch

How to use it:

• Seam spend up + duplicates up → tighten exclusions or ownership SLA.
• Core healthy, seam thin → stop obsessing; protect cores.
• Seam converting but one unit never answers → route + capacity fix before more budget.
• LSA + Ads both fat in same ZIP with flat total jobs → cut one product’s geo, not “more creative.”

Owners: media owns fences and exclusions; ops owns answer SLA and credited_unit; whoever owns LSA owns service-area alignment to the same map.

Pitfalls That Keep You Paying Twice

1. Radius-only maps in a ZIP-defined agreement. Circles ignore the contract and each other.
2. Two accounts, same keywords, soft geos. Double-serving risk plus self-competition — fix overlap before you scale.
3. Shared budget, separate egos. Floor-and-flex is fine; undocumented seam fighting is not.
4. Brand campaigns left unfenced while non-brand gets all the attention — navigational CPCs quietly inflate.
5. LSA service areas never updated after Ads fences change.
6. No CRM credited_unit field — every dashboard lies differently.
7. “Temporary” overlap that lasts nine months because nobody owns the map file.
8. Copying Unit A’s campaign and only changing the radius by two miles — exclusions and negatives don’t magically follow.
9. Solving a staffing miss with more overlap — if Unit A can’t answer, throttle Unit A; don’t just let Unit B bid harder into A’s core without a policy.
10. Rewriting the whole multi-unit advertising stack when you only needed a seam rule — keep structure docs on the multi-unit advertising page and keep this page about geos and ownership.

Frequently Asked Questions

How can I tell if my own franchise units are bidding against each other?

Look for the same keywords targeted in overlapping locations across two campaigns or accounts. Auction insights showing your other unit as a competitor, rising CPCs in the ZIPs between units, and the same household credited to both units in the CRM are strong signs. Pull 30–60 days of location data for both units to confirm.

Should my units share one Google Ads campaign or have separate campaigns?

Most operators do better with separate campaigns per unit, each targeting its own core and excluding the other unit’s core. Share negative keyword lists across units, but keep geos and budgets per unit. A shared campaign can work for brand terms only if calls and forms route to the right unit after the click.

Is radius or ZIP code targeting better for overlapping franchise territories?

In dense metros, ZIP or polygon targeting is usually better because radius circles overlap by design and rarely match territory lines. Radius works in rural areas where drive-time bubbles are clear. If your agreement defines territory by ZIP, target by ZIP.

How do I split Local Services Ads service areas between units I own?

Match each unit’s LSA service area to the same core ZIPs you use in Google Ads. Avoid letting two units’ service areas overlap unless one is intentionally taking overflow under a written rule. Review LSA service areas whenever you change your Ads geos.

What should I do when a lead comes in from a ZIP on the border between two units?

Follow a written seam rule instead of deciding case by case. A common approach is that the first unit to make valid contact within your response-time standard keeps the lead, and the other unit doesn’t call the same customer. Record a seam flag and a single credited unit so the lead isn’t counted twice.

Do franchise agreements restrict advertising between units I own?

Often they do, even when you own both units. Advertising territory can differ from delivery territory, and some agreements limit where each unit may advertise. Check your FDD and franchise agreement, and confirm with your franchisor in writing before setting up overlap.

Should both of my units bid on our brand name in the same area?

Usually not. People searching your brand already know you, so two units bidding the brand into the same ZIPs mostly raises your own cost. Keep brand campaigns tight to each unit’s core, and confirm whether corporate allows local brand bidding at all.

How often should I review territory fences for my units?

Review them weekly on a geo scoreboard and redo the map after any unit opens, relocates, remodels, or changes hours or staffing. Fences drift out of date when operations change and campaigns don’t. Keep one source-of-truth map with a single owner.

Need Help?

If two (or more) units you own are bidding into the same ZIPs and you want a clean fence + ownership map — without rebuilding your whole media stack — fill out our Contact Us form.

We can walk your cores, seam ZIPs, Ads vs LSA overlap, and the one-page lead-ownership rules that stop Google from taxing you twice for the same household.