Skip to content
All Resources
Retail Measurement 12 min read

Prepared by GSDSI Regulatory Content Team

Last updated

Editorial standardsTrust Center

Privacy-Safe Retail Measurement: Foot Traffic + Card Panels + CTV Attribution

Three signals answer three different questions. Foot traffic gives incidence, meaning who visited at cohort level inside POI polygons. Card panels give magnitude, meaning spend and basket composition in aggregate. CTV attribution gives lift against a control. Polygon quality is load-bearing, because weak geometry inflates all three joins at once.

Relationship disclosure: X-Mode and its successor Outlogic, InMarket, and Mobilewalla are referenced here as subjects of FTC consent orders finalized in 2024 and 2025. GSDSI has no supplier, partner, or reseller relationship with any of them.

How to use this article

Read the checklist here, then use the linked hub and product pages for procurement citations.

Retail measurement in 2026 runs on a three-signal stack: in-store foot traffic from mobility panels, card-spend panels from banking and payment aggregates, and CTV attribution from household exposure matched to downstream behavior. Each signal is operator-grade on a specific question, weak on others, and overlaps in ways teams under-model. Post-Apple ATT, privacy-safe-by-construction is the floor, not an optional upgrade. This guide wires the stack for retail media networks, CPG brands, and QSR operators using CTV/Smart TV ACR, global mobility, and cross-channel measurement. Pair with MRC standards diligence and IAB measurement framework expectations.

Retail teams that buy only one signal often discover gaps in QBR. Foot traffic without spend cannot value visits; card spend without visits cannot explain traffic drivers; CTV without outcomes measures reach theater. The productive architecture assigns each signal a primary KPI, documents overlap explicitly, and pre-registers holdout design before flights launch.

Foot Traffic: Incidence and Visit Proof

Mobility-sourced visits to POI polygons measure who visited at aggregated cohort level. Daily uniques inside store footprints, dwell rules, and sensitive-location exclusions define the metric, not raw ping counts. Radius geofences over-capture adjacent tenants; polygon upgrades routinely move visit estimates more than panel scaling in dense retail. Require DUAs by chain and DMA, not global device marketing totals.

Foot traffic supports store-level benchmarking, competitive conquest measurement, and OOH/CTV outcome joins. It does not directly observe transaction value or online conversion unless paired with other signals. Connect to why POI quality makes or breaks foot-traffic analytics before licensing production mobility.

Card Panels: Spend Magnitude and Basket Signal

Card-spend panels aggregate transaction signal from issuer and payment networks: category spend, ticket size, share shift, and promotional response at merchant or MCC level. They answer what the visit was worth and fill conversion detail foot traffic alone cannot see. Panel composition, merchant normalization, online/offline splits, and refund handling all affect comparability. Card data rarely resolves to individual stores without merchant-ID alignment; foot traffic rarely resolves to dollars without card join.

CTV Attribution: Exposure-to-Outcome Lift

CTV attribution joins household exposure from ACR or ad logs to store visits or card spend in governed environments. Lift studies compare exposed versus control cohorts with pre-registered windows and aggregation floors. Frequency, creative, and content context live on the exposure side; visit and spend proof live on the outcome side: conflating them without join documentation invites false confidence.

For test design see CTV measurement test design and clean room joins when raw logs cannot export.

Where Signals Overlap and Diverge

Foot traffic and card panels correlate but do not coincide: browsers who do not buy, buyers who pay cash, and online pickup distort single-signal reads. CTV exposure may precede visits by days; card spend may lag visits by hours. Model overlap explicitly: use traffic for incidence trends, card for monetization, CTV for incrementality. Double-counting the same cohort as three independent proofs inflates executive confidence.

Privacy-Safe Governance for Retail Measurement

