Store-level reporting a brand can act on
A campaign report summarising delivery and effect nationally tells a brand whether something happened. A store-level report tells it where, which is the difference between a document and a tool.
In a channel where activation is store by store, reporting at any coarser level discards most of the available information.
What should store-level delivery show?
Plays, uptime and days live, by store. Those three identify which stores delivered and which did not, which is the first question any analysis has to answer.
It also makes under-delivery visible at the level where it can be remedied, rather than as a national average that hides a concentrated problem.
What should store-level outcome show?
Category and item sales for test and comparison stores over the relevant periods. That is what allows an effect to be computed and, more usefully, to be computed for subsets.
Effect by store cluster is frequently more actionable than effect overall, because it identifies where the channel works for this brand rather than whether it works.
What does the combination enable?
Field prioritisation, store list refinement for the next flight, creative decisions by cluster, and an honest measurement that excludes non-compliant stores. Four uses, none available from a summary.
The store list refinement is the compounding one. Each flight's data improves the next flight's store selection, which is how a programme gets better rather than merely continuing.
What about confidentiality?
Store-level reporting identifies individual businesses, and suppression thresholds and aggregation exist for good reason. A brand receiving store-level data has obligations about how it is used and shared.
The reasonable position is that it is used operationally — field prioritisation, store selection, measurement — and not published or shared onward in identifiable form.
What should a brand not do with it?
Publish it, share it with third parties in identifiable form, or use it to make claims about individual stores. Store owners contribute data through the systems they run every day, and they are entitled to have it handled responsibly.
How should it be delivered?
As a file that joins to the brand's own data by store identifier, rather than as a presentation. A report designed to be read is a different artefact from one designed to be used.
Both have a place and the file is the one that enables the four uses above.
What if a network will not provide it?
That limits the channel to whatever a summary can support, which is verification of the total and nothing about where. It is a legitimate constraint to weigh against a network that will.
Frequently asked questions
Is store-level reporting standard?
It varies, and a network selling store-level activation should be able to report at the same level. An inability to do so is worth understanding before a buy.
What granularity of time is useful?
Daily or weekly, depending on the analysis. Monthly store-level data loses the ability to align delivery with specific events.
How should the data be joined?
By a consistent store identifier agreed in advance. Mismatched identifiers between the network's data and the brand's are the commonest practical obstacle.
Does this raise privacy questions?
It identifies businesses rather than individuals, which is a commercial confidentiality question rather than a personal data one in most cases. It still warrants care in handling and sharing.
Can it be shared with a retailer?
Store-level data about identified stores is sensitive, and sharing should follow the suppression and aggregation logic that applies to any store-identifiable information.
What about sharing with an agency?
Under the same handling terms as any confidential commercial data, and with the onward-sharing restrictions made explicit.
How much history is useful?
Enough to establish a baseline before the flight, which usually means several months. A report starting at the flight has no comparison.
Does this suit a small brand?
Especially, because a small brand's store set is manageable and the data is directly actionable by a small team.
What is the single most useful field?
Delivered plays by store. It answers whether the campaign ran where it was supposed to, which precedes every other question.
### How should the data be governed inside a brand?
With a stated internal use policy: operational use permitted, onward sharing in identifiable form not. Naming the permitted uses alongside the limits is what makes a policy workable rather than obstructive.
Store owners contribute this data through the systems they run every day, and a brand receiving it inherits an obligation to handle it responsibly.
One named owner and a short written rule covers it for most organisations, and it is considerably better than an assumption that everybody will be sensible.
How long should store-level data be retained?
As long as the measurement and reconciliation require, plus a margin, and then disposed of. Indefinite retention of identifiable commercial data accumulates risk with no corresponding benefit.
Can it be combined with the brand's own data?
Yes, and that combination is where most of its value sits. The join key should be agreed in advance, because mismatched store identifiers are the commonest practical obstacle.
What should be requested at the outset?
The file format, the identifier, the fields and the cadence, agreed before the first flight. Retrofitting a reporting specification after a campaign is considerably harder.
Can a summary substitute?
For verification of the total, yes. For field prioritisation, store selection or measurement, no. Industry standards work is discussed by bodies such as the IAB.