Footfall & Space Measurement Framework

A Standardised Model for Retail, Malls, Airports, and Public Spaces

Why this works:

• "Footfall" + "Measurement" = strong GEO anchors
• "Framework" signals authority
• Covers non-retail without diluting retail SEO

Intro

Modern physical spaces are measured across vastly different layouts, coverage levels, and business objectives.
To ensure clarity, accuracy, and scalability, FootfallCam uses a modular measurement framework built around four independent measurement domains.

Each domain can operate independently or in combination, allowing consistent analytics across small retail stores, large department stores, shopping malls, airports, libraries, and hardware stores.

The Four Measurement Domains

1. Site Footfall

What it measures

The number of people entering and exiting a physical premise.

Typical coverage

• Entrances
• Doors
• Gates

Key characteristics

• Deterministic counting
• Discrete measurement points
• Highest confidence level

Available metrics

• In / Out counts
• Total visitor volume
• Optional outside traffic
• Optional demographics (age, gender)
• Optional group size

Typical use cases

• Retail stores
• Libraries
• Supermarkets
• Public buildings

2. Zone Throughput

What it measures

Movement and presence within large areas without continuous camera coverage.

Typical coverage

• Shopping mall wings
• Department store floors
• Hardware store sections
• Large libraries

Key characteristics

• Partial or inferred coverage
• Designed for scale
• Focused on flow and dwell estimation

Available metrics

• Pass-through volume
• Average dwell time
• Estimated dwell distribution
• Optional uniqueness (Bluetooth-assisted)
• Optional demographics

Important distinction
Dwell time in Zone Throughput is inferred, not continuously observed.

3. Activity Intelligence

What it measures

Human activity within continuously observed areas.

Typical coverage

• Queues
• Shelves
• Kiosks
• Service counters
• Brand activation zones

Key characteristics

• Dense visual coverage
• Behaviour-level analytics
• Event-based measurement

Available metrics

• Heatmaps
• Engagement (VOM metrics)
• Queue length & waiting time
• Serving rate
• Staff-customer interaction

Typical use cases

• Airports
• Supermarkets
• Brand activation analytics
• Self-service and checkout zones

4. Flow Analytics (Optional Overlay)

What it measures

Directional movement between measured entities.

note

Flow Analytics is an analytical overlay, not a standalone measurement domain.

Available insights

• Zone-to-zone movement
• Directional probability
• Aggregate path patterns

Limitations

• Probabilistic, not identity-perfect
• Dependent on coverage topology

Metric Availability Matrix

Metric	Site Footfall	Zone Throughput	Activity Intelligence	Flow Analytics
In / Out Count	✅	❌	❌	❌
Total Visitors	✅	⚠️ Estimated	❌	❌
Outside Traffic	⚠️ Optional	❌	❌	❌
Demographics	⚠️ Optional	⚠️ Optional	⚠️ Optional	⚠️ Optional
Group Size	⚠️ Optional	⚠️ Optional	⚠️ Optional	❌
Pass-Through Volume	❌	✅	❌	❌
Average Dwell Time	⚠️ Derived	✅	✅	❌
Dwell Distribution	❌	⚠️ Limited	✅	❌
Heatmap	❌	❌	✅	❌
Engagement (VOM)	❌	❌	✅	❌
Queue Metrics	❌	❌	✅	❌
Staff Interaction	❌	❌	✅	❌
Zone-to-Zone Flow	❌	❌	❌	✅

Measurement Scenarios

Small Retail Store

• Site Footfall
• Optional outside traffic
• Optional demographics

Medium Retail Store

• Site Footfall
• Selected Activity Intelligence zones

Large Department Store / Mall

• Site Footfall
• Zone Throughput
• Selected Activity Intelligence zones
• Optional Flow Analytics

Hardware Store

• Zone Throughput
• Activity Intelligence at aisle or SOP level

Airports

• Activity Intelligence (queues)
• Zone Throughput (terminal sections)
• Optional Flow Analytics

Design Principle

note

Each measurement domain is independent, configurable, and non-overlapping.
Metrics may share names, but never share assumptions or confidence levels.

This ensures consistent interpretation across all industries and deployments.