Commissioned Research
Top 10 Best People Counting Software of 2026

GITNUXSOFTWARE REVIEW

Facilities & Property Services

Top 10 Best People Counting Software of 2026

Top 10 people counting software tools compared for retail, campuses, and events, with notes on features and deployment options.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

People counting software turns sensor streams into footfall and occupancy metrics for retail operations, venue capacity, and security analytics. This comparison frames the decision tradeoffs around data accuracy, analytics depth, and integration paths like APIs and automation for deployments that need consistent configuration and audit-grade reporting.

FootFallCam is the best choice for retail and venue teams that need real-time occupancy with zone and direction counts, since its edge-based sensing supports live line-crossing without relying on heavy post-processing, while Terabee fits teams that want zone-mapped occupancy delivered via APIs and webhooks into their workflows.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

FootFallCam

Edge-based people counting with direction-aware line-crossing supports real-time occupancy without relying on post-processing.

Best for: Fits when retail and venue teams need real-time occupancy and zone-level counts across multiple sites.

2

Genetec

Editor pick

Unified management and governance for counting analytics within Genetec’s video and alarm workflows, including role-based operational controls.

Best for: Fits when venue and retail teams need people counting integrated into an existing Genetec video and security operating model.

3

RetailNext

Editor pick

Exception-style reporting tied to mapped store zones for occupancy changes and visitor flow anomalies.

Best for: Fits when retail teams need zone-level occupancy reporting, staff filtering, and API export for store analytics workflows.

Comparison Table

1
FootFallCamBest overall
enterprise
9.4/10
Overall
2
enterprise
8.8/10
Overall
3
enterprise
8.6/10
Overall
4
vertical specialist
8.3/10
Overall
5
enterprise
8.2/10
Overall
6
vertical specialist
7.9/10
Overall
7
enterprise
7.6/10
Overall
8
vertical specialist
7.0/10
Overall
9
6.8/10
Overall
10
enterprise
6.6/10
Overall
#1

FootFallCam

enterprise

3D people counting sensors and analytics dashboard for retail footfall measurement.

9.4/10
Overall
Features9.4/10
Ease of Use9.3/10
Value9.5/10
Standout feature

Edge-based people counting with direction-aware line-crossing supports real-time occupancy without relying on post-processing.

FootFallCam uses overhead and edge-based sensing to produce people counts by zone and direction rather than only aggregated totals. Core capabilities include line-crossing detection for entry and exit, real-time occupancy reporting, and historical trend views for peak-hour and dwell-time style analysis.

The system supports multi-site aggregation and configuration of staff exclusion rules for more meaningful venue analytics. Integration is delivered through an API and event-style exports to feed external reporting and operational dashboards.

Pros
  • +Zone and direction counting works for occupancy and throughput reporting
  • +Real-time occupancy feeds support operational decision windows
  • +Staff exclusion filtering reduces counts from authorized personnel
  • +Multi-site aggregation supports centralized monitoring across locations
Cons
  • –Calibration drift can increase variance and needs periodic attention
  • –Webhooks and API workflows can require developer involvement
  • –Zone mapping can take multiple configuration iterations per camera
  • –Some advanced visitor journey views need consistent sensor placement
Use scenarios
  • Retail operations teams

    Measure entrance entry and exit flows

    Clear entrance activity visibility

  • Retailers and venue operators

    Count visitors without smartphone participation

    Sensor-based visitor counts

Show 2 more scenarios
  • Venue and commercial site managers

    Monitor queue passage over time

    Time-based counts for routes

    Managers count movement through queue areas and passageways to review traffic patterns across operating windows.

  • Facility and venue operations teams

    Handle crowding with occupancy threshold alerts

    Earlier visibility into crowding

    Teams monitor occupancy in defined areas and trigger threshold alerts when spaces approach crowding limits.

Best for: Fits when retail and venue teams need real-time occupancy and zone-level counts across multiple sites.

#2

Genetec

enterprise

Security Center platform with built-in people counting analytics modules.

8.8/10
Overall
Features8.8/10
Ease of Use8.9/10
Value8.7/10
Standout feature

Unified management and governance for counting analytics within Genetec’s video and alarm workflows, including role-based operational controls.

