A shopper with bags in front of a large LED screenPassers-by 1 240/hLooked 31%25–44: 46%
Retail media

Retail media, measured at the screen

In-store screens sell real advertising. RVC.DIGITAL tells you, per screen and per time slot, how many shoppers passed, how many looked, for how long and in which age and gender segments — and can pass that signal to your CMS, so the right campaign plays in front of the right shoppers. No face is recognised, nothing is recorded.

The same loop, morning to night

Most retail media networks play one fixed content loop from opening to closing — regardless of who is actually standing in front of the screen. The morning's older shoppers and the afternoon's families see exactly the same message, so a large share of impressions runs into the void. And when an advertiser asks what their money bought, the answer is usually store footfall from the door counter — which says nothing about who was at the screen, or whether anyone looked.

Audience
Morning · older shoppers
Midday · mixed
After school · students
Evening · families
Fixed loop
Same loop
Same loop
Same loop
Same loop
Illustrative

What you get

Proof per screen.

How many shoppers passed each screen, how many turned towards it, how long they looked, and the age and gender mix — by hour, by day, by store.

Reports your advertisers accept.

Post-campaign reach per segment and attention time for each campaign, exportable, comparable across stores. Measured, not assumed.

Audience-aware content (optional).

A real-time, anonymous audience signal to your CMS, so the content mix follows who is in the store — gradually, by time slot, never per person.

What we measure at the screen

All of it on anonymous, aggregated data: the device never recognises a face and never records an image. Privacy & compliance →

  • Passers-by — shoppers who passed the screen (possible conversion)
  • Impressions — shoppers who turned towards the screen
  • Attention — shoppers who looked longer than a set threshold
  • Average attention and watch time (seconds)
  • Age group and gender distribution — aggregated, per time slot
  • Hourly and daily breakdown, any date range
  • Store-to-store and screen-to-screen comparison
  • CSV export and API or webhook access
The RVC.DIGITAL dashboard: possible conversion by day and gross impressions by gender for one in-store screen

Audience-aware content — the CMS keeps control

The next step for a retail media network is content that follows the audience. Not reacting to a single shopper, and not switching in a flash: the system works from the aggregated audience picture of the last few minutes and shifts the content mix gradually. Mornings lean towards older shoppers; after school, students see something relevant to them — not the same loop.

RVC.DIGITAL device
1 · Sense, anonymously

The device estimates the age and gender composition of the audience in front of the zone, locally, with no recording and no face recognition.

Webhook / API
2 · Signal the CMS

That composition is passed to your CMS as a structured signal over a webhook or API. A clean input, not a command.

Your CMS
3 · The CMS decides and plays

Your own rules decide which creatives move up and by how much. Content, weights and campaign priorities stay in your system; RVC.DIGITAL adds the signal.

Dynamic, not instant

The signal is smoothed over a sliding window, bound to thresholds, and the switching cadence is tunable. A single passer-by can never destabilise the screen, and every campaign receives a stable, measurable share of screen in front of its own target audience.

RVC.DIGITAL integrates with Telelogos Media4Display (we are a member of the Telelogos Software Partner Network) and Wallboard; any CMS that can receive a webhook or call an API can consume the same signal.

Proof after the campaign

The same sensor that can drive content also measures what the screen actually delivered: reach per segment, dwell and attention time, by store and time slot. On the RVC.DIGITAL dashboard these become reports that show, after the fact, whether a creative reached the audience it was bought for. Every advertiser gets proportional visibility in front of its own target group — and a report to prove it.

A sample post-campaign report page: campaign name and period, four headline figures (passers-by, impressions, attention, average attention time), reach by age and gender segment with the target group highlighted, and a per-store breakdown. Illustrative data.

Built for how stores actually work

Its own connection.

Each device runs on its own 4G link. It does not touch your store network — no access, no exposure, nothing for IT to approve.

Plug and play.

Devices arrive pre-installed and ready to run. On site you need a power socket and a place for the camera; placement is agreed during the pilot.

Minimal hardware.

A small mini PC and a USB camera, or an existing RTSP camera stream. Linux, Windows or Android — it runs on entry-level Android signage players as well.

From a few screens to a chain.

The same setup scales from a handful of checkout-zone screens to a network across all stores, with store-level and network-level reporting.

Or built into the display: digital totems are available with the camera and RVC.DIGITAL already on board, installed as a single unit.

Built by a software company, adapted to your network

RVC.DIGITAL is a product, not a project — but it was built by a team that has written enterprise software for 25 years. Your own age bands and thresholds, a trigger cadence tuned to your network, reports in the format your advertisers already use, integration into your CMS or BI, or a measurement nobody offers yet — a checkout-queue timer and a shelf monitor both started as one customer's request. Tell us what you need, and we build it into your deployment.

Shoppers are counted, never identified

On-device processing, no image leaves the device
No face recognition, no biometric data
Independent DPIA (November 2024): outside the scope of the GDPR
Stored in the EU
Read how it works →

In use in hypermarket retail media networks

Hypermarket chains run RVC.DIGITAL across their in-store retail media networks to report the measured audience of their screens to their advertisers — by store and by time slot.

Start with a pilot, not a contract

A pilot runs in one to five stores with one to five devices for two to four weeks. We agree the screens and camera placement with you, install pre-configured devices, and close with a report: audience per screen and time slot, attention, segments, and — if you choose — a first look at how a CMS trigger would behave on your network. You decide what comes next.

Frequently asked questions

Does it work with our CMS?
With Telelogos Media4Display and Wallboard today, and with any CMS that can receive a webhook or call an API. The signal is a simple structured message; your CMS rules do the rest.
Do we need to connect it to our store network?
No. Each device has its own 4G connection and never touches your network.
Can it tell us which campaign increased sales?
No — and we would rather say so. RVC.DIGITAL measures who was in front of the screen and whether they paid attention. Linking that to till data is your analysis; we give you the audience side of it.
Does it recognise shoppers or build profiles?
No. The device detects that a person is present and estimates an age band and gender, then discards the frame. No face is recognised, nothing is recorded, nobody can be identified or re-identified. Privacy & compliance →
Can we use our existing cameras?
Often yes — an RTSP stream from an existing camera can feed the measurement, as long as the view of the screen zone is suitable. We check this in the pilot.
Can it also measure store footfall, queues or shelves?
Yes, with the same device family — see Store analytics and Shelf availability. This page is about the screens.

See your own screens measured.

A two-to-four-week pilot in a few stores, closed with a report you can show your advertisers.