Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Frameworks › The Measurement Plan Framework

Measurement Plan for Store Visits

A measurement plan for store visits: modelled visit conversions, store-locator events, offline sales matching and geo holdouts to prove media moved footfall.
Objective guideintermediate7 min readUpdated

Why footfall breaks the event-led plan

The generic plan proves each goal with an event that a tool records for the person who did it. A store visit has no such event. The website sees someone search for the nearest branch and then loses them; the ad platform may later infer, from location data on some phones, that a person who saw an ad was near the store; the till records a sale with no link to either. Each of those is a fragment of the same journey, and none of them can be stitched to the others reliably at the level of a person.

That pushes the plan in two directions at once. Downwards, towards signals the website and the business profile can capture, which stand in for the visit. And upwards, towards aggregate comparisons of sales by region and week, which are the only place the actual outcome is counted. The local marketing hub describes the local system the plan has to measure: presence, reputation, local advertising and the multi-location layer.

Decisions that change for store visits

Plan componentIn the generic planIn a store-visit planDecision it forces
Goal evidenceA tracked conversionWebsite intent proxies and business-profile actionsWhich proxies are trusted enough to carry a target
Platform conversionsObserved and attributedStore visits modelled from location data, available above eligibility thresholdsWhether to use them for bidding, reporting or neither
Outcome dataAnalytics or CRM, per userTill data by store and weekHow stores map to media regions
Proof of effectAttribution reportExposed against holdout regionsWhich regions are held out, chosen before launch
SegmentsChannel, device, audienceStore, catchment, regionWhich store attributes explain differences
OwnersMarketing and analyticsMarketing, store operations and financeWho supplies sales data, and how fast

Choose the website proxies

Store locator searches, requests for directions, clicks on a store's phone number and stock or availability checks are the closest things to a visit that the site records. Each is a KPI candidate, but they differ in how near they sit to the trip: a directions request usually precedes a visit, a page view of opening hours may only be curiosity. Specify each as an event with a store identifier attached, so it can be read per location. The trade-off is between many weak proxies and a few strong ones; choose two or three and check, using a past period, that they rose and fell with regional sales before trusting them.

Treat platform store visits as modelled estimates

Some ad platforms report store visits for advertisers who meet their eligibility thresholds, inferred from location data on a sample of phones and scaled up. The figures are useful and they are models: they credit visits under the platform's own Attribution rules and cannot tell a visit caused by the ad from one that would have happened anyway. The plan should record which platforms report them, whether the account is eligible, and what they are used for. Choose to use them for comparing campaigns inside one platform, never for adding across platforms or proving the total effect. The geo-targeted campaigns guide covers setting up store visit and call goals in the campaigns themselves.

Match till data to media by region and week

The outcome the business cares about, sales in stores, is counted by the till system, and it cannot be joined to individual ad exposures. The plan therefore defines a geography that both sides share, such as groups of postcode districts around each store, and a weekly calendar both sides use. Media delivery and spend are reported into the same regions and weeks. The cost is precision: regional data hides who responded. The gain is that the measure is the real outcome. Choose regions large enough for weekly sales to be stable, and get store operations to commit to a delivery date for the data, since a late feed stalls every reading.

Design holdout regions before the campaign starts

Regional matching shows that sales rose where media ran; only a comparison with similar regions where it did not run shows the rise was caused by the media. Pick holdout regions using past sales so they track the exposed regions closely, and fix them before launch. This is Incrementality testing applied to footfall; the incrementality testing guide covers geo designs and how to read them. Holding regions back costs sales if the campaign works; choose a holdout share the business can afford and say so in the plan, so nobody switches the holdouts on mid-flight.

Read business-profile actions beside media data, per location

Calls, direction requests and website clicks from each location's business profile are among the few signals tied to a specific store. Read them weekly per location beside the media delivered into that store's catchment. The Google Business Profile guide covers keeping each profile accurate, and the guide to location pages and listings at scale covers the single source of location data that makes per-store reporting possible. Choose to add store attributes, such as size and parking, as segments, because they often explain more than the media does. When one location's calls and direction requests fall while its profile still appears, the diagnosis for Business Profile calls and directions dropping checks the profile's details, reviews, numbers and duplicates before the media is blamed.