Genetec fits retail and venue teams that already operate a security and access-control stack and want people counting tied to the same unified management. It centers on camera-based analytics inside Genetec environments, with multi-zone counting, occupancy-style metrics, and reporting that can support operational reviews across locations.

Genetec also provides integration hooks for pulling counts into external systems and automations that align with existing workflows. The main differentiator is governance and system control for deployments that already standardize video, alarms, and role-based operations.

Pros
  • +Works inside a unified Genetec security deployment
  • +Supports multi-zone configuration for counting and occupancy reporting
  • +Provides integration interfaces for exporting counts to external systems
  • +Includes audit-style operational logging within managed video workflows
Cons
  • –People counting depends on camera analytics licensing and configuration
  • –Setup for zones and counting rules demands administrator attention
  • –External reporting customization can require developer-grade integration work
  • –Real-time workflows may be constrained by edge-to-dashboard data paths
Use scenarios
  • Enterprise security governance teams

    Manage people counting configuration by role

    Consistent administration across locations

  • Investigators and security officers

    Reconstruct crowd events from recordings

    Faster relevant footage review

Show 2 more scenarios
  • Access control and security teams

    Correlate entrances to badge reads

    Searchable access incident record

    Security teams review badge reads, door activity, alarms, and camera evidence in one investigation workflow tied to counts.

  • Physical security administrators

    Enforce access schedules by facility

    More consistent entry enforcement

    Administrators apply access rules, schedules, and door policies across facilities while people counting supports operational review.

Best for: Fits when venue and retail teams need people counting integrated into an existing Genetec video and security operating model.

#3

RetailNext

enterprise

Retail analytics platform combining people counting, shopper journey, and conversion analytics.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Exception-style reporting tied to mapped store zones for occupancy changes and visitor flow anomalies.

RetailNext focuses on retail-grade people counting with occupancy analytics and exception reporting tied to store zones. The product uses camera-based counting to generate real-time and historical footfall trends, and it supports multi-site aggregation for distributed retail teams.

RetailNext also provides workflow controls for filtering staff movement and segmenting visitors by mapped areas. Integration options include API access for exporting counts and events into external reporting and operational systems.

Pros
  • +Real-time store occupancy views with historical trend reporting by zone
  • +Staff exclusion filtering supports cleaner visitor counts for operational reviews
  • +Multi-site aggregation helps central teams compare locations in one dashboard
  • +API access supports event and count export for external reporting pipelines
Cons
  • –Zone mapping and exclusions need careful governance to avoid reporting drift
  • –Camera placement constraints can limit coverage for complex layouts
  • –Queue and dwell-style insights depend on sensor and configuration coverage
  • –Higher-volume deployments require tighter monitoring of data throughput and latency
Use scenarios
  • Retail analysts and data teams

    Feed footfall metrics into BI dashboards

    Less manual reconciliation

  • CPG field teams and auditors

    Document store execution with camera evidence

    Repeatable store evidence

Show 2 more scenarios
  • Retail operations and district teams

    Compare traffic and conversion trends

    Consistent location performance view

    Teams compare footfall, conversion, and performance patterns across stores and time periods using aggregated zone data.

  • Space-planning and store ops

    Validate layout changes using zone occupancy

    Evidence for layout adjustments

    Teams use dwell, movement, and queue patterns from zone occupancy to evaluate layout and customer flow decisions.

Best for: Fits when retail teams need zone-level occupancy reporting, staff filtering, and API export for store analytics workflows.

#4

Terabee

vertical specialist

LiDAR-based people counting sensors with cloud analytics for occupancy monitoring.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

API and webhook delivery for real-time occupancy metrics with configurable counting regions.

Terabee’s core value shows up when physical layout needs controlled counting regions and consistent visitor filtering, since zone configuration is the basis for usable totals. The system also supports operational monitoring with historical trend reporting that teams can review for peak hour analysis and capacity decisions. Multi-camera or multi-sensor setups benefit from consistent configuration so teams can compare aggregated volumes across areas.

Pros
  • +Zone-mapped counting aligned to floor plans and operational areas
  • +API and webhook integration for feeding occupancy metrics into other systems
  • +Historical reporting for peak hour analysis and trend comparisons
  • +Designed for sensor deployments with edge-to-cloud workflows
