Reviewing Email and In-Store Activity: Attribution Limits for Dispensaries

A report that places email engagement beside in-store activity can help a team ask better questions. It cannot, by itself, show that an email caused a visit. Before discussing performance, agree on what the available records actually measure and which conclusions they can support.

This guide focuses on reporting design and data quality, not tactics for generating store visits.

Define the observation before choosing the metric

Distinguish a recorded transaction from a store visit, and an email click from an identified person. These observations describe different events. If the available system records transactions but not foot traffic, label the report accordingly rather than presenting transactions as a count of all visits.

• What event is recorded, and by which system?
• What date range and time zone does the report use?
• Does the measure count events or distinct records?
• Which records are excluded, missing or not matchable?
• Is the result observed, platform-attributed or estimated?

Check the data before interpreting a change

Review duplicate records, missing identifiers, delayed imports, inconsistent location names and changes to the source system. Confirm how refunds, cancellations and corrections are represented when financial totals are involved. Retain the report configuration so a later review can reproduce the same calculation.

Use only data the business is authorized to access for the reporting purpose. Prefer aggregate reporting when individual records are unnecessary, and keep customer-level information out of creative briefs and presentation examples.

Make attribution settings visible

If a platform assigns credit to a campaign, record the rule, time window and event used by that report. Describe how overlapping campaigns and other channels are handled, or state that the treatment is unknown. Two dashboards can show different results because they answer different questions.

A match between campaign and transaction records establishes an observed relationship under the selected method. It does not establish how much activity would have happened without the communication. Keep that distinction in the headline as well as the methodology note.

Review alternative explanations

Check whether operating hours, location coverage, reporting availability or other business conditions changed during the period. A comparison with the previous week may be useful context, but it should not be labeled causal evidence merely because the figures differ.

If the business needs an estimate of incremental impact, agree on a suitable evaluation design with a qualified analyst before claiming that result. Document the assumptions and limitations rather than attaching a stronger conclusion to an ordinary matchback report.

Finish with a decision-ready reporting note

A useful summary states the observation, calculation, coverage gaps and next question. For example: the report contains matched activity within a specified window; unmatched activity is excluded; additional impact has not been established. Avoid a headline that claims the campaign generated every matched event.

For related financial definitions, see email ROI measurement; for ongoing review context, see campaign and retention reporting. Hiigher’s account and campaign review can help identify reporting gaps and clarify what the current setup can support.