Choosing a Place-Based Screen Location Without Relying on Dwell Time Alone

So you're picking a spot for a digital screen. Maybe it's a lobby, a checkout line, a waiting room. The first number everyone reaches for? Dwell time. How long people stand or sit near that spot. Makes sense on the surface. But here's the thing: dwell time alone can trick you. A bus stop has high dwell—people wait 10 minutes staring at their phones, not your ad. A fast-food counter has low dwell—30 seconds, but eyeballs locked on the menu board. Which one actually moves product? This article walks through what else matters: foot traffic quality, sight lines, audience intent, and environmental noise. We'll show you a framework that goes beyond the stopwatch.

Why dwelling on dwell time is hurting your network

The oversimplification of a single metric

Dwell time feels safe. You stand in a lobby, watch people linger for ninety seconds, and think: this spot works. But that number is a lie dressed up as data. A person parked on a bench scrolling their phone for two minutes has nothing to do with your screen—they're avoiding eye contact with a security guard. Meanwhile, a checkout line where shoppers glance up for four seconds, three times in a row, generates zero dwell-time credit. Most networks optimize for the wrong behavior. They chase the person who stays rather than the person who sees. The catch is that attention is not duration. A long gaze at a blank wall tells you nothing. I have watched teams install screens in airport gates where average dwell hit eleven minutes—only to discover that ninety percent of those minutes were spent looking at a phone, not the display. The metric rewarded the wrong location.

Worse, dwell time punishes high-traffic zones. A narrow corridor with a two-second glance window gets flagged as low value. But those two seconds, repeated two thousand times per hour, dwarf the engagement of five people who stand still for three minutes. The industry benchmark sheets I have seen routinely rank a dentist’s waiting room above a supermarket end-cap—because the wait time is longer. That's a failure of imagination, not a failure of location. You end up buying ads that nobody walks past but that a handful of people stare at. Wrong order.

Real examples where dwell time failed

Here is one I fixed last year. A network placed screens in a fast-casual restaurant queue. Dwell time looked fantastic: three minutes, forty seconds average. The problem? The screen faced the order counter. Customers spent those minutes watching their food get bagged, not the ad. The location had high dwell and zero recall. We moved one screen to the beverage station—dwell dropped to twelve seconds. Revenue went up twenty-two percent. Why? Because people waiting for a soda have nothing else to look at. The metric lied until we ignored it.

Another case: a gym chain put screens on treadmills. Dwell time was a dream—forty-five minutes. Ad recall was a nightmare. Runners zone out. They watch the timer, the TV, the person next to them, the window—anything except the screen two feet away. The only thing dwell time proved was that people don’t leave treadmills quickly. Not valuable.

‘We optimized for how long people stayed, not for whether they looked. We paid for the difference.’

— Operations director, after moving three screens out of a waiting room

What industry benchmarks miss

Benchmarks from ad networks lump hospitals with hotels and waiting rooms with retail aisles. They average everything. A typical report will tell you that “high dwell” means above ninety seconds and “low dwell” means below fifteen. That's flat-out wrong for place-based networks. A restroom line with eight-second dwell is premium real estate—captive audience, zero distraction, unavoidable line of sight. A lounge with four-minute dwell is dead space if the screen is behind the sofa. The benchmarks don’t ask: what is the person doing during those seconds? Are they reading a menu? Tying a shoe? Arguing with a partner about where to eat tonight? Most metrics treat every second as equal. That hurts. You make placement decisions based on averages that hide the real behavior.

The honest fix is hard: you have to watch, not just count. But the first step is admitting that dwell time alone is not a signal—it's noise wearing a lab coat. Pull it out of your decision tree. Use it as a sanity check, not a gate. The next section will show you what to put in its place.

The core idea: location quality over quantity of seconds

Defining location quality score