Cons
  • –Counting accuracy can require ongoing calibration drift checks
  • –Complex layouts can take more configuration time than single-zone installs
Use scenarios
  • Retail operations teams

    Monitor store occupancy and staff capacity

    Faster staffing decisions

  • Venue facilities managers

    Track audience flow between zones

    Better crowd management

Show 1 more scenario
  • Analytics engineers

    Send counts into data pipelines

    Unified analytics view

    API and webhook events support automated ingestion into reporting and alert systems.

Best for: Fits when venue teams need real-time occupancy data plus API delivery into operational workflows.

#5

Sensormatic IQ

enterprise

Retail intelligence platform including footfall counting, shopper analytics, and loss prevention.

8.2/10
Overall
Features8.2/10
Ease of Use8.3/10
Value8.1/10
Standout feature

Occupancy threshold alerting drives crowding notifications from zone-level metrics without manual polling.

Sensormatic IQ is designed around camera-based people counting with line-crossing detection and zone mapping so teams can define where visitors should be counted. It adds occupancy threshold alerting so reports can trigger operational attention when zones exceed configured limits. Multi-site aggregation supports historical trend reporting that helps identify peak-hour patterns and occupancy variance across locations.

Pros
  • +Configurable zone mapping supports counting rules by space and entrance
  • +Occupancy threshold alerting converts analytics into actionable operational triggers
  • +Multi-site aggregation supports consistent reporting across many locations
  • +API and webhook integration supports automated data delivery to other systems
Cons
  • –Accuracy can degrade with calibration drift after environmental changes
  • –Zone configuration and exception handling require governance discipline
  • –Real-time feeds depend on camera installation quality and coverage angles
  • –Advanced analytics often require tighter coordination with site managers
Use scenarios
  • Retail operations teams

    Trigger crowding alerts by store zone

    Faster responses to overcrowding

  • Analytics and BI teams

    Centralize people counts across sites

    Comparable traffic reporting

Show 2 more scenarios
  • Systems integration teams

    Push counts into external workflows

    Automated operational data flow

    API and webhook integration sends event-ready count and occupancy data to downstream tools.

  • Venue management teams

    Measure entry and exit flows

    Improved throughput planning

    Line-crossing detection supports tracking of arrivals and departures for capacity planning.

Best for: Fits when fixed-camera teams need occupancy monitoring plus automated API delivery to operations.

#6

DILAX

vertical specialist

Automatic passenger counting and people flow systems for public transit.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Occupancy-oriented real-time outputs with zone-mapped reporting for operational crowding decisions, not just totals.

DILAX is a people counting software built around camera-based counting and an occupancy-focused workflow for retail and venue teams. It supports zone mapping and produces real-time occupancy outputs that can feed internal dashboards and operational reporting. DILAX also provides an automation and integration surface through exported data and event-driven updates for downstream systems.

Pros
  • +Zone mapping enables tailored counts for entrances, aisles, and service areas
  • +Real-time occupancy outputs help teams react to crowding during operating hours
  • +Exported data supports integration with reporting stacks and BI tools
  • +Multi-site aggregation supports consolidated reporting across locations
Cons
  • –Accuracy depends on camera placement and ongoing calibration drift checks
  • –API and webhook coverage can require engineering work for complex event schemas
Use scenarios
  • Retail operations teams

    Monitor real-time occupancy by mapped zones

    Real-time zone occupancy visibility

  • Venue operations teams

    Feed live occupancy data into dashboards

    Dashboards reflect live counts

Show 2 more scenarios
  • Facilities and analytics teams

    Automate downstream reporting with exported events

    Automated downstream consumption

    Exports and automation surfaces send event updates so downstream systems can consume counts without manual handling.

  • Operations managers

    Review occupancy trends for store and venue planning

    Better operational planning inputs

    Occupancy-focused outputs support operational reporting that supports decisions about layouts and staffing needs.

Best for: Fits when multi-site teams need zone-specific occupancy reporting with integration through exports and event updates.

#7

Eurotech

enterprise

IoT gateways and people counting solutions integrated with the Everyware device platform.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Zone-mapped occupancy reporting with API event output for multi-site dashboards and real-time alerting workflows.

