Commissioned Research
Top 10 Best People Count Software of 2026

GITNUXSOFTWARE REVIEW

Facilities & Property Services

Top 10 Best People Count Software of 2026

Compare people count software options for retail, with editorial notes on Density and Camlytics, plus key tradeoffs for buyers.

21 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

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe 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 count software turns camera or sensor events into occupancy and foot-traffic metrics through configured detection zones, counting logic, and reporting schemas. This comparison helps operators weigh integration fit, API and automation options, and deployment tradeoffs between video-based analytics and sensor or thermal counting systems.

Density is the best pick for multi-site workplace teams that need a camera-to-API pipeline for occupancy analytics because it delivers count events for external systems like heatmap generation while keeping governed dashboard access, whereas Camlytics is a strong alternative for SMB teams that want API-driven occupancy logic since it’s built for event-style integration beyond dashboard-only reporting.

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

Density

People counter API delivery of count events for external systems doing occupancy heatmap generation.

Best for: Fits when multi-site teams need a camera-to-API pipeline for occupancy analytics and governed dashboard access.

2

Camlytics

Editor pick

People counter API delivers counted events for programmatic occupancy logic beyond dashboard-only use.

Best for: Fits when teams need API-driven occupancy analytics with multi-site reporting and rule tuning.

3

Placer.ai

Editor pick

Venue-level footfall and visit analytics with historical benchmarking that work without RTSP video feed ingestion.

Best for: Fits when aggregated store visits and occupancy trends matter more than real-time line counting and alerts.

Comparison Table

1
DensityBest overall
enterprise
9.3/10
Overall
2
8.8/10
Overall
3
enterprise
8.7/10
Overall
4
8.4/10
Overall
5
vertical specialist
8.2/10
Overall
6
7.8/10
Overall
7
7.6/10
Overall
8
7.1/10
Overall
9
enterprise
6.9/10
Overall
10
vertical specialist
6.7/10
Overall
#1

Density

enterprise

Occupancy and people count software for workplaces, buildings, and shared spaces.

9.3/10
Overall
Features9.0/10
Ease of Use9.5/10
Value9.5/10
Standout feature

People counter API delivery of count events for external systems doing occupancy heatmap generation.

Density provides people counting for retail and commercial spaces using computer-vision counting and a browser-based operations view. It focuses on turning camera feeds into actionable occupancy metrics with zone-based reporting, historical exports, and event summaries tied to counting lines.

Administration centers on configuration control per site and role-based access to dashboards and settings. Automation support centers on a people counter API and scheduled report delivery workflows for downstream occupancy analytics.

Pros
  • +People counter API for integrating counts into occupancy analytics pipelines
  • +Zone-based counting configuration supports multi-area reporting
  • +Historical trend export supports auditing and capacity review workflows
  • +Role-based access controls limit who can change counting settings
Cons
  • –Counting accuracy can drop when camera placement or lighting is inconsistent
  • –Requires careful zone and line configuration per camera to avoid misattribution
Use scenarios
  • Retail and venue operators

    Count entries and movement through zones

    Traffic monitoring and occupancy metrics

  • Venue and event operations teams

    Monitor zoned occupancy during live events

    Capacity risk visibility

Show 2 more scenarios
  • Space planners and real estate teams

    Assess allocation ratios using maps

    Move plans with evidence

    Planners use mapped layouts and allocation context to evaluate workspace changes informed by people count software outputs.

  • Facilities and office administrators

    Manage meeting room capacity with occupancy

    Better availability decisions

    Teams use occupancy signals from people counting to support review of room usage, release rules, and capacity decisions.

Best for: Fits when multi-site teams need a camera-to-API pipeline for occupancy analytics and governed dashboard access.

#2

Camlytics

SMB

Video analytics software with people counting, line crossing, and occupancy features.

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

People counter API delivers counted events for programmatic occupancy logic beyond dashboard-only use.

Camlytics is positioned for deployments where edge devices or camera-based counters need consistent zone logic and alerting behavior across locations. The people counter API enables integration with occupancy analytics, so applications can pull near real-time counts and occupancy states for signage, reporting, or workflow triggers. Configuration includes staff exclusion filtering to separate employee movement from shopper footfall. Multi-site aggregation helps consolidate peak hour benchmarking across sites into a single reporting view.