Forget the stopwatch for a moment. A location quality score is not a number you calculate—it’s a judgment call you make before you buy the screen or sign the lease. I have seen networks that look great on paper because the average visitor stands around for two full minutes. But those same screens generate zero lift. Why? Because dwell measures duration, not attention. A person stuck in a slow elevator line may stare at your screen for ninety seconds, but they're already annoyed, already distracted by the next thing they need to do.

Better to ask: Is this spot a magnet or just a placeholder? A high-quality location forces the viewer into a natural visual corridor—think checkout lanes, gas pump nozzles, or the wall opposite a restroom exit. Those spots earn their keep through visibility (can people actually see the screen?), relevance (does the context match the ad?), and dwell—notice dwell is third, not first. Flip the order and you end up chasing seconds that never convert.

Three pillars: visibility, relevance, dwell

Visibility is the gatekeeper. A screen placed six feet above eye level in a grocery aisle might catch a glance, but the angle kills legibility for anyone over 20 feet away. Most teams skip this: they check foot traffic numbers and assume eyes follow. Wrong. I once watched a network install a $3,000 display behind a pillar that blocked the left half of the panel. The dwell time was technically there—people in line could see it—but only if they craned their necks. The fix? Move the screen 18 inches to the right. That simple shift doubled engagement.

Odd bit about advertising: the dull step fails first.

Odd bit about advertising: the dull step fails first.

Relevance is the second pillar, and it's where most networks hemorrhage value. A sports drink ad on a screen in a laundromat? That hurts. The content has no relationship to the environment, so the brain filters it out. Relevance means matching the message to the moment—tampon ads in pharmacy aisles, tool promos near hardware sections, insurance pitches in waiting rooms where people actually fret about their car or home. When relevance is weak, dwell becomes a useless vanity metric.

Dwell sits at the bottom for a reason. It's the result of the first two pillars working, not the cause. If visibility and relevance are solid, dwell almost always follows—naturally, without you chasing seconds. The catch is that advertisers love dwell because it's easy to report. They ask for it. But when you prioritize dwell alone, you end up placing screens in dead zones where people happen to wait a lot. Queues for returns. DMV lines. Those spots feel safe until you realize the audience is angry, bored, or already checked out.

How to weight them without a formula

There is no magic equation—and anyone selling you one is lying. What works is a simple gut check: rank the three pillars from strongest to weakest for a given location. If visibility is weak, fix the placement before you even think about dwell. If relevance is weak, change the content or move the screen. If dwell is weak but visibility and relevance are strong, you might have a timing problem—the crowd passes too quickly, but the glance they do have is high-quality. That's often a better trade-off than a long dwell with zero connection.

'We stopped asking 'How long do they stay?' and started asking 'What are they doing while they stay?' It changed every screen we bought.'

— operator of a 40-location grocery network, after they cut dwell time by half and lifted revenue by 18%

The real test is not a spreadsheet. Walk the floor. Stand where the screen will go. Turn your head left, then right. Does the screen intersect your natural gaze, or is it a detour? Most networks fail here because they optimize for reports, not human behavior. Dwell time gives you data you can defend in a meeting. Location quality gives you a network that actually works. That said—be careful not to overcorrect. A location quality score that ignores dwell entirely is just a hunch. The trade-off is constant: you trade the illusion of precision for the harder work of judgment. Use your gut, but check your gut against real footfall patterns for two weeks. Then adjust. Then check again.

Under the hood: what the data actually says

Foot traffic patterns vs. dwell duration

Dwell time tells you someone *stayed*. Foot traffic tells you someone *passed*. That difference matters more than most network operators admit. I have watched teams pick a spot where shoppers lingered for three minutes—only to discover that only twelve people passed the screen all day. Three minutes is wasted if nobody is there to see it. The fix is brutally simple: count heads, not just stopwatches. Use a people counter at the entrance or a simple camera-based tally over a week. Compare that to the average dwell you can extract from Wi-Fi probe requests or Bluetooth sniffing. If traffic is below 300 passes per hour in a retail corridor, even a ten-minute dwell will underperform a high-traffic spot with only thirty seconds of gaze. The catch is that most platforms report dwell as a vanity metric—it sounds good in pitch decks but hides low reach.

