On this page
- 01Key takeaways
- 02The two views every network needs
- 03Standardize definitions before comparing locations
- 04Measure discovery by market
- 05Attribute calls and forms to the correct location
- 06Connect follow-up and pipeline outcomes
- 07Account for market size and maturity
- 08Use trends, not one-month snapshots
- 09A practical location scorecard
- 10See both views working together
- 11Frequently asked questions
- 12References
A business with one location asks one question of its marketing: is it working? A business with forty locations has to ask that question forty times, and then a forty-first time about the network as a whole.
That is the real measurement problem, and most multi-location reporting solves only half of it. It shows head office a tidy network total, or it hands each location a page of its own numbers, but it rarely holds both at once. We have run marketing measurement for multi-location home-service networks for years, and the method that holds up is simple to state: measure at two levels at the same time. A network view for the decisions head office makes, and a location view for the accountability each operator owns. This article is how we build that, from discovery through to revenue, without either view drowning out the other.
Key takeaways
- Measure at two levels at once: a network view for strategy and governance, and a location view for local accountability. Everything else in this article follows from that.
- You cannot compare locations until the definitions match. A lead and a qualified lead have to mean the same thing at every location before any chart is honest.
- Local visibility legitimately varies by market. Google ranks local results on relevance, distance, and prominence, and states there is no way to pay for a better local ranking.
- Judge locations on trends, not one month. For Smart Bidding, Google recommends evaluating performance across periods with at least 30 conversions, or 50 for Target ROAS. In GA4, some reports can also be subject to data thresholds when user or event counts are low.
- Build one per-location scorecard across visibility, leads, conversion, follow-up, and revenue, then roll it up.
The two views every network needs
Multi-location measurement should preserve two views at once: a network view for strategy and governance, and a location view for local accountability, investment, and improvement.
The two views answer different questions and belong to different people. The network view is what head office reads to decide where to invest, which markets are healthy, what to standardize across the system, and whether a problem is spreading or isolated. The location view is what a single operator reads to know whether their location is getting found, whether their leads are being handled, and whether local demand is turning into revenue. Both run on the same chain of measurement, from visibility to leads to conversion to follow-up to revenue. Read that chain from the top and you see the network. Read it one location at a time and you see what each operator is actually dealing with.
The failure mode is picking one. A network-only report averages away the single location that is quietly leaking, because its shortfall vanishes into the total. A location-only report gives forty operators forty scorecards and gives head office nothing to steer with. Measuring by location does not replace the network view. It makes the network view honest, because a network number you cannot break down by location is a number you cannot act on. Holding both together is the backbone of a Franchise & Multi-Location Growth System.
Explore the Franchise & Multi-Location Growth SystemStandardize definitions before comparing locations
You cannot fairly compare locations until every location counts the same things the same way. Standardize the definitions first, then compare.
The fastest way to produce a misleading location report is to let each location define its own terms. One counts every form fill as a lead. Another counts only the forms its front desk judged worth a callback. A third runs a local vendor whose “conversions” turn out to be newsletter signups. Put those three on one chart and the chart is fiction. Before any comparison, agree on a shared dictionary and configure it identically everywhere.
Google's own definitions are a useful anchor, because they tie a counted action to real business value rather than activity. A key event in Google Analytics is “an event that measures an action that's particularly important to the success of your business” ( Google Analytics Help, About key events). A conversion in Google Ads is an interaction that leads to a behaviour valuable to you, such as a purchase, a sign-up, or a phone call (Google Ads Help, About conversion tracking). The discipline is to decide once what a lead is, what a qualified lead is, and what counts as a booked job or sale, then to define those same key events and conversion actions across every location's property and landing page. Count real outcomes, not raw form fills, and count them the same way in every market. Only then does a comparison between locations mean anything.
| Term | What it must mean network-wide | How it is counted |
|---|---|---|
| Discovery / visibility | A person found this location in its market | GBP views and searches; sessions to the location page |
| Lead | A person asked this location to contact them, or booked | Form submissions and tracked calls, defined identically everywhere |
| Qualified lead | A lead that fits the service, area, and intent worth pursuing | Marked by one agreed rule, not each location's judgment |
| Conversion / key event | The specific valuable action you optimize toward | The same GA4 key event or Ads conversion action at every location |
| Booked job or sale | A lead that became paid work | Recorded in the CRM and fed back to the ad platform |
| Revenue | The money that work produced | Attributed to the location that earned the lead |
Measure discovery by market
Start measurement upstream, at discovery. Ask whether each location is being found in its own market, and accept that visibility legitimately differs from one market to the next.
Before a location can win a lead, someone has to find it. Google Business Profile reports discovery per location: how many people viewed the profile on Search and Maps, the searches they used, and the actions they took, including calls, requests for directions, and clicks to the website (Google Business Profile Help, Understand your Business Profile performance). For a network, the same metrics are available in bulk through the Business Profile Performance API, so you can pull every location into one dashboard instead of opening profiles by hand (Business Profile Performance API).
The harder truth to build into your reporting is that local visibility is not the same everywhere, and that is not always a performance problem. Google says local results are based mainly on three things: relevance, how well a profile matches the search; distance, how far the business is from the person searching; and prominence, how well known the business is, based partly on links and reviews (Google Business Profile Help, Tips to improve your local ranking on Google). Distance and prominence can differ substantially by market for structural reasons a location cannot fully control, though prominence can be improved over time through stronger local authority, links, and reviews. Google also states plainly that there is no way to request or pay for a better local ranking, so visibility is earned through the profile, the site, and genuine reviews. More reviews and positive ratings can help a location's local ranking, and replying to them shows customers you value their feedback (Google Business Profile Help, manage customer reviews).
One more constraint shapes what you measure. Google uses the mobile version of a site's content for indexing and ranking, so each location page needs to preserve its important content and functionality on mobile (Google Search Central, mobile-first indexing). Measure discovery per location, but always read it against the market rather than against a network average.
Attribute calls and forms to the correct location
Every call and form has to land against the right location, or the entire per-location view is guesswork. Build attribution in before you compare anything.
A lead that cannot be traced to a location is a lead you cannot manage or measure. Location-level attribution rests on a few mechanics, each of which Google documents. For web forms, the Google tag goes on every page of the site, and a conversion action, or a GA4 key event, fires when the form is submitted (Google Ads Help, use the Google tag; Google Ads Help, about conversion tracking). Give each location its own landing page or its own conversion action so the submission is credited to that location's line rather than a shared pool.
For calls, Google Ads phone call conversion tracking records calls made straight from an ad and calls to the number on your website, using a Google forwarding number that shows a tracking number to people who arrived from an ad, and it counts a call once it lasts longer than a minimum duration you set (Google Ads Help, about phone call conversion tracking). Location assets carry each store's address and a call button into the ads themselves (Google Ads Help, about location assets). The Business Profile Calls metric also reports call activity per location, though it is worth remembering exactly what it counts: clicks on the call button, not answered calls (Google Business Profile Help, Understand your Business Profile performance).
Finally, feed the result back from the CRM. Enhanced conversions for leads matches a lead that later becomes a customer back to the ad interaction that produced it, using hashed first-party data, as long as the closed conversion is uploaded within 63 days of the click (Google Ads Help, about enhanced conversions for leads; Google Ads Help, guidelines for importing offline conversions). That is what ties a booked sale back to the location and campaign that earned it.
| What arrives | How it is tracked | How it ties to the location | Limitation to remember |
|---|---|---|---|
| Website form | Google tag on every page plus a conversion action or key event | A distinct per-location page or conversion action | Only as accurate as the tag and the page setup |
| Call from an ad | Phone call conversion tracking; counted past a minimum duration | The ad and location asset for that location | Very short calls are not counted |
| Call from the site or profile | Google forwarding number; GBP call-button metric | The location's number and profile | GBP counts button clicks, not answered calls |
| Closed sale from CRM | Enhanced conversions for leads, uploaded within 63 days | The location and campaign that earned the lead | Uploads past 63 days are not imported |
Connect follow-up and pipeline outcomes
A lead you measured but never followed up is a cost, not a result. Connect each location's leads to an owner, a response time, and a pipeline outcome, or the numbers upstream do not matter.
Most networks measure discovery and leads and then stop, which is exactly where the money is lost. Two locations can generate the same number of leads and produce very different revenue, and the difference is almost always what happens in the minutes and days after the lead arrives. So the location view has to continue past the form. Every location's leads need a single destination and a named owner rather than a shared inbox nobody is accountable for. Response speed and pipeline progression should be measured per location, because those are the variables an operator can actually move. And the outcome has to be fed back: when a lead becomes a booked job, that result belongs in the same system that recorded the lead, so the location view ends in revenue rather than in a count of enquiries.
This is the back half of the visibility-to-revenue chain, and it is where real lead volume either becomes revenue or stalls out of sight. Across the Merry Maids Canada network we have measured more than 1,350,000 genuine leads over five years, with 93 percent coming through local websites and 83 percent organic (our work with Merry Maids Canada). Volume at that scale only becomes revenue when every location owns the follow-up behind it.
Account for market size and maturity
Do not rank locations on raw totals. A downtown location and a small-town location are not comparable until you adjust for market size, competition, and how long the location has been open.
A raw leaderboard rewards the biggest market and punishes the newest location, and it teaches head office the wrong lesson every month. A location in a dense city with a five-year head start will out-produce one that opened in a small market last quarter, and neither fact tells you which is better run. Fair comparison means comparing rates and context, not totals. Look at conversion rate rather than lead count, cost per qualified lead rather than raw spend, follow-up speed, and each location's share of the demand available in its own market. Put the context beside the numbers: the size of the market, the level of competition, and the number of months the location has been operating.
This is not only fair, it reflects how discovery actually works. As the discovery section showed, distance is measured from each searcher and prominence depends on links and reviews that differ by area, so part of the gap between two locations is structural, not fully a matter of effort, even though prominence is something a location can build over time. You can never make two markets perfectly comparable, and it is honest to say so. But a comparison that accounts for market size and maturity beats a raw ranking that just measures how big and how old a market is.
Use trends, not one-month snapshots
Judge each location on its trend over time, not on a single month. Per-location samples are small, and one month rarely holds enough data to mean anything.
Break a network into locations and you also break its data into small samples, and small samples swing hard from month to month. A location that looks like it collapsed in February may simply have had a quiet four weeks. Google's own guidance is the clearest argument for reading trends instead of snapshots. For automated bidding it recommends evaluating performance over periods with at least 30 conversions, and 50 for target return on ad spend (Google Ads Help, about Smart Bidding). Google Analytics can also apply data thresholds that withhold some information when a report covers a narrow date range with low user or event counts, a situation that a single location viewed over a single month can produce (Google Analytics Help, about data thresholds).
When you do compare periods, compare like with like. Conversion windows should match, since a recent period's clicks may still convert later and will under-report if you close the books too soon (Google Ads Help, about conversion windows). Know which attribution model your report uses, too. Data-driven attribution is now the default in Google Ads for most conversion actions, and the older rule-based models, first click, linear, time decay, and position-based, are no longer supported (Google Ads Help, about attribution models), with Google Analytics removing the same models in November 2023 (Google Analytics Help, get started with attribution). Give a new location a ramp before you grade it, use period-over-period and year-over-year comparisons, and read each location for direction and consistency over time.
A practical location scorecard
Bring it together in one per-location scorecard that runs the full chain from visibility to revenue, with market context beside it, then roll every location up to the network view.
Everything above becomes usable when it lives on one scorecard that both an operator and head office can read. The scorecard follows the chain: discovery, leads, qualified leads, conversion rate, follow-up speed, and pipeline or revenue, with market context and a trend indicator sitting alongside so no number is read on its own. An operator sees their own line and the handful of measures they can influence this month. Head office reads the same measures rolled up, as totals, medians, and outliers, which is what turns a pile of location reports into a single marketing dashboard worth trusting. For the dashboard structure itself, see What a Franchise Marketing Dashboard Should Show at the Location Level. The same scorecard serves both views because it is built on the shared definitions from earlier, so a qualified lead means the same thing at the location level and across the whole network. Review the fast-moving measures monthly, and the structural ones, market share and cost per qualified lead, quarterly, once there is enough data to trust them.
| Measure | Location view (the operator) | Network view (head office) | Read it as |
|---|---|---|---|
| Discovery | Views, searches, and actions on this profile | Visibility by market, outliers flagged | Against the market, not the average |
| Leads | Forms and calls this location received | Total and median leads per location | Volume, adjusted for market size |
| Qualified leads | Leads that met the agreed rule | Share qualified across the network | Quality, not just quantity |
| Conversion rate | Leads that became booked work | Distribution and low outliers | A rate, comparable across markets |
| Follow-up speed | Time to first response | Locations that are slow to respond | The most movable number |
| Pipeline / revenue | Revenue attributed to this location | Revenue by market and by opening year | The outcome the chain exists for |
| Market context | Market size, competition, months open | The context that makes a ranking fair | Why a gap may be structural |
| Trend | Direction over several months | Which way the network is moving | Direction beats any single month |
See both views working together
A network that measures both views can do two things at once that a single-view network cannot: invest head-office money where the evidence says it pays, and find the one location that is losing ground before another quarter goes by. That is the whole reason to measure by location without losing the network picture.
If you want to see what that looks like across your locations, explore the Franchise & Multi-Location Growth System. If you would rather start with a second set of eyes on where growth is stalling today, request a Growth Opportunity Audit.
Find your biggest growth gapsFrequently asked questions
How should multi-location companies report marketing?
With two linked reports built on one shared set of definitions: a per-location scorecard that each operator owns, and a network roll-up that head office reads. The reports are only comparable because a lead, a qualified lead, and a conversion are defined and configured the same way everywhere, so the network total can always be broken back down to the location that produced it.
What is the best way to compare franchise locations fairly?
Set the right context beside every location, then rank on rates instead of totals. Weigh each location against three things: the size of its market, the competition it faces, and how many months it has been open. Compare on conversion rate, cost per qualified lead, and follow-up speed, read as a trend, so a busy market and a location that opened last quarter can sit on the same chart without one flattering the other.
How can a franchise track leads and revenue by location?
Attribute at the source, then close the loop. Each location needs its own tracked destination for calls and forms, so a lead is credited to the right place the moment it arrives. Then closed sales have to travel back from the CRM to the location that earned them, so the number you end on is revenue rather than enquiries. The goal is one unbroken path per location, from the first click in a local market to the paid job.
Which marketing numbers should each location owner actually see?
Give each operator their own line only, and only the measures they can change week to week: response time, conversion rate, and the quality of the leads they are working. Keep the network roll-up, the budget decisions, and the cross-market comparisons with head office. Showing an operator the entire network's numbers mostly invites them to explain away a local shortfall with figures they do not control.
References
- Lime Advertising. Merry Maids Canada: One lead system across a national franchise network. Case study.
- Google Analytics Help. About key events. Google.
- Google Ads Help. About conversion tracking. Google.
- Google Ads Help. Use the Google tag for Google Ads conversion tracking. Google.
- Google Business Profile Help. Understand your Business Profile performance. Google.
- Google Business Profile Performance API. Google for Developers.
- Google Business Profile Help. Tips to improve your local ranking on Google. Google.
- Google Business Profile Help. Manage customer reviews. Google.
- Google Search Central. Mobile site and mobile-first indexing best practices. Google.
- Google Ads Help. About phone call conversion tracking and measuring calls from ads. Google.
- Google Ads Help. About location assets. Google.
- Google Ads Help. About enhanced conversions for leads. Google.
- Google Ads Help. Guidelines for importing offline conversions. Google.
- Google Ads Help. About Smart Bidding. Google.
- Google Analytics Help. About data thresholds. Google.
- Google Ads Help. About conversion windows. Google.
- Google Ads Help. About attribution models. Google.
- Google Analytics Help. Get started with attribution. Google.
About the reviewer
Vitor Lima
President, Lime Advertising
Vitor leads Lime's growth, technology, strategy and next chapter as a Marketing & Growth Agency for the AI Era. He brings more than 25 years of experience across marketing, technology, ecommerce, franchise growth, business systems and operations.