Eurotech delivers people counting through sensor and camera-based deployments that feed a cloud-hosted occupancy and footfall view. The system is designed around zone mapping for retail and venue layouts, which supports multi-entry reporting across spaces.

Pros
  • +Zone mapping supports consistent counts across complex retail layouts
  • +API surface supports real-time occupancy feed and downstream event routing
  • +PII stripping and anonymization support privacy-focused reporting workflows
  • +Edge-based processing reduces network dependency for counting accuracy
Cons
  • –Calibration drift can require periodic checks to control accuracy variance
  • –Queue and dwell analytics depend on sensor positioning discipline
Use scenarios
  • Retail operations teams

    Track people across mapped retail zones

    Zone-based traffic visibility

  • Venue operations teams

    Monitor occupancy across multiple entry points

    Multi-entry occupancy reporting

Show 2 more scenarios
  • IT and integration teams

    Push occupancy events to other systems

    Occupancy events in other tools

    An API layer sends occupancy events to downstream systems so other applications can react to live counts.

  • Privacy and compliance teams

    Reduce personal data in occupancy pipelines

    Anonymized occupancy data

    Governance controls support privacy workflows with data minimization through PII stripping and anonymization.

Best for: Fits when retail or venue teams need multi-zone people counting with API-driven occupancy events across multiple sites.

#8

Kepler Analytics

vertical specialist

Retail people counting and staff optimization platform using proprietary shelf sensors.

7.0/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.0/10
Standout feature

Real-time occupancy threshold alerting tied to configured zones, with webhook outputs for downstream automation.

Kepler Analytics turns camera views into zone-based counts and occupancy metrics that can be compared across sites in a single reporting area. The workflow centers on configuration of viewing angles, calibration behavior over time, and zone mapping so teams can define where people are counted. A cloud-hosted dashboard provides historical trends, peak hour analysis, and real-time occupancy feeds used for daily operations and reporting.

Pros
  • +Zone mapping and multi-site aggregation with consistent reporting views
  • +API webhook integration for pushing occupancy and counting events to other systems
  • +GDPR-focused anonymization with PII stripping for visitor privacy controls
  • +Real-time occupancy feed plus historical trend reporting for operations and KPIs
Cons
  • –Accuracy can degrade without disciplined calibration drift checks across locations
  • –Alerting requires careful zone selection to avoid threshold noise
Use scenarios
  • Store operations managers

    Occupancy threshold alerting for entry control

    Fewer overcrowding incidents during peaks

  • Analytics and BI teams

    Feed footfall metrics into data pipelines

    Unified reporting across systems

Show 1 more scenario
  • Multi-site retail analysts

    Peak hour analysis by location

    More accurate staffing schedules

    Historical trend reporting compares occupancy patterns across stores to plan staffing and promotions.

Best for: Fits when retail teams need zone-level occupancy reporting with automation via webhooks.

#9

Storetraffic

SMB

Footfall counting sensors and analytics dashboard for retail and mall environments.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Outbound callback delivery of count and occupancy events for custom processing in external systems.

Storetraffic is a people counting product geared toward retail and venue teams that need a camera-based footfall view across zones. It reports counts and occupancy metrics and supports operational workflows around store performance and in-store capacity.

Pros
  • +Zone mapping supports consistent counts across multiple camera angles
  • +Outbound callbacks simplify pushing live and historical metrics into internal dashboards
  • +Multi-site reporting supports aggregated review of locations and time windows
  • +Dedicated occupancy outputs help teams monitor capacity without manual math
Cons
  • –Setup requires careful camera framing so line crossing events match site layouts
  • –Real-time alerting workflows are limited compared with vendors that ship full threshold alert consoles
  • –Exports can require additional engineering to match analytics schemas used by enterprises
  • –Calibration drift handling is not as transparent as more operationally prescriptive competitors
Use scenarios
  • Store operations managers

    Monitor footfall by zone during shifts

    Better coverage and reduced bottlenecks

  • Retail analytics leaders

    Feed footfall into reporting dashboards

    Consistent reporting across locations

Show 2 more scenarios
  • Facility and venue capacity leads

    Track occupancy against capacity limits

    Lower risk of overcrowding

    Occupancy metrics support operational checks for safe throughput and space planning across zones.

  • Multi-site store planners

    Standardize zone layouts across locations

    Comparable zone performance metrics

    Zone configuration enables comparable counts and occupancy metrics across multiple stores with shared layouts.