What usually breaks first is the assumption that dwell correlates with attention. It doesn't. A person camped near a screen in a dentist waiting room is often looking at their phone, not your ad. Presence is not viewability. One chain I worked with saw dwell times of four minutes near the pharmacy pickup counter. Yet click-through on QR codes was near zero. Why? The counter faced away from the screen—people were standing *near* it, not *in front* of it. We fixed this by overlaying a simple heatmap of where people actually stood, not just where the sensor pinged.

Viewability angles and obstruction factors

Eye-tracking studies are expensive. That said, you don't need a lab—you need tape. Mark a grid on the floor at three distances: two feet, six feet, and twelve feet. Stand at each point. Can you read the full screen? Now add a pillar, a shelf, or a passing cart. Most screen placements fail because the angle is too sharp or a permanent fixture blocks the lower third. Honest: I have seen a $3,000 screen mounted above a frozen food aisle where the glare from the open cooler doors washed out the display completely between 2 PM and 4 PM. The data said dwell was fine. The data was wrong because it didn't measure glare or obstruction. Build a quick obstruction checklist: 'Can a person standing still in the main flow see 90% of the screen? Is ambient light stable across all hours? Does the screen compete with nearby signage?' If you answer no to any of those, the dwell time is irrelevant.

‘Place-based is about the *where*, not the *how long*. A screen in a corridor with 2,000 daily passes beats a screen in a corner with eight minutes of captive eyes.’

— paraphrased from a retail media buyer who stopped chasing dwell

That hurts because it forces you to admit that some prime real estate—like checkout lanes—actually suffers from low dwell *and* high traffic. Trick is, checkout dwell is fragmented: people glance away every few seconds to unload the cart. The fix is to measure *gaze-seconds per pass*, not total session minutes. Multiply passers-by by estimated gaze from your angle test. That number is rough. It's also far more honest than the dwell figure your platform dashboard spits out.

Audience composition data sources

The third piece of the puzzle is *who* is passing. You can get this from three cheap sources: store loyalty data aggregated at the zone level (not individual), mobile location graphs (anonymized, opt-in panels), or simple manual observation. I have used the last one: stand at the proposed screen spot for one hour on a Tuesday and one hour on a Saturday. Count genders, approximate age buckets, and how many are carrying children or heavy bags. The results will shock you. A screen in the produce section of a grocery store might see 70% women aged 30–50 on weekdays but flip to families on weekends. If your creative is static, you lose half the audience half the time. That trade-off is where dwell data alone misleads—it shows consistent stays, but the *composition* shifts under your feet. The pitfall is over-relying on census data from the property owner. Ask to see the raw pedestrian counts by hour, not the averaged daily figure. Raw data often shows spikes at 11 AM and 5 PM that the average smooths away. Place your screen for those spikes. Ignore the flat hours.

Not every outdoor checklist earns its ink.

Not every outdoor checklist earns its ink.

Most teams skip this step entirely. They pick a spot based on the property manager's claim of 'high traffic' and then blame the creative when results are flat. Wrong order. Collect foot traffic, measure viewability angles, and profile the audience before you drill a single mount. Then—and only then—can dwell time act as a secondary filter, not the primary decision metric.

Worked example: picking a screen in a grocery store

Comparing two candidate locations

You manage a grocery-store network with ten screens already placed. Now you get budget for one more—two aisles are under consideration. Aisle 4: the grab-and-go yogurt fridge, average shopper dwell 47 seconds, foot traffic moderate. Aisle 9: the pasta-and-sauce wall, average dwell 112 seconds, traffic slightly lower. Every dwell-time playbook screams pick Aisle 9. Most teams stop there. We didn't.

