Wayfinding analytics and real-time updates: what to measure and change
Quick answer: DigitalSignage.com measures wayfinding screens through the touch events they log: every tap on a SignStudio touch scene is an event, so a directory reports sessions, taps per scene and the destinations people choose, and a QR code on the screen reports scans. Searches typed into a mapping vendor's map are measured by that vendor, and people counting needs a sensor. Updates reach the screens in minutes: a tenant move is a row in a shared Google Sheet, a closure is a scene swap, an event is a scheduled campaign, and an embedded map reloads at the refresh interval set in SignStudio. Proof of play is an Enterprise feature.
Key facts
- A touch directory reports four things without extra hardware: sessions, taps per scene, destinations chosen and the time of each, because every touch in a SignStudio scene fires an event that can be logged.
- A QR code on a wayfinding screen reports scans when it carries a link tagged with UTM parameters; the QR component is part of mediaCLOUD Plus+.
- A directory cannot count the people who walked past it, read a static sign or asked a guard; that needs a sensor or a tally sheet at the desk.
- A tenant move reaches every screen as one edited row in a shared Google Sheet within the component's refresh interval, against a reprint cycle of 1 to 2 weeks for printed directories.
- In the 30-day worked example below, 1,240 searches on one directory put the top destination at 18 percent and failed searches at 9 percent, enough to justify one new static sign and one synonym.
- Proof of play is an Enterprise feature; on the free and Plus+ plans the record is the schedule plus remote screenshots from SignStudio player management.
- Software is free for the first 3 screens and $3 per screen per month on Plus+, every screen billed once an account has 4 or more, so 10 measured directories cost $360 a year.
Last updated November 4, 2026. Sources: our touch, scheduling, player management, QR and KPI guides; ADA 2010 Standards; WCAG 2.2; ISO/IEC 18004.
What can a wayfinding screen measure?
Whatever passes through the screen as an event: touches, scene opens, destinations chosen, QR scans and the time of each. It cannot see the people who did not touch it, so a wayfinding analytics plan always pairs the screen's own events with one or two signals from outside it, such as a tally at the information desk.
| Signal | Where it comes from | What it needs | What it tells you | What it cannot tell you |
|---|---|---|---|---|
| Touch sessions | Touch events in SignStudio scenes | Touch components, part of mediaCLOUD Plus+ | How many people used the directory and when | Who they were, or how many walked past |
| Taps per scene and destination chosen | The same events | Nothing extra | Which categories, tenants and destinations matter | Whether they arrived |
| Search terms and failed searches | The mapping vendor's search box | The vendor's report | Missing names, old names, misspellings | Lives in the vendor's tool, not in SignStudio |
| QR scans | A link with UTM parameters behind the code | QR component on Plus+, or a QR image on the free plan; your web analytics | How many took the route to their phone | Scans are intent, not arrivals |
| Session length and abandonment | Events with timestamps | Timestamps per event | Confusing steps, long dead ends | Why they left |
| Passers-by and glances | A camera or sensor | Separate hardware and a privacy review | Attention to non-touch directional screens | Nothing about intent |
| Questions at the desk | A tally in a shared Google Sheet | Staff discipline | What the screens fail to answer | Volume at unstaffed times |
| Screen uptime | SignStudio player management | Included on every plan | Online or offline, last check-in, a remote screenshot | Whether anyone looked |
Bottom line: the screen gives you sessions, taps, destinations, scans and times for free; searches live with the mapping vendor, foot traffic needs a sensor, and the desk tally catches what the screens miss.
Our documentation states that every touch in an interactive scene is an event, that touches can be logged at the resource level and that reports show which buttons and scenes get used. It does not describe the report format, an export or a dashboard per screen, so ask support (support@digitalsignage.com, live chat at https://chat.digitalsignage.com/) for the current reporting options before promising a specific report.
People counting and attention measurement with cameras or sensors are covered in our audience analytics guide; they are separate hardware with their own privacy obligations, and they measure the passive directional screens that touch events cannot. Keep that layer optional. Most wayfinding decisions come from the touch events and the desk tally alone.
Touch events carry no personal data when the scenes are designed that way: a tap on "Pharmacy" records the destination and the time, not the person. Keep it so. Do not add a form that asks for a name or an email to a wayfinding flow, keep the desk tally to the question and the hour, and treat camera-based counting as its own privacy review.
Which wayfinding metrics drive which decisions?
Each metric should map to one change you would actually make; a metric with no decision attached is not worth collecting. The thresholds below are common planning figures to start a review, not benchmarks, and the right numbers for a building come from its own first 30 days.
| Metric | Starting threshold, a common planning figure | Decision it drives |
|---|---|---|
| Sessions per day per directory | Under 20: relocate the kiosk or add an attract loop; over 300: add a second kiosk nearby | Placement and count |
| Top destination share | One destination above 15 percent of taps | Add a static directional sign for it at the nearest junction |
| Failed searches | Above 5 percent of searches | Add synonyms, former names and categories to the tenant sheet |
| Sessions ending without a destination | Above 30 percent | Simplify the first screen; fewer choices, bigger targets |
| Peak-hour share | 30 percent of sessions inside 2 hours | Staff the desk then; daypart the attract loop for that audience |
| QR scans per session | Under 10 percent | Enlarge the code, move it to the result screen, improve the prompt |
| Language switches | Any regular use of a language | Translate the full content set for it |
| Offline hours per month | Any | Fix the network drop or the power schedule before anything else |
Bottom line: eight metrics, eight decisions; review them monthly, change one thing at a time, and read the next month's numbers before changing the next.
A key performance indicator, or KPI, is a number tied to a goal; our goals and KPIs guide shows how to write the goal first and pick the number second. For wayfinding the goal is usually one of three: fewer questions at the desk, shorter time to destination, or more use of a service people could not find, and each goal points at a different metric above.
Read the metrics over a long enough window. Thirty days is a common planning figure for a first review, because a single week carries the weekday and weekend pattern only once and a holiday can double or halve the searches. Compare like with like: the same directory, the same opening hours, and the same month a year earlier once that data exists.
How do real-time updates reach wayfinding screens?
Through four routes that need no reprint: an edit in a shared sheet, a scene swap, a scheduled campaign, and an embedded web page that reloads on its own. Which route fits a change depends on who makes it and how often, and a good system gives leasing, facilities, events and security each their own route.
| Change | Where it is edited | How it reaches the screen | Time to screen | Who makes it |
|---|---|---|---|---|
| Tenant moves, renames, hours | A shared Google Sheet | The Google Sheets component shows the sheet and updates when it changes | Minutes, at the component's refresh | Leasing or reception |
| Closure or construction detour | A scene in SignStudio | Publish; players download the scene and switch | Minutes | Facilities |
| Today's event in Hall B | A campaign with a date and time rule | Scheduled ahead; players switch on their own clock | No wait at the time set | Events team |
| New corridor or floor plan | The mapping vendor's editor | The Web Page component reloads the embed at the refresh interval set in SignStudio | At the next refresh | Facilities with the vendor |
| Emergency instruction | A campaign at Emergency priority | Overrides every other campaign on the screens it targets | Immediate on publish | Security |
| Transit times, weather, news | The Web Page or RSS component | Fetched live while the player is online | Live | Automatic |
Bottom line: give each department the route it needs (a sheet, a scene, a schedule or an embed) and keep the Emergency campaign built and unscheduled so security never designs under pressure.
The priority ladder in our scheduling guide is Emergency, High (80), Normal (50), Low (20) and Default (10): the highest valid campaign wins, then the most specific schedule, then the most recently changed. A detour scene at High priority therefore replaces the normal directory on its screen group and drops away when its end date passes.
Updates also survive a network drop. Our guide on what happens when the internet goes down documents that the DigitalSignage.com SignPlayer caches every assigned scene and plays from the cache, so the directory and the detour keep showing; live zones such as the embedded map and feeds pause until the connection returns, then the player syncs any change published meanwhile.
User management keeps the routes separate. Our user management guide documents roles from Owner to Viewer with scopes that limit a user to specific screens, groups or content, so leasing edits the sheet, facilities edits scenes for its building's group, and only security touches the Emergency campaign. Changes are logged.
Name things so that a change is easy to find later. A scene called "Detour, level 2, east corridor, until 14 March" tells the next person what it is and when it should disappear; a scene called "New detour 2" does not. Put the end date in the campaign rule as well as in the name, so the detour removes itself if nobody remembers to.
Where is digital wayfinding technology heading?
Toward the visitor's phone, more languages on the first screen, accessibility modes built into the design rather than bolted on, kiosks that pair with mobile, and assistants that answer a typed or spoken question from the directory data. These are directions we see in deployments and standards, stated as directions and not as statistics.
| Direction | What it looks like on the screen | What to plan now |
|---|---|---|
| QR handoff to the phone | The route continues on the visitor's device after one scan | Size the code for its scan distance (a 6 ft scan needs a 7.2 inch code); build the mobile page |
| Multilingual by default | A language switch on the first screen, names in their own script | Allow 30 to 40 percent extra space in every text box; choose fonts with full coverage |
| Accessibility modes | High contrast, larger type, audio, a lowered touch zone | Design to ADA 2010 section 308 (15 to 48 in) and WCAG 2.2 (4.5:1, 24 px targets) from the start |
| Kiosk plus mobile | The kiosk orients, the phone navigates | One data source, the tenant sheet, feeding both |
| Assistants | A question such as "where can I buy a phone charger" answered from the directory | Keep the tenant data clean and structured; the answer is only as good as the sheet |
| Indoor positioning | A blue dot on the phone's map from beacons or Wi-Fi | A separate vendor layer, not a DigitalSignage.com feature; budget it separately |
| Analytics tied to operations | Search data changes static signs and staffing rotas | A monthly review with facilities and the desk |
Bottom line: every direction in the table rewards the same preparation, a clean structured tenant list and an accessible layout, so start there whatever you buy later.
The language switch is the direction with the clearest payback, because the content already exists and only needs translating. Build every text box with 30 to 40 percent spare room from the first version and the second and third languages cost translation time alone. Our multi-language localization guide gives the expansion figures by language, from 30 percent longer in German to 50 percent shorter in Chinese.
Our documentation does not describe a built-in assistant, indoor positioning or beacon support in SignStudio. Where a page on this site mentions them it is describing the market, and anything beyond the Google Sheets, Web Page, QR and touch components is a question for support (support@digitalsignage.com, live chat at https://chat.digitalsignage.com/).
How do you prove what played on a wayfinding screen?
With proof of play on Enterprise, or with the schedule plus remote screenshots on the other plans. Proof of play is a log of which file played on which screen and when; on DigitalSignage.com it is an Enterprise feature priced per screen in the public calculator, and it is what an advertiser or a landlord's auditor expects.
On the free and Plus+ plans the evidence is two documents. The campaign schedule fixes what each screen group was assigned to show and when, and SignStudio player management shows each player online or offline with its last check-in and takes a remote screenshot on demand, which a weekly routine can file. That is enough for a detour notice or a tenant's promotion; a paid advertising contract usually calls for the Enterprise log.
Worked example: turning 30 days of searches into a signage change
A shopping centre reviews one entrance directory after its first 30 days. The numbers below are an illustration, not a benchmark: the directory logged 1,240 searches, about 41 a day, and the desk kept a tally of questions in a shared sheet. The review takes an hour and produces four changes.
| Step | Finding | Calculation | Change |
|---|---|---|---|
| 1. Top destination | Restrooms, 223 searches | 223 / 1,240 = 18 percent, above the 15 percent threshold | Add a static restroom sign with an arrow at the entrance junction ($150 to $400 as a planning figure) and a restroom line in the attract loop |
| 2. Failed searches | 112 searches returned nothing | 112 / 1,240 = 9 percent, above 5 percent | Investigate the terms |
| 3. Largest failure | 48 searches for "Sunrise Books", the former name of Northside Books | 48 / 112 = 43 percent of failures | Add a "Former name" column to the tenant sheet and fill it; 5 minutes |
| 4. Peak hour | 384 searches between 12:00 and 14:00 | 384 / 1,240 = 31 percent in 2 of 12 hours, 1.9 times the average hourly share of 16.7 percent | Daypart the attract loop with the food court map from 11:30 to 14:30; staff the desk at lunch |
| 5. QR scans | 62 scans in 30 days | 62 / 1,240 = 5 percent, under 10 percent | Enlarge the code from 3.6 to 7.2 inches so it scans from 6 feet, and move it to the result screen |
| 6. Expected effect | Restroom searches and the renamed-tenant failures | 223 + 48 = 271 of 1,240 searches, 22 percent, now answered before anyone touches the kiosk | Re-read the numbers after the next 30 days |
Bottom line: one hour with 30 days of events bought a $150 to $400 sign, a 5 minute sheet edit, a lunch daypart and a bigger QR code, and should remove about a fifth of the searches from the kiosk.
The restroom finding is the common one. When a single destination dominates a directory's searches, the building has a static signage gap, not a kiosk problem, and the cheapest fix is a printed arrow at the junction where people get lost. The QR size comes from the 10:1 distance-to-size rule in our QR code size guide.
How to do this in DigitalSignage.com
Build the directory on touch components, which are part of mediaCLOUD Plus+, and read the touch events as the usage record; put the tenant list in a shared Google Sheet shown by the Google Sheets component; embed the mapping vendor's map in the Web Page component; add the QR component with a UTM-tagged link and count scans in your own web analytics. A locked-down full kiosk presentation is an Enterprise feature.
- Create screen groups per building or wing so campaigns and scenes target the right directories.
- Give leasing an Editor role scoped to the sheet-driven scenes and security access to the Emergency campaign only.
- Build the Emergency and detour scenes now, at Emergency and High priority, and leave them unscheduled.
- Schedule the event dayparts a week ahead with date and time rules.
- File a remote screenshot of each directory weekly from player management.
- Review the touch events, the mapping vendor's search report and the desk tally on the first working day of each month.
Our documentation does not describe a search-term report inside SignStudio, heat maps, people counting, a per-screen analytics dashboard or an export format for touch events; for any of these, ask support (support@digitalsignage.com, live chat at https://chat.digitalsignage.com/) rather than promising them in a tender.
Frequently asked questions
Wayfinding analytics and real-time updates: what to measure and change
Measure what passes through the screen as events: touch sessions, taps per scene, destinations chosen, QR scans and the time of each, plus the mapping vendor's search terms and a tally of questions at the desk. Tie each metric to one decision, such as a static sign when one destination exceeds 15 percent of searches. Real-time updates reach the screens as a Google Sheet edit, a scene swap, a scheduled campaign or an embedded web page that reloads. Proof of play is an Enterprise feature on DigitalSignage.com.
What analytics can a wayfinding kiosk provide?
Sessions, taps per scene, destinations chosen, session length and the time of day, because every touch in a SignStudio touch scene fires an event that can be logged. QR scans are counted through the link's UTM parameters in your web analytics. Search terms and failed searches come from the mapping vendor's report. Foot traffic past the screen needs a separate sensor or camera.
Which wayfinding solutions have visitor analytics?
Any touch-based platform that logs events, any mapping vendor that logs searches, and any sensor vendor that counts people; a complete picture usually combines two of the three. On DigitalSignage.com every touch is an event logged at the resource level and reports show which buttons and scenes get used; the report format and export are not described in our documentation, so ask support for current options.
How do real-time updates reach wayfinding maps and directories?
A tenant change is a row edited in a shared Google Sheet that the Google Sheets component follows when the sheet changes. A closure or detour is a scene published to the screens' group, with High priority if it must replace the normal directory. An event is a campaign scheduled by date and time. A floor-plan change is made in the mapping vendor's editor and the Web Page component reloads the embed at its refresh interval.
What are the latest trends in digital wayfinding technology?
Stated as directions rather than statistics: handoff to the visitor's phone by QR code, a language switch on the first screen, accessibility modes designed in from the start (ADA 2010 section 308 reach ranges, WCAG 2.2 contrast and targets), kiosks paired with mobile from one data source, assistants that answer questions from the directory data, and indoor positioning as a separate vendor layer.
How do you prove a wayfinding screen was playing?
With proof of play, a log of which file played on which screen and when, which is an Enterprise feature on DigitalSignage.com priced in the public calculator. On the free and Plus+ plans the evidence is the campaign schedule plus remote screenshots from SignStudio player management, which also shows each player online or offline with its last check-in.
What does wayfinding analytics cost?
Nothing extra for the screen's own events: touch components are part of mediaCLOUD Plus+ at $3 per screen per month, every screen billed once an account has 4 or more, so 10 directories are $360 a year. The mapping vendor's search report is part of its subscription. People counting sensors are separate hardware. Proof of play is priced per screen on Enterprise in the public calculator.
Related guides
- Digital signage goals and KPIs: what to measure and how
- Audience analytics for digital signage
- Scheduling and playlists in SignStudio
- Digital wayfinding systems implementation guide
- Interactive wayfinding and digital directory systems
- How big should a QR code be on a digital sign?
- Player management in SignStudio
- What happens when the internet goes down
- Digital directories for malls and shopping centers
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no watermark, no time limit), then from $3 per screen per month on Plus+. Once an account has 4 or more screens, every screen is billed, so 10 screens cost $360 a year; Enterprise is priced per screen in the public price calculator. The free DigitalSignage.com SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser, so the hardware you already own usually works. Start free · pricing · How 11 vendors compare on price
Maintained by MediaSignage Inc., operator of DigitalSignage.com since 2006. Product behavior on this page comes from our own SignStudio and SignPlayer documentation; where we do not document a step, this page says so instead of guessing. Last reviewed November 4, 2026.