Best for: Fits when retail teams want camera-based zone counts plus export and callbacks into existing BI and alert systems.

#10

Density

enterprise

Occupancy and people counting sensors for measuring space utilization in offices and venues.

6.6/10
Overall
Features6.6/10
Ease of Use6.5/10
Value6.7/10
Standout feature

API and automation-ready count exports that keep zone traffic metrics synchronized with external workflows.

Density counts people from camera feeds and turns zone-based traffic into a cloud dashboard for retail and venue operations. The workflow centers on mapping detection areas to business zones and producing live occupancy-style metrics with filtering for staff and known exceptions.

Pros
  • +Zone mapping and configuration tied directly to operational reporting needs
  • +API access supports automated count ingestion into downstream tools
  • +Staff exclusion filtering reduces false counts from scheduled presence
  • +Multi-site aggregation supports comparative reporting across locations
Cons
  • –Configuration changes require governance discipline to avoid inconsistent zone logic
  • –Camera placement constraints can limit accuracy when sightlines are obstructed
  • –Real-time feeds depend on stable edge capture and network throughput
  • –Cross-camera deduplication needs careful calibration across overlapping views
Use scenarios
  • Retail, venue, and facility operators

    Count entries exits and movement in zones

    Count data for operations

  • Workplace operations teams

    Validate desk reservations against occupancy

    Policies reflect actual usage

Show 2 more scenarios
  • Venue and event operations teams

    Monitor crowd density against capacity thresholds

    Live capacity issue awareness

    Venue operators compare live zone counts with configured capacity thresholds during events for crowding visibility.

  • Facilities and workplace analytics

    Report recurring utilization across space types

    Consistent utilization insights

    Facilities teams track desk, room, floor, and workspace usage over reporting periods to identify peak demand and underuse.

Best for: Fits when retail or venue teams need zone-based counts, automation via API, and centralized multi-site reporting.

Conclusion

After evaluating 10 people counting software, FootFallCam stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
FootFallCam

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About People Counting Software

Which tools support API or webhook delivery for people-count events?
Sensormatic IQ supports API and webhook delivery for pushing entry, exit, and occupancy metrics into downstream workflows. Kepler Analytics also provides API webhook integrations for zone-based occupancy reporting. Terabee centers integrations on API and webhook delivery for real-time occupancy metrics.
How does zone mapping change what teams can report compared with whole-store totals?
FootFallCam produces zone-level counts with direction-aware line-crossing so entry and exit can be separated by configured regions. RetailNext ties exception reporting to mapped store zones so occupancy changes can be traced to specific areas. Density turns mapped detection areas into live occupancy-style metrics instead of relying only on aggregate counts.
When should occupancy threshold alerting be used, and which products implement it?
Sensormatic IQ uses occupancy threshold alerting from zone-level metrics to flag crowding risk without manual polling. Kepler Analytics provides real-time occupancy threshold alerting tied to configured zones with event-style outputs. Eurotech emphasizes API-driven occupancy events intended for alerting workflows across multi-zone deployments.
What breaks if staff exclusion filtering or governance controls are missing?
FootFallCam supports staff exclusion rules so venue analytics reflect customer movement rather than staff circulation. Density includes staff filtering and exception handling tied to detection zones, and missing rules can skew occupancy and peak-hour analysis. Genetec provides role-based operational controls, and without RBAC-style governance, configuration changes can become harder to audit across locations.
How do multi-site aggregation and reporting differ across the top options?
Sensormatic IQ supports multi-site aggregation so teams compare traffic and occupancy across locations in one view. Kepler Analytics provides a cloud dashboard for multi-site aggregation and trend reporting. Storetraffic supports zone configuration and multi-location reporting to standardize layouts across sites.
Which tools are better suited for venue teams that need real-time occupancy visibility?
Terabee targets venues with real-time occupancy visibility and configurable counting regions. FootFallCam provides real-time occupancy reporting using line-crossing detection with direction. DILAX focuses on occupancy-oriented real-time outputs tied to zone-mapped reporting for operational crowding decisions.
Which products emphasize edge-based processing rather than relying only on cloud processing?
Terabee is described as edge-ready through sensor-first deployments that pair hardware with a configurable cloud dashboard. FootFallCam uses edge-based sensing with overhead capture to deliver zone and direction counts for real-time occupancy. FootFallCam also prioritizes direction-aware line-crossing to reduce dependency on later post-processing.
How do privacy controls like PII stripping and anonymization show up in real deployments?
Kepler Analytics emphasizes GDPR-aligned anonymization and PII stripping as part of its data handling approach. Eurotech focuses on data minimization, including PII stripping and anonymization where compliance workflows require it. Genetec integrates people counting into unified video and alarm management, which shifts privacy handling into the existing operational governance model.
How should teams plan data migration when moving from one counting system to another?
RetailNext exports API-access counts and events, which helps map existing zone concepts into external reporting systems during migration. Density offers API and automation hooks designed to keep zone traffic metrics synchronized with downstream workflows, which reduces gaps when replacing manual exports. Storetraffic provides outbound callbacks for count and occupancy events, which supports rehydrating historical pipelines by aligning event payloads to the new system.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right People Counting Software

