Fewer people passing, fewer coming in, or fewer buying are three different problems with three different owners.
Glimpse tells you which one moved, store by store, hour by hour, and whether what you did about it worked.
Trusted by the world's biggest retailers, brands, transport operators and property groups
A dashboard tells you what the numbers are. A tool helps you change them.
Glimpse is built to be used - to test a window, move a fixture, open a till, re-plan a rota - and then to tell you, hour by hour, whether it worked.

The street is as busy as ever, but a smaller share of the people walking past choose to come in. Windows, A-boards, lighting, whether the door is open, the promotional message.
Owner: Marketing and visual merchandising.

People are coming in, but fewer are buying. They didn't find it, they engaged but didn't convert, or the queue sent them away. Layout, range, staffing, service.
Owner: Store operations.

Measure footfall by hour against the rota, queue length against tills open, dwell against square metres. Allocate staff to demand, open a till before the queue forms, give space to what earns it.
Owner: Operations and property.
Different levers, different owners. The playbook below is how each one gets pulled.
Specific, repeatable, and measurable afterwards. None of them needs a data scientist. All of them need the footfall count to be right.
Compare capture rate across like-for-like stores and find the ones where the street is busy but the door is quiet. Change the window, the entrance, the signage, one thing at a time, and read capture rate the following week against the store's own baseline and its peers.
The extra visitors were already outside.
Make the change in one store or a few, hold the rest as the control, and measure the difference in capture rate, dwell or conversion hour by hour. Weather, day of week and season hit the control stores too, so the comparison strips them out.
Keep what works, revert what doesn't, roll out with evidence.
Heatmaps show where people go and the dead zones they never reach. Dwell zones show which fixtures hold them and which they walk past. Move the fixture, re-route the aisle, re-site the concession, then watch the heatmap change.
A luxury department store lifted product and concession engagement by 22% this way.
Footfall by hour and day shows when the store is actually busy, not when the rota assumes it is. Queue alerts tell the floor a line is building before customers give up.
Conversion by hour shows where service, not demand, is the constraint.
Engagement credits a display, a screen or a concession with the shoppers it actually held, not everyone who walked past.
Evidence for a retail media rate card, a concession negotiation or a supplier-funded fixture.
Compare every store on the same measures, find the outliers, and quantify the opportunity before you act. Fix the three stores with the biggest number first.
Opportunity = capture-rate gap × passers-by × conversion × average transaction value.
Take a store with 6,000 passers-by a day, converting at 20% with an average transaction of £42, and a capture rate of 12% where its like-for-like peers manage 14%. Closing that two-point gap brings in 120 more visitors a day. At the same conversion rate that's 24 more transactions, just over £1,000 a day, roughly £30,000 a month - from people who were already walking past the shop.
Glimpse data can quantify that for every store in the estate before you change anything, so the effort goes where the number is biggest.
Change any figure and the result updates. Start from the store in the example.
Closing the capture rate gap brings in:
Illustrative arithmetic on the figures you enter. It runs in your browser, no data is sent or stored.
"Glimpse transformed our understanding of concession placement and shopper behaviour, providing insights that optimised store layout and improved customer engagement."
Read the case study →
Yes. Make the change in a test store or group, keep comparable stores as the control, and compare capture rate, dwell or conversion between them hour by hour. Because day of week and season affect the control stores too, the difference between the groups is the effect of the change.
Both. Your teams use the Glimpse Portal and report exports day to day. Our client success team runs estate-level analysis and regular success reviews with you, and insight workshops as the partnership matures — see Our approach.
Yes. Everything in the Portal is available as JSON through the REST API or can be exported as CSV for further analysis.
Data flows from the day a site goes live. Changes to a window or a layout show in capture rate and dwell within days; conversion and staffing effects within weeks.
A typical engagement starts with an 8–12 week proof of concept and ends with an executive review, the business case and a rollout roadmap.
It depends on the metric you're trying to change - are you looking to increase conversion from customers inside the store, or to attract more customers in from outside?
We've provided an example ROI calculator to model the impact of increasing capture rate - try it out with your own numbers!
Everything here comes from one platform, fed by your existing CCTV where it can see, Glimpse Sensors where it can't, and Glimpse in a Box where there's nothing to connect to.
Video is processed on site and never stored; only metadata leaves the building. How that works - the pipeline, the three ways to deploy, how accuracy is validated and how privacy is designed in - is on the next page.
A Discovery Session works through your estate, your levers and your objectives, and leaves you with a view of where the opportunity is likely to sit and what a Proof of Concept would measure.
The form didn't load. Book a discovery session on our contact page.
No obligation. No hard sell. We'll come back to you within one working day.Prefer email? sales-emea@glimpseanalytics.com