Decision points in a worked store-visit plan

Illustrative example — not a real result

A footfall measurement plan for an invented garden-centre group, Fernhollow

Fernhollow runs 18 garden centres. Its spring campaign runs for five weeks from mid-March, with £150,000 across local search, social and digital outdoor near 14 of the centres. The other 4, matched on the previous two springs' weekly sales, are held out. The plan, condensed:

GoalKPISourceGrainTargetRead
People plan a visitDirections requests and store-page stock checksWebsite events with store_id, business profilesStore, weekUp 25% on last spring in exposed storesWeekly
Platforms see visitsModelled store visits per campaignSearch platform, account eligibleCampaign, weekUsed only to compare campaignsWeekly
Visits turn into salesTill transactions and revenuePoint-of-sale feed, delivered TuesdaysStore catchment, weekn/aWeekly
Media causes the upliftSales growth in exposed against holdout storesPoint-of-sale feedGroup, campaign periodExposed stores 6 points ahead of holdoutsTwo weeks after the flight
Locations stay accurateProfile accuracy audit pass rateListings toolStore100% before launchOnce, then monthly

In the first spring the exposed stores grew sales 11% and the holdouts 4%, a gap of 7 points. Platform store visits suggested a much larger effect, because they also counted regular weekend visitors.

The plan's value lay in the decision taken in January, not in March: choosing the four holdout centres while everyone still agreed they were fair. Without them, the spring rise would have been credited to the campaign in full, since garden centres are busy every spring.

Measuring the plan: KPIs and cadence

The KPIs for a footfall plan sit at three levels. Intent: directions requests, calls, store-locator searches and stock checks per store. Modelled visits: platform store-visit counts per campaign, read within each platform. Outcome: store transactions and revenue per region and week, and the gap between exposed and holdout groups. Read intent and media delivery weekly per store. Read sales weekly but judge the campaign only after the flight, on the full period, since weather and bank holidays swamp single weeks in retail. The plan also tracks its own inputs: the date the till feed arrived, the share of events carrying a store identifier, and the profile audit result.

Where a store-visit plan misleads

Modelled visits are built on samples of phones whose owners share location, which may not resemble the customer base. Regional comparisons absorb local events, a competitor opening, roadworks or a local news story, that land in one group and not the other. Website proxies favour customers who research online and miss the ones who simply drive past. And a holdout shows the effect of the campaign as a whole, not which channel within it did the work; splitting that needs separate tests.

The store visits objective hub sets out the KPI set this plan collects and the channels whose effect it has to measure.

Common mistakes

  • Using modelled visits as the outcome. They steer campaigns within a platform; they do not prove footfall.
  • Choosing holdouts after the campaign. Regions picked later tend to be the ones that make the result look good.
  • Events without a store identifier. A proxy that cannot be read per location loses most of its value.
  • Reading single weeks. Weather and holidays move footfall more than media does in any one week.
  • Letting the till feed slip. If sales data arrives late, the plan reports only proxies.
  • Ignoring listing accuracy. Wrong hours or locations on profiles undo the campaign at the last step.

Frequently asked questions

Are platform store-visit conversions accurate enough to optimise against?

They are useful for comparing campaigns within one platform, because the same model is applied to each. They are less useful for comparing platforms or for proving the campaign caused visits, since each platform models from its own location data and credits visits that might have happened anyway. The plan should use them to steer within a platform and use regional sales and holdouts to judge the whole.

Which website events best stand in for a store visit?

The ones closest to leaving for the shop: requests for directions, clicks on a phone number, a store-locator search followed by a store page view, and stock or availability checks for a named store. Page views of opening hours are weaker but still useful. Test which proxies move with regional sales before giving any of them a target.

How large should holdout regions be?

Large enough that normal week-to-week variation in their sales is small compared with the effect the campaign is expected to have, and similar enough to the exposed regions in size, seasonality and store mix. That usually means grouping several catchments together rather than holding out a single store, and checking the match on past sales before launch.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Google Business Profile Help — Google Business Profile Help
  2. [GA4] About events — Google Analytics Help

Related