Options differ most in how reliably the system delivers correct counts over your actual layouts and lighting, and how much control you get over calibration, zones, and edge cases like occlusions. Our focus is on Calibration controls, Counting zones, and Auditability, because these determine whether numbers stay consistent after setup changes.

Calibration controls for your camera setup

Why it matters

Calibration controls matter because people counting quickly drifts when placement, zoom, or lighting changes. Good controls let us tune without rebuilding everything and keep counts stable.

How to check

In a demo, ask to see how the system runs a calibration or setup step, then try changing camera position parameters (or simulate with a sample) and rerun calibration. Check whether it provides acceptance guidance (e.g., pass/fail visuals) and how counts change before/after.

Counting zones and entry/exit rules

Why it matters

Counting zones and entry/exit rules determine which movements count and which are ignored. When zones are too rigid, the same location produces different results across time of day or crowd patterns.

How to check

Request a walkthrough where you define zones on an example floor plan or video still, then set how counts map to entry vs exit. Ask the demo user to test at least two tricky scenarios (a person partially blocked; someone walking near the boundary).

Accuracy verification with sample review

Why it matters

Accuracy verification matters because we need confidence, not just a live number. A system that supports repeatable verification helps us confirm counts match observed ground truth.

How to check

Ask for a way to import or capture a short sample clip and produce count results alongside review tools. Confirm whether it shows per-frame or event-level review (for example, flags when detections are uncertain) so we can validate the logic.

Handling of overlaps and queued movement

Why it matters

Overlaps and queued movement break naive detectors and create double-counts or missed counts. If event handling is limited, reports may look stable while being wrong at peak congestion.

How to check

On the demo, look for a test location that includes slow groups or side-by-side movement. Ask how the system prevents double-counting when paths intersect and what it reports when people are occluded.

Export formats and data model consistency

Why it matters

Export formats and a consistent data model matter because counts must feed reporting and automation without translation errors. If fields shift between views, we spend time reconciling instead of using data.

How to check

In a demo, request exports for raw events and aggregated counts, then compare column names and timestamps across two different views (live vs report). Also ask what identifiers persist for zones and how they appear in exports.

Audit log and RBAC for changes

Why it matters

Auditability and RBAC matter because zone edits and calibration changes directly affect counts. If we cannot track who changed what and when, trust erodes quickly.

How to check

Ask to see an audit log view showing configuration changes tied to user actions. Confirm that role-based permissions prevent non-admin accounts from editing zones or calibration and that change history remains accessible after updates.

Red flags

  • Counts change a lot after minor lighting or camera adjustments with no repeatable calibration workflow
  • Zone boundaries don’t support real movement patterns, causing visible boundary double-counts
  • Exports lack consistent identifiers or timestamps, forcing manual reconciliation later

Fit by situation

  • If we have multiple entrances with different movement directions, prioritize Counting zones and entry/exit rules.
  • If we expect camera tweaks or seasonal lighting changes, prioritize Calibration controls for your camera setup.
  • If our team needs traceable edits for reporting sign-off, prioritize Audit log and RBAC for changes.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.