A key tradeoff is that higher-quality line crossing detection and zone-based counting depends on upfront calibration and ongoing drift management after installation. Camlytics fits teams that already standardize sensor placement and want automated ingestion plus exportable historical trend data rather than manual reporting.

Pros
  • +People counter API supports event-driven occupancy analytics integration
  • +Multi-site aggregation consolidates counts for cross-location reporting
  • +Staff exclusion filtering reduces employee-related miscounts
  • +Historical trend export supports recurring peak hour benchmarking
Cons
  • –Zone and threshold tuning requires disciplined calibration
  • –Operational analytics depth can lag specialized enterprise platforms
  • –Integration outcomes depend on consistent sensor placement
  • –Audit-grade governance features are limited versus access-control incumbents
Use scenarios
  • Retail operations analysts

    Consolidate occupancy trends across locations

    Earlier detection of underperforming stores

  • Security and access engineering

    Trigger occupancy-based rules in systems

    Fewer manual exception checks

Show 2 more scenarios
  • Store managers

    Reduce staff-driven counting noise

    Cleaner shopper KPIs

    Staff exclusion filtering limits employee movement impact on shopper footfall metrics.

  • BI and data engineering teams

    Export historical trends for dashboards

    Consistent reporting across teams

    Historical trend export enables refreshable reporting pipelines and comparisons over time.

Best for: Fits when teams need API-driven occupancy analytics with multi-site reporting and rule tuning.

#3

Placer.ai

enterprise

Location analytics platform delivering foot traffic and visitor counting data for retail and commercial real estate.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Venue-level footfall and visit analytics with historical benchmarking that work without RTSP video feed ingestion.

Placer.ai is a footfall and location intelligence service that turns device-level movement signals into people counts by venue and time window. It supports occupancy analytics workflows for retail and multi-site operators, including zone-based views such as store visits, dwell-like patterns, and visit frequency trends.

Placer.ai is distinct for its measurement approach that focuses on aggregated counts and historical benchmarking rather than requiring a dedicated RTSP video ingestion pipeline. People count outputs plug into decisioning via exports and integrations that fit reporting and analytics automation needs.

Pros
  • +Aggregated footfall and visit metrics support multi-site occupancy analytics reporting
  • +Historical trend reporting supports peak hour benchmarking for retail and venues
  • +Measurement outputs reduce dependency on line crossing camera setups
  • +Exports and analytics workflows fit automated reporting pipelines
Cons
  • –Zone-level granularity depends on venue boundaries and reference geofences
  • –Real-time bidirectional counting and queue length monitoring need different tooling
  • –Limited fit for workflows that require on-premise processing and edge appliances
  • –Staff exclusion filtering is not designed around staff IDs or biometric signals
Use scenarios
  • Transportation and GIS teams

    Use traffic time series without installs

    Expanded historical perspective

  • Venue and event planning teams

    Estimate attendance in defined zones

    Evidence-backed attendance estimates

Show 2 more scenarios
  • Retail operations and analytics teams

    Benchmark visit trends across stores

    Consistent multi-location comparisons

    Teams compare visit trends across stores, regions, and brands using people count outputs and historical benchmarking.

  • Digital and out-of-home planners

    Plan proximity audiences by location

    Location-informed KPI tracking

    Marketers use visitation benchmarks and location footprints from people count software to plan and evaluate campaigns.

Best for: Fits when aggregated store visits and occupancy trends matter more than real-time line counting and alerts.

#4

Axis Communications

enterprise

Network camera vendor offering AXIS People Counter analytics embedded in IP cameras and VMS.

8.4/10
Overall
Features8.4/10
Ease of Use8.4/10
Value8.4/10
Standout feature

Edge analytics configuration inside Axis video workflows, enabling counting near the PoE camera and tighter control of capture conditions.

Axis Communications delivers people counting through its edge-focused video analytics pipeline and camera-centric deployments. The offering centers on RTSP video feed ingestion into Axis analytics software and on configuring counting lines and zones in the camera-side workflow.

Pros
  • +Camera-side counting reduces latency versus server-only analytics
  • +Zone and line counting can separate ingress from egress flows
  • +Axis ecosystem integrations support fleet-wide analytics configuration
  • +RTSP video feed workflows fit standard access-control network layouts
