About kiosk integration
Understand how an OmniLab experience runs on a touchscreen kiosk, and who owns which part of the setup.
Run an OmniLab campaign on a touchscreen kiosk so visitors can scan a card or a voucher in-store and play straight away. This page explains how the setup works end to end and who is responsible for each piece, so you can brief your kiosk provider before any build starts.
A kiosk deployment always involves three parties: you, OmniLab, and the company that supplies or builds the kiosk. Most delays on these projects come from an unclear split of responsibilities, so agree that split first.
How the setup works
The kiosk is the host. It shows your own welcome screen, reads the barcode, and then opens the OmniLab experience in a web frame that fills the screen. Everything the visitor sees inside that frame — the game, the form, the branding, the reward — comes from OmniLab. Everything around it belongs to the kiosk.
- 1Welcome screen and session chrome
- 2Home and close buttons — the visitor’s way out at any moment
- 3The OmniLab experience: game, form, branding, reward
- 4On-screen keyboard for form entry
- 5Barcode scanner
Everything outside the dashed frame is built by your kiosk provider.
The visitor journey looks like this:
- The kiosk shows a welcome screen inviting the visitor to scan.
- The visitor scans a barcode.
- The kiosk builds the OmniLab experience address, adding the scanned value to it.
- The kiosk opens that address in its web frame.
- OmniLab checks the scanned value, then runs the experience.
- When the session ends — or when the visitor walks away — the kiosk closes the frame and returns to its welcome screen.
- 1The kiosk shows its own welcome screen
- 2The visitor scans a barcode on the kiosk's scanner
- 3The kiosk builds the address and opens it in its web frame
- 4The OmniLab experience loads inside that frame
- 5The visitor plays — everything on screen now comes from OmniLab
- 6OmniLab tells the kiosk when the session ends or the screen goes quiet
- 7The kiosk clears the frame and returns to its welcome screen
- 8At any moment the visitor can press the kiosk’s close button, which jumps straight to step 7
Steps 4 to 6 run inside a frame the kiosk opened — the kiosk application never hands over, it stays in control the whole time.
OmniLab does not control the kiosk
OmniLab supplies the experience and the address that loads it. Scanning, screen management, and returning to the welcome screen are all handled by the kiosk software.
Two ways a visitor starts a session
Which one you choose changes what the visitor has to do at the screen, and what you have to print on the barcode.
| Approach | The visitor scans | What happens next | Use it when |
|---|---|---|---|
| Known member | Their loyalty card | OmniLab recognises the member and takes them straight into the experience | You already run a loyalty programme and want zero friction at the screen |
| New participant | A printed invitation or voucher | The visitor fills in the acquisition form on the kiosk, then plays | You are recruiting new contacts and want the visit to generate a signup |
The known-member route requires your customer identity system to be connected to OmniLab first. See Customer accounts.
For the exact addresses and parameters, see Kiosk URLs.
Who owns what
Share this table with your kiosk provider at the first technical meeting.
| Responsibility | Owner |
|---|---|
| Welcome screen design and build | Kiosk provider |
| Barcode scanner and the values it reads | Kiosk provider |
| Web frame that loads the experience | Kiosk provider |
| Building the experience address and adding the scanned value | Kiosk provider |
| On-screen keyboard for form entry | Kiosk provider |
| The “are you still there?” message and returning to the welcome screen | Kiosk provider |
| Detecting that a visitor has walked away | OmniLab, via a script an admin installs |
| The experience itself: game, form, branding, reward | OmniLab |
| Campaign configuration, rewards, and prize stock | You, in OmniLab Studio |
| Barcode stock: which cards or vouchers are printed and distributed | You |
| Staff supervision and prize handover in-store | You |
The short version: OmniLab owns everything inside the frame, your kiosk provider owns everything outside it, and you own the campaign and the barcodes.
What to prepare before you brief a provider
- The campaign is built and published in OmniLab Studio, so a real address exists to test against.
- You know which of the two start routes you are using, and the barcode values are decided.
- Rewards and prize stock are configured, because these change what the visitor sees at the end.
- Your IT team knows the kiosk needs internet access to your OmniLab domain.