One campaign, eight locations: how to find out where it actually worked
A campaign that runs across several locations almost never works equally at all of them, and a blended report hides which ones it carried. To find out, read spend against checks one location at a time, compare each location with its own usual week rather than with the others, and move budget only on a difference that holds up.
The number that looks fine and tells you nothing
A group runs one campaign across every location - the new fall menu, say, on Meta and Google, the same creative everywhere. At the end of the month the report comes back with one figure for the brand, and the figure is decent. The meeting moves on.
What that figure can't show is how it was made. A common shape: two locations in dense neighborhoods account for most of the response, a few did about what they would have done anyway, and one spent its share of the budget reaching people who live closer to a competitor. Blended together, it reads as a campaign that worked.
Why locations answer differently
The same ad lands differently because the locations aren't the same business. The one downtown lives on weekday lunch and office parties. The one by the highway is a Saturday destination. The newest is still being discovered, and the oldest has regulars who would come without being asked. Who lives nearby, which dayparts matter, who the competition is and how well known the place already is all change what a campaign can do there.
Where this gets difficult is that the platforms don't report it that way. They report by campaign and by ad, not by which register rang. And unless the campaign was built with a separate budget for each location - most aren't, because it's more work - the platform puts the money wherever its own goal is cheapest to hit, which is not necessarily where your tables are empty.
Reading it one location at a time
The reframe is to stop asking whether the campaign worked and start asking where. That takes three things.
First, spend by location. If the campaign wasn't split, work it out from where the ads were delivered; next time, split it. Second, revenue by location that can be tied to the campaign - checks, not taps on Directions. Third, a fair comparison: each location against its own normal week, not against the others. The downtown location will always outsell the suburban one. The question is which of them moved.
Read that way, a campaign usually sorts its locations into three groups: where it clearly earned its spend, where it made no visible difference, and where there isn't enough to say yet. All three are useful. The third is the one most reports hide.
What to do with the answer
The temptation is to cut the locations where it didn't work. Sometimes that's right. More often those locations need a different campaign, not no campaign - a different offer, a different daypart, a tighter radius. The location carrying itself on regulars may not need ads to find new guests at all, and that budget is better spent on the one still being discovered.
What we'd want to protect is the habit: every campaign read per location, every time, so the group's budget follows the registers rather than last year's split.
Where restauWant comes in
This is the reading the restauWant app does by default. It matches campaigns to checks per location and per night, shows the group, each brand and each location in one view, and keeps what's verified apart from what's estimated - including saying plainly when there isn't enough data yet. Each location can be opened on its own, so a general manager sees their place and ownership sees all of them.
Reading a campaign by location
- Split the budget by location before the campaign runs - or at least record where the ads were delivered.
- Pull each location's checks for the campaign period and for a normal period before it.
- Tie revenue to the campaign where you can prove it - and keep estimates in a separate column.
- Sort the locations into three - earned its spend, no visible difference, not enough to say.
- Change the campaign for the middle group before you cut it.
- Do the same read after every campaign - not once a year.
How do I measure marketing for each restaurant location?
Set spend by location against revenue by location that can be tied to the campaign, and compare each location with its own usual week. A single blended figure for the brand hides the differences.
Should every location get the same ad budget?
Rarely. A new location still being discovered and an established one full of regulars need different things. Let each location's results set its share.
Why don't the ad platforms' numbers match my sales by location?
The platforms count actions on the ad - clicks, calls, taps on Directions - by campaign. They don't see which register a guest paid at.
Can a general manager see only their own location?
In the restauWant app, yes. Access is set per group, brand or location.
