How to Measure Marketing Performance Across Multiple Locations

The core problem: same words, different numbers

Ask five location managers how many leads they had last month and you may get five answers built five ways. One counts form fills from the website. One counts calls logged at the front desk. One reads the Google Business Profile dashboard. One includes walk-ins. One asks the agency. Each number is defensible. None of them can be compared, and head office ends up allocating budget by reputation, seniority or volume of complaint.

The fix is not a fancier dashboard. It is a measurement setup in which every location is counted the same way, so differences in the numbers reflect differences in performance rather than differences in counting. The strategic side of multi-location marketing (what stays central, what goes local) is covered in marketing strategy for multi-location organizations. This article is about the measurement underneath it.

Write one conversion dictionary for every location

Start with a single list of what counts, used by every location, every supplier and every report. For each conversion, define what it is, how it is confirmed and where it is recorded.

• Primary conversions: appointment or booking requests, quote requests, connected phone calls, completed bookings or purchases.
• Secondary signals: direction requests, phone taps, location page visits, Business Profile website clicks.
• Outcomes: booked appointments that took place, signed jobs, revenue, where the operating systems can supply them.

Then settle the awkward cases explicitly. Does a walk-in count, and who records it? Is a call that reaches voicemail a lead? Does an inquiry that one location refers to another count for the first, the second or both? Write the answer down once. Our article on what should count as a marketing conversion covers the general principles; the multi-location twist is that every location must apply them identically, including the ones that feel their situation is special.

Capture the location on everything

If a conversion does not carry its location, it cannot be reported by location, and someone will end up allocating it by guesswork. Location needs to be captured at the point of conversion, in every system.

• Website events. Each primary event carries a location parameter, taken from the location page the visitor was on or the location they chose in the form. One event with a location parameter is far easier to report on than a separate event per branch.
• Forms. A required location field where the visitor could plausibly mean more than one, rather than relying on which page they happened to be on.
• Calls. A distinct tracked number per location, at least for the website and Business Profile, so calls can be attributed without asking every caller.
• Business Profiles. One verified profile per real location, each linking to its own location page with campaign parameters, so profile traffic is identifiable in analytics. The listing side is covered in local SEO for multi-location businesses.
• Booking and point-of-sale systems. Location identifiers that match the ones used in analytics and the CRM, so records can be joined.
• The CRM. A location field on every lead and opportunity, filled automatically from the form where possible.

Decide which location gets credit when they differ: the one the visitor chose, the one that served them, or the one nearest to them. Most organizations should credit the location that served the customer for revenue, and the location chosen at inquiry for lead volume, and say so in the definitions.

Give each location the same view

Location managers should see their own numbers, built from the same template as everyone else’s. A useful location view is short:

• Primary conversions this month, against the same month last year and against target.
• The split by source: search, maps and Business Profile, paid, referral, direct.
• Calls, including missed or unanswered calls if the phone system can report them.
• Business Profile actions and new reviews, with the average rating trend.
• Where available, how many inquiries became booked appointments or jobs.

The point of the location view is not surveillance. It is to let a manager see what is in their control. A location with healthy inquiry volume and poor bookings has an operational question: response time, phone handling, availability. Marketing cannot fix a phone that goes to voicemail at lunch, but the report can show it is happening.

Roll up for leadership, and compare fairly

Leadership needs one report covering all locations, built from the location views, not assembled separately. It should show the organization’s totals against target, each location side by side on the same handful of measures, and the shared programs (brand campaigns, organization-wide search) that do not belong to any one location. Our guide to the executive marketing dashboard describes the structure.

The hardest part is comparing locations fairly. A branch in a city of a hundred thousand people will outproduce one in a town of five thousand on every raw measure, and cutting the town’s budget because of it is usually a mistake. Better comparisons:

• Each location against its own history, same period last year, which also handles seasonal patterns that differ between, say, a coastal location and an inland one.
• Each location against its capacity, where capacity is measurable: chairs, rooms, technicians, appointment slots.
• Rates rather than volumes: inquiry-to-booking rate, cost per booked appointment, share of calls answered.
• Locations grouped with their peers: urban with urban, rural with rural, new with new.

Handle shared spend honestly

Some marketing benefits every location at once: brand campaigns, the main website, organization-wide search ads, sponsorships. Do not force all of it into location reports. Three workable approaches:

• Report shared programs separately at the organization level and judge them on total results.
• Allocate shared costs to locations using a simple, written rule (by conversions, by capacity or equally) and accept that it is a convention, not a measurement.
• Where locations run their own campaigns as well, keep those in clearly separated campaigns with location in the name, so they never mix with shared spend. The account structure for this is covered in paid media accounts for multiple locations.

Whichever you choose, say which on the report. Most arguments between locations and head office about marketing are really arguments about an allocation rule nobody wrote down.

Govern it centrally

Consistency does not survive on goodwill. It needs a few written rules, owned by someone at the centre:

• The organization owns every account: GA4, Tag Manager, ad accounts, Business Profiles, call tracking, the consent platform. Locations and suppliers get access; nobody owns a location’s data personally.
• One naming convention for locations, used identically in analytics, the CRM, ad campaigns, call tracking and booking systems. “Saint John”, “SJ” and “St. John” are three locations to a database.
• One UTM convention for campaign links, including location-run promotions and print material.
• Change control: no location or supplier adds tags, forms or tracking numbers without going through the central owner.
• A new-location checklist: location page, Business Profile, tracked number, location value in every system, test conversion run, added to reports. Each item ticked before the location goes live.
• A closure and merger rule: what happens to a location’s history, numbers and profiles when it closes or combines with another.

A worked example

An illustrative case. Say a physiotherapy group runs six clinics across New Brunswick and Nova Scotia, two in cities and four in smaller towns. Each clinic manager has been reporting “new patients” their own way, and head office is about to move budget from two town clinics to the city ones.

The group writes one dictionary: a lead is an online booking request or a connected call to a clinic’s tracked number; an outcome is a first appointment attended. Location is captured from the clinic chosen in the booking form and from the tracked number. Each manager gets the same monthly view; leadership gets a roll-up comparing each clinic with its own prior year and its available appointment slots.

The picture changes. The town clinics turn out to fill a higher share of their capacity from fewer leads, while one city clinic has plenty of inquiries and a low rate of attended first appointments, traced to a front desk that cannot answer calls during peak hours. The budget decision becomes an operational one.

That is the value of comparable numbers: they move the conversation from whose location is better to what each location needs. In our analytics and measurement work for multi-location clients, the dictionary and the naming convention come before any dashboard, because a beautiful report built on five counting methods is still five counting methods.