Cons
  • –Extensibility for a custom people counter API is limited by module scope
  • –Counting quality depends on consistent camera placement and calibration
  • –Audit-grade governance features like RBAC and audit logs may require add-on design
  • –Dwell and advanced occupancy analytics coverage can be thin versus broader suites
Use scenarios
  • Security and facility operations

    Count people in defined areas

    Operational occupancy monitoring

  • Video monitoring teams

    Triage incidents using behavioral events

    Less footage hunting

Show 2 more scenarios
  • Transportation and site security teams

    Identify vehicles at the edge

    Automated vehicle identification

    Teams run camera edge workflows that recognize license plates to support site security processes alongside people counts.

  • Security investigators

    Investigate incidents with event metadata

    More targeted incident review

    Investigators use event metadata and associated recorded video to narrow review timelines tied to people count events.

Best for: Fits when a camera-first rollout needs line and zone people counting with centralized Axis management.

#5

Retail Sensing

vertical specialist

Retail people counting and shopper behavior analytics with traffic and conversion reporting.

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

Counting output is structured around configurable zones so occupancy analytics match each store layout.

Retail Sensing is a people count system designed around location-aware configuration, where counting zones and store layouts drive the resulting metrics. The software outputs operational counts that can be used for occupancy analytics and workflow triggers when combined with retailer-specific rules. Multi-site reporting helps centralized teams benchmark sites with consistent settings instead of rebuilding dashboards per store.

Pros
  • +Zone-based counting supports store-specific layouts for comparable metrics
  • +Event outputs align counts to operational reporting and occupancy analytics
  • +Multi-site aggregation reduces dashboard duplication across locations
  • +Configurable workflows support threshold alerting for monitored areas
Cons
  • –Accuracy is sensitive to sensor placement and calibration drift
  • –Deeper automation depends on integration work with existing data systems
  • –On-prem style deployments require operational oversight for hardware lifecycle
Use scenarios
  • Operations analytics teams

    Monitor zone occupancy across stores

    Faster operational decision cycles

  • Loss prevention managers

    Trigger alerts from monitored entrances

    Reduced review time

Show 2 more scenarios
  • Store managers

    Benchmark peak hour performance

    Clearer staffing guidance

    Store-level reporting uses the same zone definitions so peak hour comparisons stay consistent.

  • Systems integration teams

    Connect people count to data pipelines

    Unified reporting dataset

    People count results can be routed into downstream systems for standardized reporting and occupancy heatmap workflows.

Best for: Fits when retail teams need consistent zone-based counts across sites and planned reporting automation.

#6

Dahua Technology

enterprise

Surveillance manufacturer providing people counting and density analytics in cameras and NVR software.

7.8/10
Overall
Features7.8/10
Ease of Use7.8/10
Value7.8/10
Standout feature

Edge analytics tied to Dahua camera configuration enables zone-based people counting without a separate sensor compute stack.

Dahua Technology delivers people counting as part of its broader video surveillance and edge appliance ecosystem. People counts come from camera-side analytics that can send occupancy-related events to an integration layer via supported interfaces such as RTSP video feeds and device integrations.

Pros
  • +Camera-centric analytics reduce external system latency for live occupancy decisions.
  • +RTSP video feed compatibility supports common downstream viewing and evidence workflows.
  • +Edge-first deployment model fits PoE sensor network runs without constant cloud dependency.
  • +Zone-based counting modes support different line and region definitions per entrance.
Cons
  • –People count outputs depend on Dahua analytics configuration and camera placement.
  • –Cross-vendor integration requires more work than purpose-built people counter API products.
  • –Multi-site aggregation can be operationally complex without a consistent device management workflow.
  • –Calibration drift management is not automated end to end across large fleets.
Use scenarios
  • Retail operations and store managers

    Track entry exit for queues

    Improves staffing decisions

  • Facilities and building security teams

    Monitor ingress egress through lobbies

    Reduces overcrowding risk

Show 2 more scenarios
  • Security integrators and installers

    Deploy edge analytics with Dahua cameras

    Shortens integration cycles

    Camera-side people counting can integrate via supported interfaces for consistent site-wide reporting.

  • Operations analysts in multi-site retail

    Compare occupancy across locations

    Enables site performance tracking

    Centralized views of people counts enable cross-store reporting for entrance and exit performance.

