Skip to main content

🧭 Zones: drawing, naming & managing

Create zones to analyse traffic in specific areas of a camera's view. Zone filters update all widgets & heat maps for that area/time range

Leo avatar
Written by Leo
Updated over 5 months ago

What zones are

  • A zone is a polygon overlaid on the camera image.

  • Current UI supports 4-sided polygons. (Enterprise: custom polygons with unlimited sides.)

  • You can add unlimited zones per camera; we recommend ≤ 4 for clarity.

Create a zone

  1. Go to Cameras → [Camera] → Heatmap.

  2. Click Add zone.

  3. Click four corners on the image to draw the polygon.

  4. (Optional) Name the zone; otherwise it’s labelled by colour.

  5. Save.

Tip: Draw slightly inside walls/fixtures to avoid edge noise.

Edit or delete a zone

  • Open Heatmap → select the zone → adjust corner points → Save.

  • To remove, select the zone → Delete.

  • Changes take effect immediately for the current date filter.

Naming rules

  • Names are for your reference; use letters & numbers (no emojis/specials).

  • Keep names short and descriptive: Entrance, Promo Bay A, Till Queue.

Filtering & time alignment

  • Use the Zone picker to view zone-specific metrics.

  • Changing the date range recomputes all zone metrics and the heatmap to that same window.

  • Use All zones to return to full-frame analytics.

Calibration & placement tips

  • Mount cameras high and angled down to reduce occlusion.

  • Avoid mirrors/strong reflections and harsh backlighting.

  • After drawing a zone, do a quick walk test through it to confirm counts.

  • Keep zones non-overlapping where possible to simplify attribution.

“No data” state

  • Newly created cameras/zones show No data until movement occurs in view.

  • Ensure the device is online and the zone actually covers foot traffic.

  • Note: if a camera goes offline, counts aren’t backfilled for the gap.

Permissions

  • Admins & Managers can create, edit, and delete zones.

  • Viewers are read-only.

Troubleshooting

  • Zone saved but zero counts: widen the polygon or verify foot traffic with a walk test.

  • Numbers look inflated: check for reflections or people re-entering (counts are session-based, not unique individuals).

  • Cluttered visuals: reduce to ≤ 4 zones or hide unused ones via the picker.

Did this answer your question?