Skip to main content

🔗 Linking zones to kiosks (Kiosk Engagement Rate)

Connect a camera zone to a kiosk to understand how nearby footfall turns into kiosk interactions.

Leo avatar
Written by Leo
Updated over 5 months ago

What Kiosk Engagement Rate means

Kiosk Engagement Rate shows how many people who entered the linked zone actually interacted with the kiosk.

Simple formula

Kiosk Engagement Rate = zone entries with kiosk interaction ÷ total zone entries
  • A person enters the zone and interacts with the kiosk: counted as engaged.

  • A person enters the zone and does not interact: counted as not engaged.

  • Counts are session based, not unique individuals.

Requirements

  • A camera with a zone drawn that covers the kiosk area or a sensible proximity.

  • A kiosk device that reports interaction events.

  • Matching time filters on the dashboard so camera and kiosk data line up.

How linking works today

  • The Merlin Cloud team creates the zone ↔ kiosk link for you.

  • Contact support with: organisation, location, camera, zone name or colour, and kiosk ID.

  • The link will appear in your dashboard once configured.

Roadmap: self-serve linking from the dashboard is planned for a future sprint.

What you will see

  • A new metric on the main dashboard: Kiosk Engagement Rate for the linked zone.

  • Existing kiosk KPIs continue to work: funnels, kiosk conversion rate, and content viewed.

  • When you filter by the linked zone, all widgets update to zone-specific analytics.

Interpreting the metric

  • High engagement, low footfall: the kiosk converts well but the area is quiet. Consider relocating signage to drive more visits into the zone.

  • Low engagement, high footfall: strong attraction to the area but weak kiosk pickup. Review on-screen messaging, CTA placement, or height and angle.

  • Balanced engagement: steady footfall and healthy interaction rate. Test content variants to improve conversion.

Accuracy and limitations

  • Camera counts typically reach 85 to 90% accuracy in good conditions. Crowding, occlusion, lighting, mirrors, or poor placement reduce accuracy.

  • We do not track identities. Re-entries count as new sessions.

  • If a camera goes offline, zone counts are not backfilled.

  • If a kiosk goes offline, kiosk interactions are queued and sync when online, which can shift the timestamp slightly.

Best practices for reliable linkage

  • Draw the zone to fully cover the kiosk footprint plus a small approach area.

  • Keep zones non-overlapping near the kiosk to avoid attribution confusion.

  • Mount the camera high and angled down so the kiosk and approach path stay visible.

  • After linking, do a quick walk test: enter the zone without using the kiosk, then repeat and interact with the kiosk, and confirm the rate changes as expected.

Troubleshooting

  • Engagement rate looks too low

    • Confirm the zone actually covers where people stand to use the kiosk.

    • Check kiosk interaction logging on the device.

    • Reduce reflections and backlighting around the kiosk.

  • Counts look too high or noisy

    • Tighten the zone so pacing on the edge is not counted.

    • Avoid overlapping zones near the kiosk.

  • No rate shown

    • The zone may not be linked yet. Contact support with camera, zone, and kiosk details.

    • New zones show No data until movement and interactions occur.

Permissions

  • Admins and Managers can view and act on the metric.

  • Viewers are read only.

  • Link creation is currently handled by the Merlin Cloud team.

Did this answer your question?