Foot traffic attribution helps marketers connect location-based advertising with real-world visits, but a credible result requires more than counting devices near a store. This practical checklist explains how to define visit rules, compare exposed and control groups, match identities in privacy-safe ways, report incrementality, and diagnose weak or misleading results.
Overview
Foot traffic attribution measures whether an advertising campaign is associated with visits to a physical location. It is commonly used for geofencing marketing, mobile location targeting, retail media measurement, and other forms of location based advertising.
The central question is not simply, “How many exposed people visited?” It is, “Did advertising produce more visits than would likely have occurred without the advertising?” That distinction separates basic store visit measurement from stronger incrementality analysis.
A useful measurement plan has five components:
- Exposure definition: Which impressions, devices, users, or consented audiences count as exposed?
- Visit definition: What signal qualifies as a store visit, and how are passersby excluded?
- Attribution window: How long after exposure can a visit reasonably be credited?
- Comparison method: What control or baseline shows what would have happened without the campaign?
- Privacy and quality controls: How are consent, data minimization, identity matching, and coverage limitations handled?
Before launching, document these choices in a measurement brief. If the rules change after results are visible, comparisons become difficult and the final report may overstate certainty. For background on vendor methodologies and coverage, see Foot Traffic Measurement Vendors Compared.
Checklist by scenario
For a single-store campaign
- Record the exact store address, entrance areas, operating hours, and any nearby locations that could create signal overlap.
- Define a visit using a dwell or presence rule rather than counting every location ping. The rule should help distinguish a likely visit from a brief pass-by.
- Set a primary attribution window, such as same day or several days after exposure, and document why it fits the buying journey.
- Separate campaign-exposed visitors from visitors who were eligible for the campaign but did not receive an impression.
- Report exposed visits, control visits, visit rate, estimated incremental visits, and the assumptions behind each figure.
A small location may need stricter validation because a radius can include sidewalks, neighboring businesses, roads, or adjacent properties. Review Geofencing Radius Best Practices when setting or revising the geographic boundary.
For multiple stores or franchises
- Maintain a clean location file with store IDs, addresses, coordinates, operating status, and campaign eligibility.
- Check for overlapping geofences and decide how visits will be assigned when locations are close together.
- Report results by store, market, region, and campaign total. A strong aggregate result can conceal weak performance at individual locations.
- Account for differences in opening hours, local competition, store format, and media availability when comparing locations.
- Use consistent naming and IDs across the ad platform, analytics system, point-of-sale data, and reporting dashboard.
Franchise teams can use a national-to-local structure, but measurement rules should remain consistent enough to support comparison. The guide to hyperlocal advertising for franchises provides additional planning context.
For geo-conquesting or competitor-location targeting
- Define the competitor locations and targeting period before launch.
- Use a neutral outcome location for measurement, such as the advertiser’s store or another agreed conversion point.
- Separate exposure near competitor sites from exposure near the advertiser’s own locations.
- Do not assume that a visit after competitor exposure was caused by the campaign. Compare it with an appropriate control group or pre-campaign baseline.
- Review the results by distance, market, and time since exposure rather than relying only on one blended total.
For examples of how this tactic can differ by industry, see Geo-Conquesting Examples by Industry.
For QR codes, promotions, or offline-to-online campaigns
- Assign a unique QR code or tracking parameter to each placement, location, creative, or distribution partner.
- Measure scans, landing-page sessions, offer activations, and store visits as separate stages.
- Use a redemption or transaction signal when available, but do not treat a scan as proof of a store visit.
- Record campaign dates and placement changes so unusual results can be investigated later.
QR codes can add a first-party signal to a location campaign, but they have their own gaps and duplication risks. Use the QR Code Attribution checklist alongside foot traffic measurement.
What to double-check
Exposure quality
Confirm that impressions were actually delivered to the intended audience and geography. Check for accidental inclusion of employees, residents, internal test devices, or locations outside the service area. If a proximity marketing SDK or measurement partner is involved, document which event fields are collected and how exposure is passed into the attribution workflow.
Visit quality
Ask how the system identifies a visit, filters repeated signals, handles multi-location visits, and treats stores inside malls or larger buildings. A visit count without these rules is difficult to interpret. Also check whether the measurement source has enough coverage in the target market to support a reliable comparison.
Identity and consent
Use only signals collected and matched under the applicable consent and data-use process. Prefer aggregated reporting, limited retention, and privacy-safe identity resolution over unnecessary person-level detail. Do not rebuild identifiable profiles merely to improve a campaign report. For implementation guidance, read Privacy-Safe Identity Resolution for Local Marketing and Location Permission Prompts Explained.
Incrementality
A simple exposed-versus-unexposed comparison can be misleading if the groups differ in intent, geography, device behavior, or store access. Where possible, use a holdout or matched control design. A basic calculation is:
Incremental visit rate = exposed visit rate − control visit rate
Estimated incremental visits can then be calculated by applying that difference to the relevant exposed audience. Label the result as an estimate, state the confidence limitations, and avoid presenting correlation as proven causation.
Reporting consistency
Keep the reporting template stable from campaign to campaign. At minimum, include campaign dates, eligible audience, delivered impressions, exposed audience, visit definition, attribution window, exposed visit rate, control visit rate, incremental visit rate, estimated incremental visits, and known coverage limitations. A dashboard should also show spend and cost per incremental visit when the required inputs are available. See Location Analytics Dashboard KPIs for a broader KPI framework.
Common mistakes
- Counting proximity as conversion: Being near a store is not the same as entering it. Use a visit rule designed to reduce pass-by activity.
- Changing the attribution window after launch: A longer window may increase attributed visits, but it also changes the meaning of the result.
- Using no control group: Seasonal demand, promotions, weather, local events, and existing brand intent can all affect visits.
- Combining unlike locations: A highway-adjacent store and a downtown store should not automatically share the same geographic or visit assumptions.
- Ignoring store operations: Closures, reduced hours, stock issues, renovations, and staffing changes can distort the outcome.
- Overinterpreting small samples: When audiences or visits are limited, present directional findings and explain the uncertainty.
- Mixing measurement sources without reconciliation: Ad-platform visits, vendor estimates, point-of-sale records, and first-party events may use different definitions. Compare methodology before combining totals.
- Collecting more identity data than necessary: Better measurement should not depend on unrestricted tracking. Apply consent management, purpose limitation, and data minimization throughout the workflow.
When to revisit
Use this checklist before every major campaign, seasonal planning cycle, market expansion, or measurement-tool change. Revisit the rules sooner when store locations move, operating hours change, a new ad channel is added, consent flows are updated, or a vendor changes its coverage or methodology.
At the end of each campaign, save the measurement brief with the final report. Record what changed from the previous cycle: geographic boundaries, visit logic, attribution window, control design, identity inputs, and data sources. This creates a useful audit trail and makes year-over-year comparisons more meaningful.
Before acting on a result, complete this final review:
- Can another analyst reproduce the exposed and control audience definitions?
- Are visits measured consistently across the locations being compared?
- Is the attribution window appropriate for the customer journey?
- Does the control group represent a reasonable no-advertising baseline?
- Are consent, retention, and identity-matching practices documented?
- Does the report distinguish observed visits from estimated incremental visits?
- Are operational or seasonal factors noted beside the result?
If the answer to each question is clear, the campaign report is more likely to support a sound budget decision. If not, fix the measurement design before optimizing the media. Reliable foot traffic attribution is built through repeatable definitions, transparent assumptions, and privacy-safe location analytics—not through a larger visit number alone.