Best for: Fits when retail or facility teams already use Dahua cameras and need on-premise occupancy monitoring with zone control.

#7

Sensormatic Solutions

enterprise

Johnson Controls brand offering IoT-based people counting, shopper analytics, and loss prevention systems.

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

Audit logging plus role-based access for store-wide people count administration and changes.

Sensormatic Solutions provides people counting through a store-focused sensor and analytics stack that fits retail deployments with edge appliances and managed workflows. Its reporting centers on occupancy and footfall style outputs for operations teams, with configuration paths for site-level grouping and historical trends export.

Pros
  • +Edge appliance deployment model reduces dependence on browser-only workflows
  • +Multi-site reporting supports centralized comparison across locations
  • +Counts can be integrated via a people counter API into other systems
  • +Audit log and RBAC support structured admin governance
Cons
  • –Zone-based counting and calibration adjustments can require specialized setup time
  • –API coverage is narrower than full occupancy analytics pipelines in some platforms
Use scenarios
  • Store operations managers

    Track customer flow by entrance

    Improved staffing alignment

  • Retail analytics teams

    Export historical occupancy trends

    Better demand forecasting

Show 2 more scenarios
  • IT administrators

    Govern multi-site user access

    Lower compliance risk

    Enables role-based access controls and audit logging for managed deployments.

  • Systems integrators

    Push counts to third-party tools

    Unified reporting workflows

    Uses people counter API and standard device connectivity to sync downstream systems.

Best for: Fits when retail operators need managed multi-site occupancy reporting with controlled access to counts and events.

#8

AxxonSoft Axxon One

enterprise

Video management software with people counting analytics for security and facility operations.

7.1/10
Overall
Features7.1/10
Ease of Use7.1/10
Value7.1/10
Standout feature

Counting rules can be managed within the same VMS environment as recording and access workflows.

AxxonSoft Axxon One is built around camera-centric data flows, so people counting stays aligned with recording, review, and evidence workflows instead of living as a separate analytics tool. Counting configurations can be tied to specific areas and directionality so ingress and egress accounting can be split by rule sets. For organizations with multiple sites, it can aggregate historical count outputs for repeatable peak-hour benchmarking across locations.

Pros
  • +People counting stays connected to recording, playback, and evidence review
  • +Zone and direction rules support separate ingress and egress counting
  • +RTSP ingestion keeps counting aligned with existing camera deployments
  • +Multi-site aggregation supports repeatable occupancy reporting
Cons
  • –Zone tuning and calibration require disciplined setup per camera angle
  • –People counting configuration depth can slow initial rollout for large fleets
  • –API-based automation depends on enabled integrations rather than basic exports
  • –Thin support for non-camera sensor inputs limits kiosk-style deployments
Use scenarios
  • Security operations teams

    Audit footfall against recorded events

    Faster validation of incidents

  • Retail analytics teams

    Normalize foot traffic across doors

    More consistent store-level trends

Show 2 more scenarios
  • Facilities and building managers

    Monitor occupancy by workspace zones

    Better space utilization decisions

    Configured area rules turn camera streams into zone-based occupancy monitoring for reports.

  • Multi-site security integrators

    Aggregate counts across campuses

    Uniform cross-site reporting

    Historical aggregation supports standardized peak-hour benchmarking across multiple locations.

Best for: Fits when teams need occupancy analytics tightly tied to existing VMS workflows.

#9

RetailNext

enterprise

In-store analytics platform combining sensor-based people counting with conversion and journey analytics.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

RetailNext’s configurable zone analytics ties camera counts to store-defined areas for targeted store KPI reporting.

RetailNext focuses on retail camera-based people counting with analytics centered on store operations rather than device-level telemetry.

Pros
  • +Zone-based counting supports area-level analytics across store layouts.
  • +Multi-location reporting helps compare trends between sites.
  • +API and export options support data piping into BI and workflows.
  • +Admin tooling supports managing data views across roles and locations.
Cons
  • –Camera-based deployment can require more site planning than some alternatives.
  • –Advanced counting accuracy depends on calibration and stable mounting.
  • –Video feed ingestion paths are less direct than RTSP-centric counting setups.
  • –Some occupancy and heatmap workflows require tighter configuration discipline.
