A store-level dwell figure tells you a visit lasted, say, eleven minutes. It does not tell you that eight of those minutes went to a checkout queue and the promotional table you built the campaign around got twenty seconds. The average visit length is a real number, but it hides the thing an operator actually needs to fix, which is where inside the visit the time goes. Time spent per zone is the measure that opens the visit up and shows you.
This post defines zone-level dwell, separates it from the store-level dwell figure it is often confused with, sets out how to draw zones that mean something, and reads the patterns zone dwell produces. For typical dwell figures at the venue level, see dwell time benchmarks; this post is the sub-venue case and does not restate those numbers.
What is time spent per zone in a store?
Time spent per zone is the average dwell time within a defined area of a store or venue: a department, an aisle, a promotional table, a queue, or a mall atrium. Store-level dwell tells you how long a visit lasts; zone-level dwell tells you where inside that visit the time actually goes. That distinction is what makes it useful: a high-dwell zone that converts poorly may signal confusion or a queue, while a low-dwell zone you expected to work may be badly placed. Measuring it needs interior movement resolved to zones, not just a single entry count at the door.
The value is entirely in the granularity. A store total is one number for the whole visit; zone dwell is a number for each area the visit passed through, which is what lets you act on a specific fixture rather than guess at the whole floor.
Store dwell vs zone dwell: why the average hides where the time goes
Store-level dwell and zone-level dwell answer different questions, and the first cannot substitute for the second.
Store dwell is the length of the whole visit, entrance to exit. It is a useful health signal: rising store dwell often tracks with engagement, and it is the figure venue benchmarks are quoted in, which is why dwell time benchmarks works at the venue level. But it is an average over the entire floor, so it flattens the visit into one figure and loses the internal distribution completely.
Zone dwell keeps the distribution. It attributes time to each area, so two stores with an identical eleven-minute average visit can be read apart: one spread its time evenly across departments, the other lost half of it to a single slow checkout. The store total is the same. The diagnosis is opposite. That is the case for measuring dwell at the area level rather than settling for the average, and it is the reason zone dwell is a distinct metric rather than a finer slice of the same one.
Defining zones that mean something
Zone dwell is only as good as the zones you draw, and a badly drawn map produces numbers that are technically correct and practically useless. A zone should map to a decision you could actually make about that area. The recurring ones:
- Entrance and decompression. The stretch just inside the door where arriving shoppers slow down and adjust before they start shopping. Dwell here is expected to be low and transitional; treating it as a selling zone misreads it. The mechanics of this area are covered in the decompression zone.
- Departments and categories. The main selling areas, drawn to match how the floor is merchandised so dwell maps to a buying decision.
- Promotional areas. Feature tables, end caps, and seasonal displays, kept as their own zones so a campaign can be measured against the space it was given.
- Queues and service points. Checkouts, service desks, and fitting-room approaches, where dwell is a cost to manage rather than engagement to celebrate.
- Atriums and common areas. In a mall, the shared spaces between tenants, where dwell reflects the pull of the programming rather than any single store.
The principle across all of these is that a zone earns its place on the map only if a high or low reading would change what you do. A zone you would never act on is noise.
What zone dwell diagnoses
Zone dwell becomes actionable when you read it against what you expected the zone to do. The gap between expectation and reading is the diagnosis.
| Pattern | Likely cause | Action |
|---|---|---|
| High dwell, low conversion | Confusion, a queue, or a fixture that is hard to navigate | Check signage, staffing, and stock in the zone; time the queue directly |
| Low dwell in a zone you expected to work | Poor placement, weak sightline, or the wrong adjacency | Move the fixture into the main path or improve the approach to it |
| Rising dwell at a promotional table | The promotion is pulling attention as intended | Hold the placement and test replicating it in comparable stores |
| Long dwell at a checkout or service point | A queue is building | Add coverage at the peak hours the traffic curve shows |
The first row is the one that earns the metric its keep. High dwell reads as a good sign until you pair it with conversion, at which point a high-dwell, low-conversion zone flips from a success into a warning: people are stuck there, not engaged. A queue, a confusing fixture, or a stock gap all produce that signature, and none of them is visible in a store-level average. The dead-zone case is the mirror image: an area you invested in that shoppers pass without pausing, which usually means it sits off the main path or its sightline is weak. Zone dwell finds both, which a single visit-length number never can.
Zone dwell with layout and heatmaps
Zone dwell is one of a family of spatial measures, and it is most useful read alongside the other two rather than alone. A heatmap shows where shoppers are, as density; zone dwell shows how long they stay, as time. The two are different questions, and a zone can be dense but fast (a thoroughfare) or sparse but slow (a considered-purchase area), so store heatmaps and zone dwell together describe an area more completely than either does by itself.
Layout work is where they pay off. A fixture drawing long dwell but sitting off the main flow is a candidate to move; a high-traffic path with no dwell is a candidate to merchandise. That loop, reading spatial data and acting on the floor plan, is the subject of data-driven layout optimization. Zone dwell also feeds the movement view: knowing how long shoppers spend in each area is a natural extension of tracing shopper flow between zones, which maps the sequence of areas a visit passes through. Dwell adds the duration to that sequence.
Measuring zone-level dwell without cameras
Zone dwell has a harder measurement requirement than a store total. A door-line counter can give you entries and, with an exit count, an average visit length, but it cannot attribute time to areas inside the store, because it never sees the interior. Zone dwell needs interior movement resolved finely enough to say which zone a shopper was in and for how long.
Ariadne measures this with Hybrid Fusion, its patented camera-free method. Time-of-Flight depth sensing counts every visitor at the entrances, capturing geometry rather than images, while patented phone signal sensing follows movement through the interior, detecting the signals a phone emits even in airplane mode, and tracks that movement to about one-metre precision. The sensor streams both feeds to Ariadne, where Hybrid Fusion combines them into one trajectory per visit and computes counts, dwell, and paths. The streams carry no identifier: no MAC address, no device ID, no biometric data, and no camera is involved. Identifiers are stored only when a visitor explicitly opts in, which keeps the method GDPR-friendly and outside biometric territory.
Because the interior movement resolves to about one metre and fuses centrally into a trajectory per visit, dwell can be attributed to a zone: the trajectory shows how long the visit sat inside each area you defined, without a camera watching the floor and without capturing who anyone is. That is what lets an operator read a high-dwell, low-conversion aisle or a slow checkout as time in a place rather than as a face. For how the same layer supports zone-level movement analytics across the store, see zone-level movement analytics.
FAQ
What is the difference between store dwell and zone dwell?
Store dwell is the length of the whole visit, entrance to exit, expressed as one average. Zone dwell attributes that time to each area the visit passed through. Two visits with the same total length can spend their time completely differently across zones, and only zone dwell shows the distribution.
How do you define a zone for dwell measurement?
Draw a zone to match a decision you could act on: a department, a promotional table, a queue, an atrium, or the decompression area just inside the door. A zone earns its place on the map only if a high or low reading would change what you do about that area. Zones you would never act on add noise, not insight.
What does high dwell with low conversion mean?
It usually means shoppers are stuck rather than engaged. A queue, a confusing fixture, a stock gap, or hard-to-read signage can all hold people in a zone without producing sales. High dwell reads as positive until you pair it with conversion, at which point a high-dwell, low-conversion zone becomes a signal to investigate that specific area.
Do I need cameras to measure time spent per zone?
No. Ariadne counts with Hybrid Fusion: Time-of-Flight depth sensing plus patented phone signal sensing, never cameras. Time-of-Flight captures geometry rather than images, and signal sensing captures no MAC address by default, so the measurement involves no video, no faces, and no biometric data.
How is zone dwell different from a store heatmap?
A heatmap shows density, where shoppers are. Zone dwell shows duration, how long they stay. A zone can be dense but fast, such as a thoroughfare, or sparse but slow, such as a considered-purchase area. Read together the two describe an area more completely than either does alone.
