TagPipes Companion for Chrome Add to Chrome →

Analytics

One Store, One Key: Fixing Location-Level Reporting for Restaurant Brands

Three reports, three answers

Ask three systems how one store did last month and you'll often get three answers. Analytics calls it "Midtown." The ordering platform calls it "Store 0142." The ad account's location report calls it "ATL Peachtree." Those names are made up for this post. The pattern isn't.

Nobody can join those reports, so someone exports three spreadsheets and matches rows by hand. Location-level return on ad spend turns into a guess. And the stores that look best are often just the ones with the cleanest names, because they're the only rows that matched.

Why it happens

Each tool was set up separately, often years apart, by whoever owned it at the time. The ordering platform got store numbers from operations. Marketing named the analytics values after neighborhoods. An agency built ad locations from the listing titles. The reservation tool got whatever each general manager typed in.

None of those choices was wrong on the day it was made. They just never met. That's why another dashboard won't fix it: a dashboard joins data on a shared field, and right now there isn't one.

The location key

The fix is a decision, not a tool. Agree one stable ID per store and carry it on every record.

  • Stable. It doesn't change when a store is renamed, remodeled or changes hands. A short code or number holds up better than a name.
  • Owned. One person issues new keys and retires old ones. Without an owner, the next new store gets a key in a different format.
  • Registered. A short register, one row per store, maps the key to every name each tool uses: the ordering platform's store number, the POS location, the analytics value, the listing and the reservation venue.

The register is the part people skip, and it's the part that saves your history. With it, you can translate last year's reports into the new key instead of starting over.

Where the key has to appear

  • Online orders: every order record carries the key, not just a store name.
  • Reservations: the same, in the reservation tool's export.
  • Analytics: the key as a parameter on store page views, checkout and the order event.
  • Google Business Profile: the store code. Google lists Store code under the profile's Advanced settings and describes it as a way to keep multiple profiles organized (Manage advanced profile settings). Set it to the key.
  • POS export: the location column uses the key, or maps to it through the register.
  • Ad reporting: location-level campaigns and location values in ad reports use it too.

The links on each listing belong on that list as well. Google Business Profile Links by Location shows how to put the key on every listing link so map clicks land on the right store.

The handoff problem

The most common break isn't inside any one tool. It's between them. A guest picks a store on the brand site, taps Order, and lands on the ordering site. Does the store they picked come with them? Or does the ordering site ask again, or quietly pick a default?

Test it. Choose a store on your brand site, follow the order button, and see what the ordering site shows. Then check that the analytics event on the ordering side carries the same key. If the choice resets, orders get credited to whichever store the guest picks second, or to the default, and store numbers drift without anyone noticing. Your Restaurant Website Is Not One Website covers the other handoffs on a typical restaurant site.

A five-question self-check

  1. Does every online order carry the location key?
  2. Does every reservation carry the key?
  3. Does each Google Business Profile store code equal the key?
  4. Does the POS export use the key, or map to it through the register?
  5. Does the store choice survive the handoff to the ordering site?

If any answer is no or don't know, start there. These are our checks from practice, not measured findings.

What you can report once it holds

Once the key is everywhere, a store report is a join instead of a reconciliation. Your own orders and marketplace orders side by side for each store, kept apart the way Your Own Orders vs Marketplace Orders recommends. Orders and revenue by store and channel, including marketplace payouts (Net Per Order by Channel). Loyalty members by the store that recruited them (The Loyalty Sign-Up Is Your Most Valuable Form). Holiday comparisons that line up store for store (Holiday Weeks Break Store Reports).

If you'd like help agreeing the key and checking where it breaks, book a data and tracking audit. To see what your site loads before a guest makes a choice, request a free privacy scan; we review each request within 48 hours.

Rawsoft provides technical implementation and analysis, not legal advice. Please confirm any regulatory interpretation with your counsel.

Get new research by email

New posts and Website Privacy Index findings, sent to your inbox. No spam, unsubscribe anytime.

We only use your email for this list. See our Privacy Policy.

About Rawsoft

Rawsoft is an Atlanta-based digital data agency specializing in analytics implementation, privacy and consent management, and media tracking for enterprise brands.

Add Rawsoft as a preferred source on Google

More from the blog

Analytics

Your Own Orders vs Marketplace Orders: The Guest Data You Never Get Back

A marketplace order and an order on your own site can be the same meal. Only one of them leaves you a guest you can market to.

November 2026Read

Media Tracking

Your Restaurant Website Is Not One Website

A restaurant site hands visitors to ordering, loyalty, gift card and catering vendors on different domains. What that does to tracking, attribution and privacy.

August 2026Read