Use scenarios
  • Retail auditors and field teams

    Document shelf conditions with evidence

    Repeatable store evidence

  • Retail merchandising teams

    Link shopper traffic to category performance

    Evidence for merchandising changes

Show 2 more scenarios
  • Loss prevention and retail security

    Review suspicious transactions with camera context

    More contextual exception reviews

    Teams review camera behavior alongside point-of-sale events to investigate potential incidents using people count data.

  • Retail operations and district teams

    Compare store traffic changes over time

    Consistent view of trends

    Retail teams compare footfall and performance trends across stores and periods using people count software exports.

Best for: Fits when retail teams need multi-site people counting analytics with API-based reporting pipelines.

#10

Irisys

vertical specialist

People counting and occupancy monitoring software built around thermal sensor hardware.

6.7/10
Overall
Features6.7/10
Ease of Use6.7/10
Value6.7/10
Standout feature

Edge appliance people counting with configurable zone-based layouts for separate ingress and egress visibility.

Irisys delivers people counting from edge sensors and turns those inputs into occupancy analytics for retail and site operations. The system supports zone-based counting so teams can separate entrances, aisles, and concourses for ingress and egress reporting.

Pros
  • +Zone-based counting supports entry and aisle level occupancy reporting
  • +Historical trend export supports peak hour benchmarking across time
  • +Edge appliance deployment reduces reliance on continuous cloud processing
  • +Ingress and egress balancing helps separate arrivals from departures
Cons
  • –RTSP video feed ingestion is not a first-class path compared with sensor-first deployments
  • –Live threshold alerting and alert routing controls appear limited versus enterprise access analytics suites
  • –Multi-site aggregation requires careful standardization of sensor placement rules
  • –Bidirectional counting accuracy can degrade with poor calibration drift management
Use scenarios
  • Retail operations managers

    Track store entry and exit patterns

    Improved staffing during peak hours

  • Property facility directors

    Benchmark footfall across multiple sites

    Consistent occupancy planning

Show 2 more scenarios
  • Security and compliance teams

    Monitor occupancy trends by zone

    Faster occupancy anomaly detection

    Edge sensor counts convert into zone-level occupancy analytics for operational oversight.

  • Analyst and planning teams

    Export hourly trends for forecasting

    More accurate demand forecasts

    Historical trend exports enable peak-hour benchmarking and forecasting inputs for planning workflows.

Best for: Fits when retailers need sensor-based occupancy analytics with zone reporting and trend exports.

Conclusion

After evaluating 10 people count software, Density 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
Density

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 Count Software

How do AxxonSoft Axxon One and Axis Communications handle RTSP video feed ingestion for people counting?
AxxonSoft Axxon One ingests RTSP camera streams and converts video detections into count events tied to its occupancy metrics workflow. Axis Communications also centers on RTSP video feed ingestion, but it routes counting line and zone configuration through its camera-side workflow inside the Axis edge analytics pipeline.
Which platforms support a people counter API for automation instead of dashboard-only reporting?
Camlytics exposes people count events through a people counter API designed for downstream dashboards, access control logic, and reporting pipelines. Density also supports API delivery through scheduled report workflows for external occupancy analytics systems, so count events can be used beyond in-app charts.
When does multi-site aggregation matter most, and how do Retail Sensing and Sensormatic Solutions implement it?
Multi-site aggregation matters when teams need comparable counts across store layouts and operational schedules. Retail Sensing emphasizes repeatable configuration for multi-site aggregation so zone-based outputs remain consistent across locations. Sensormatic Solutions provides managed multi-site rollouts with audit logging and role-based access, which supports controlled administration across sites.
What breaks if counting rules and zones are not standardized across locations in zone-based systems?
When zone definitions differ across sites, occupancy analytics become non-comparable because the count events reflect different line crossing rules and layouts. RetailNext’s configurable zone analytics tie camera counts to store-defined areas for targeted KPI reporting, so misaligned zone configuration shifts what each KPI represents. Irisys similarly relies on configurable zone-based layouts for separate ingress and egress visibility, so inconsistent zone mapping breaks ingress and egress balancing.
Which tools support staff exclusion filtering for reducing miscounts?
Camlytics includes staff exclusion filtering to reduce miscounts by tuning detection rules against known staff behavior patterns. AxxonSoft Axxon One provides configuration controls for zones and counting rules within the same VMS environment, but it does not foreground staff exclusion as the primary control mechanism in its core workflow.
How do Dahua Technology and Dahua-aligned deployments approach on-premise processing for occupancy monitoring?
Dahua Technology emphasizes on-premise processing patterns that fit retail and facility environments where local compute is preferred. In that model, edge analytics tied to Dahua camera configuration generate occupancy-related events and forward them to an integration layer using supported interfaces such as RTSP video feeds and device integrations.
How do Sensormatic Solutions and Density compare for admin controls and access governance?
Sensormatic Solutions targets store-wide people count administration with governance features such as audit logging and role-based access. Density offers role-based access to dashboards and settings through a browser-based operations view, so administrators can control configuration access without leaving the operational console.
When is bidirectional counting or ingress versus egress reporting required, and which tools support that split?
Ingress versus egress reporting is required when occupancy logic must balance queue entry with exit capacity. Irisys supports zone-based counting that separates entrances, aisles, and concourses for ingress and egress reporting. Dahua Technology also supports ingress and egress monitoring through edge analytics that send occupancy-related events to an integration layer for centralized dashboards.
How do AxxonSoft Axxon One and Placer.ai differ in what data they produce for occupancy analytics pipelines?
AxxonSoft Axxon One produces count events derived from camera detections inside its VMS-aligned workflow, so occupancy analytics are built from video-driven detections. Placer.ai focuses on aggregated store visit and historical benchmarking signals, so it avoids a dedicated RTSP video ingestion pipeline and feeds decisioning via exports and integrations tailored to reporting automation.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right People Count Software