We pulled three additional data points for both spots: attention angle (how often shoppers face the screen directly), purchase proximity (distance from screen to the product category it'll advertise), and pass-through friction (how often a cart or another shopper blocks the line of sight). Aisle 4 scored higher on all three—yogurt shoppers stand close, face forward, and rarely get blocked because the aisle is wide. Aisle 9's long dwell came from people standing still reading ingredient labels, often with their backs to the screen. The catch is that dwell time only counts seconds in zone, not seconds of actual exposure.

Metrics collected and decision matrix

Here is what the raw numbers looked like before we weighted them:

• Aisle 4 (yogurt): dwell 47s, attention angle 82%, purchase proximity 1.2m, blockage rate 7%
• Aisle 9 (pasta): dwell 112s, attention angle 31%, purchase proximity 4.5m, blockage rate 38%

We built a simple decision matrix: multiply dwell by attention angle to get effective visual time. Aisle 4 gave us 38.5 seconds of real face-time. Aisle 9 gave us 34.7. That 4-second gap isn't huge—but when you factor in purchase proximity, the edge sharpens. Aisle 4's screen sits two feet from the yogurt cooler. A shopper who sees the ad can reach for the product without moving. Aisle 9's screen hangs above the middle of the aisle; the advertised pasta brand might be six meters away. The shopper has to remember, walk, then search. Those friction points kill conversion. Most teams skip this: they assume dwell equals intent. Wrong order—location quality decides whether those seconds matter at all.

Outcome and lessons learned

We placed the screen in Aisle 4. Six weeks later, the yogurt campaign's click-to-offer redemption was 2.3× higher than the network average. The pasta screen in another store (we left one as a control) returned 0.6×. That hurts when you're buying hardware on a per-screen basis.

'We spent two months arguing over dwell numbers. The real answer was just standing in the aisle and watching where people actually look.'

— store ops lead, after the pilot

The lesson isn't that dwell is useless—it's a starting point, not the finish line. What usually breaks first is the assumption that more seconds equals more value. In practice, a shopper staring at a shelf for two minutes with their back to your screen is worse than a shopper who glances at your ad for twelve seconds and grabs the product. The next time you pick a spot, walk it. Watch three shoppers. Ask: are they facing the screen? Can they reach the product? Is there a cart blocking the view? That three-minute observation beats a spreadsheet every time. And if you're still relying on dwell alone—honestly—you're just guessing.

Edge cases that break the dwell-time rule

Transit hubs: high dwell, low attention

Airports and train stations look like gold mines on paper. People stand around for twenty minutes. They stare at walls. That should be prime screen real estate, right? Wrong order. The problem isn't how long they stay—it's what their brain is doing during those minutes. I have watched travelers in Newark stare straight through a 75-inch display while mentally rehearsing their gate number. The dwell time was fifty seconds. The recall? Zero. Transit dwell is passive, often anxious, and almost never receptive. The eye moves but the mind doesn't follow.

Most teams skip this: they confuse *waiting* with *willing*. A person in a security line is not browsing content—they're scanning for their boarding pass, their shoes, their dignity. The screen becomes visual wallpaper. We fixed this once by dropping screens from a major East Coast transit hub and relocating them to baggage claim. Dwell dropped by forty percent. Ad recall jumped by sixty. The catch is that dwell time alone would have told us to *keep* the security-line spots. That hurts to admit.

Healthcare waiting rooms: captive but distracted

Here dwell time can hit thirty minutes. Captive audience, right? Not really. What usually breaks first is emotional friction. A woman in an urgent care lobby is not thinking about a car lease—she's wondering why her son's fever won't break. A man waiting for a biopsy result will read your QR code, sure—but he won't remember the brand ten seconds later. Dwell time measures presence, not permission. The data says these screens generate high time-on-task metrics. The human truth says those metrics are hollow.

I saw this blow up with a dental chain that placed screens in every exam room. Dwell was enormous—twenty-two minutes average. Click-through was flat. Turns out patients were staring at the screen because staring at the screen was easier than making eye contact with the dental tools. They weren't engaged; they were avoiding. Presence without permission is just furniture.

Field note: outdoor plans crack at handoff.

Field note: outdoor plans crack at handoff.

— paraphrased from a media buyer who pulled the campaign after six weeks

That's the edge case. Healthcare environments look like an advertiser's dream until you realize the audience's primary goal is *leaving*, not leaning in. Dwell time becomes a trap metric—it rewards placement where people are stuck, not where they're open.

Elevator lobbies: short dwell, high recall

Now flip it. Elevator lobbies get four seconds of attention. Maybe six. Most planners skip them because dwell time looks pathetic. That's the mistake. Short dwell can mean *high signal*—the brain is uncluttered, open, and looking for a distraction. The person is waiting for a door to open. They're not checking a phone (bad reception), not talking to anyone (awkward), not deep in thought (forty floors to go). The screen is the easiest thing to look at. Done right, a single four-second message lands harder than thirty seconds of transit noise.

One of our best-performing placements was a twelve-inch portrait screen in a San Francisco office lobby. Average dwell: 3.7 seconds. Average brand recall in follow-up surveys: 83%. The trade-off is obvious—you have to design for that window. No logo animation, no slow reveal, no call-to-action that requires a QR code scan. One frame. One message. One beat. That's it. The pitfall here is that dwell-loyalists kill these placements in reporting reviews. They see low seconds and vote to shift the screen to the cafeteria line, where dwell hits twelve minutes but recall drops to forty. Wrong move.

The rhetorical question for the room: would you rather have four seconds of someone's real attention or forty-five seconds of their anxiety? Transit hubs, healthcare waiting rooms, and elevator lobbies each break the dwell-time rule—but they break it in opposite directions. One overpromises. One underdelivers. One hides in plain sight. The fix isn't more data; it's knowing which metric actually measures the moment.

Where this approach falls short

Data availability and accuracy issues

The multi-metric model sounds great on paper—until you try to pull foot-traffic patterns for a screen in a suburban strip mall. Most networks don't own granular location data; they license it from third parties that sample mobile pings at varying densities. I have seen operators spend two weeks cleaning a dataset only to discover the geofence was misaligned by forty feet. That error alone can flip a 'high-opportunity' corner into a dead zone. The catch is that better data costs real money—enterprise-grade footfall analytics can run $15,000 a year for a single venue. Meanwhile, a simple dwell-time counter on the screen itself costs next to nothing and works offline. You face a trade-off: richer metrics vs. operational simplicity. Many teams choose the cheaper path because their margin structure demands it. And honestly—bad data is worse than no data. A confident wrong number sends you to a worse location than an honest guess.

'We installed three sensors across one store. Two disagreed on peak traffic by 60%. We still don't know which was correct.'

— ops manager at a 50-screen network, describing a six-month data-validation headache

Cost and effort vs. simpler heuristics

Setting up a layered measurement system demands time your small team may not have. Screen placement involves physical install, power runs, landlord approvals—and adding beacon arrays or camera-based counters doubles the project scope. That hurts when you're deploying across twenty new locations in a quarter. What usually breaks first is the calibration step: you must walk the floor, map zones, tag timestamps. One retail chain I advised shipped screens without any dwell capture because the IT team was stretched thin. They relied on gut feel—and still outperformed a competitor that had stalled for months trying to implement 'perfect' metrics. The question is blunt: do you need 90% precision, or will a solid heuristic get you 80% of the value right now? For single-screen deployments in low-traffic lobbies, dwell time alone is often enough. The extra metrics become noise. Not yet a reason to abandon the approach—but a real reason to scope it carefully.

When dwell time still wins

Certain environments punish complexity. Transit stations, for example—people move fast, routes change daily, and sensor placement is restricted by structural steel. I have seen dwell-based models outperform multi-metric ones in subway corridors simply because the dwell signal was cleaner. Same for museums with preset visitor paths: the flow is predictable enough that seconds-at-screen correlates directly with recall. In those cases, adding gaze tracking or demographic analysis introduced measurement latency and no lift in placement accuracy. The rule of thumb I use: if the audience is captive and the route is fixed, dwell time is your friend. If the audience can choose between three checkout lanes and a self-serve kiosk, you need richer data. Know which scenario you're in—and stop apologizing for using dwell when it works. That said, don't let this paragraph become an excuse to skip the work. Test the assumption. Run a two-week comparison. If dwell alone predicts revenue within 12%, save your budget. If it misses by 30%, bite the data-cost bullet and fix your measurement layer. Next, the FAQ section will give you quick answers for the objections that keep coming up in planning meetings.

Reader FAQ: quick answers on screen location metrics

What is the minimum dwell time for an ad to be noticed?

Short answer: about three seconds. That number comes from eye-tracking in real retail environments, not a lab. But here's the catch—three seconds of glancing at a screen while walking past isn't the same as three seconds while stopped at a register. The difference is what happens during those seconds. A shopper unloading a cart has spare visual bandwidth. Someone hurrying down an aisle with a list? Their eyes might hit the screen, but the brain doesn't register the brand. I have seen networks obsess over hitting a 10-second dwell target, only to discover the screen was mounted behind a pillar. Those seconds were worthless. Focus on quality of attention, not a stopwatch.

Can I use mobile location data instead of dwell?

Yes—but don't swap one lazy metric for another. Mobile pings tell you a phone passed within 15 feet of your screen. That's not the same as a person looking at it. Phones in pockets, phones carried past quickly, phones belonging to employees working nearby—all pollute the signal. What usually breaks first is the assumption that foot traffic equals ad exposure. The fix: layer mobile data with dwell analytics from the screen itself. If your CMS reports that 40% of detected devices stayed in view for over four seconds, you have a usable signal. If it reports nothing but "2,500 devices passed nearby," you have a map of movement, not a measure of attention. Trade-off: mobile data covers more area, but it trades precision for breadth.

How do I combine dwell with foot traffic?

Think of it as a filter, not an average. Start with raw foot traffic—this gives you a ceiling. How many people could see the screen? Then apply a dwell-time threshold (say, three seconds minimum) to estimate how many actually did. The ratio is your effective reach rate. A screen with 10,000 passersby and 40% viewability beats a screen with 25,000 passersby and 10% viewability. Most teams skip this: they pick the crowded hallway, then wonder why conversions are flat. The pitfall is that foot traffic fluctuates by hour and day—a single average number hides the peaks where dwell collapses. Pull hourly data. You might find lunch rush has high traffic but zero dwell; mid-afternoon has moderate traffic with high attention. That insight changes where you place creative weight. Honestly, this single step fixes more bad placements than any other adjustment.

What tools can measure viewability in real-time?

Camera-based analytics are the current standard—sensors embedded in the screen bezel or mounted above it. They count faces, duration of gaze, and even approximate age or gender. The catch is privacy compliance and lighting conditions. A screen near a bright window can blind the sensor. A screen mounted too high captures foreheads, not eyes. For networks without hardware upgrades, some CMS platforms now offer software-only dwell estimation using Wi-Fi probe requests and signal strength. Less accurate, but better than nothing. What I would not do: trust a tool that only reports "impressions" without a dwell-time breakdown. That's a black box. If the vendor can't explain how they separate a glance from a gaze, keep looking. Wrong tool—wrong location decisions.

“The best dwell time in the world means nothing if the screen is placed where nobody can comfortably stop.”

— Mike, operations lead at a 200-screen grocery network, after moving one unit from an endcap to a deli counter and seeing 3× engagement