Minimum cohort sizes, sensitive-location exclusions, purpose limitation, and deletion SLAs apply upstream of reporting. FTC location orders made sensitive-place scrubbing baseline. Retail measurement that exports individual-level paths fails modern procurement: cohort aggregates and clean-room outputs are the shippable forms. See privacy-safe targeting and geo-panel audit 2026.

Pre-register pilot success metrics: polygon QA pass rate, DUAs inside footprints, card-merchant match rate, CTV household match rate, and lift thresholds with holdout construction documented before spend. Retail media matures when measurement appendix matches media appendix in the contract.

Agree the Metric Before the Campaign, Not at the Readout

Most disputes about retail measurement are not disagreements about data. They are disagreements about what was being measured, discovered once the numbers arrive. Visits, incremental visits, transactions, and incremental sales are four different questions, and a stakeholder expecting one will read a chart showing another as either a triumph or a failure depending on which they had in mind.

Settle four things in writing before launch: the metric, the comparison it is measured against, the window, and who signs off on the result. It takes very little time and removes the most common way a measurement program loses credibility, which is not an inaccurate number but a number answering a question nobody agreed to ask. Where two teams genuinely need different metrics, report both from the start rather than reframing one afterwards.

A Reconciliation Order for When the Three Signals Disagree

The quarterly meeting where foot traffic is up and card spend is flat is the normal case, not the exception, and the order in which you investigate it decides whether anyone learns anything. Run the mechanical explanations first, because they are cheap and they are usually right. Did the polygon set change during the period, through a geometry refresh, a new store batch, or a closed-location purge? Did panel composition shift by market? Did the card provider re-map merchant identifiers or move its online and offline boundary? Any of those moves the series without anything happening in the stores.

Only when the mechanical checks come back clean should you reach for behavioral explanations, and each one has a distinguishing test. A shift toward pickup shows up as visits with compressed dwell rather than as fewer visits. A ticket-size decline separates from a traffic decline when transaction counts hold while spend falls. Cash and out-of-panel cards depress the spend read without touching the visit read at all, so a divergence that appears in one market and not in its neighbors points at panel coverage rather than at shopper behavior.

Methodology changes deserve a rule of their own. When a comparison window crosses a vendor restatement or a backfill, the series on either side of that date is not comparable, and charting straight through it is how a measurement artifact becomes a strategy. Require published methodology-change dates from all three vendors as a contract deliverable, keep them on one shared calendar, and mark them on every chart that spans them.

Write the reconciliation order into the measurement appendix before the flight rather than after the result. The reason is not tidiness. When the sequence gets chosen after everyone has seen which signal flatters the program, the explanation that survives is the convenient one, and the same disagreement returns next quarter wearing a different story. See foot traffic versus credit card panels for which signal owns which question, and foot traffic panel sizing for whether the read is powered at all.

Frequently Asked Questions

What does each retail measurement signal answer?
Foot traffic: who visited. Card panels: spend magnitude and basket. CTV attribution: whether media changed visit or spend versus control. Use all three for different questions, not as redundant proof.
Why do POI polygons matter for retail measurement?
Visit counts, CTV outcome joins, and competitive benchmarks all anchor on store geometry. Weak polygons inflate visits and attribution lift in dense retail corridors.
Can card panels replace foot traffic?
No. Card data sees spend, not all visits: cash, non-panel cards, and browsers who do not purchase are invisible. Traffic and card are complementary.
How should CTV lift studies be designed?
Pre-register exposure definition, outcome definition, control construction, attribution window, and aggregation floors. Document household-to-outcome match rates at each join hop.
What privacy controls are required in 2026?
Cohort aggregation floors, sensitive-location exclusions, documented consent chains, deletion SLAs, and purpose limitation aligned to activation and measurement use cases.
Why do retail measurement readouts get disputed?
Usually because the metric was never agreed. Visits, incremental visits, transactions, and incremental sales answer different questions. Settle the metric, its comparison, the window, and sign-off before launch, and report both where two teams need different ones.

✓ Opt-Out Request Honored via Global Privacy Control