In people count software, the real differences show up in how reliably the system matches your counting zones and how you operationalize the outputs. We focus on detection accuracy under your floor layout, plus how configuration, outputs, and automation behave when you change cameras or sites (integration depth and data model matter most when you must schedule and audit outputs).

Zone-accurate counts

Why it matters

Zone-accurate counts decide whether the numbers map to your operational reality (for example, sales areas vs. corridors). If counts drift by zone, occupancy and staffing decisions follow the wrong story.

How to check

Ask for a demo using a floor plan that looks like yours, with at least one narrow passage and one wider area. Then compare reported counts for a short labeled test session (people move through zones in a scripted way).

Configuration without rework

Why it matters

Setup configuration depth determines whether you can change layouts, camera positions, or monitored areas without long downtime. Inconsistent configuration steps also lead to repeated mistakes across sites.

How to check

Request a walkthrough of how they define monitored areas and thresholds. During the demo, change a zone boundary and confirm the time-to-save and whether recalibration steps are required.

Event outputs and export formats

Why it matters

People count software is most useful when outputs arrive in the formats your tools expect. Clear event outputs let you build automation around entry/exit moments or periodic totals.

How to check

Ask to see a sample export (CSV/JSON or an equivalent) and at least one event feed example. Confirm the timestamp semantics (local vs UTC), granularity (per interval vs per person event), and whether you can export historical windows immediately.

API and automation hooks

Why it matters

An API and automation hooks matter when counts must feed dashboards, ticketing, or analytics on a schedule. The main separation is whether automation supports provisioning and repeatable runs.

How to check

In the demo or documentation review, ask for an example workflow: create a site, define zones, and pull counts on a schedule. Verify authentication method, available endpoints or webhooks, and whether the API supports multi-site identifiers.

Admin controls and audit log

Why it matters

Admin controls and audit log help you manage changes to counting configuration and reduce disputes about when numbers changed. This is especially important across multiple sites and roles.

How to check

Ask how roles are handled (who can view counts vs change zones). Then request a sample audit log entry when a zone configuration is edited, including who changed it and what changed.

Red flags

  • Counts look consistent in the happy-path demo but break when you resize zones.
  • Exports are hard to interpret because timestamps or intervals are unclear.
  • Admin actions on zones aren’t traceable to a user with an audit record.

Fit by situation

  • If you run many distinct floor layouts across locations, prioritize Zone-accurate counts.
  • If you expect frequent layout tweaks or camera swaps, prioritize Configuration without rework.
  • If your team must route counts into dashboards and scheduled reports, prioritize API and automation hooks.
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.