Kiosk URLs
Understand what a kiosk URL does, how the scanned barcode is passed into it and what to give your technical team.
A kiosk always opens the same touchpoint. At the start of each session, it adds who the visitor is, so the experience opens as that person.
What the address controls
- Which experience loads: a specific touchpoint, a space, or the campaign's landing page if it has one.
- Language and variant:
lsets the kiosk's language for each session, so a visitor never inherits the last one's choice. You can also lock one variant. - Who the visitor is: a scanned loyalty card adds the member's identifier. Without a card, the session starts signed out.
The shape of a kiosk address
It's the touchpoint link from Studio, plus the kiosk's language and one value the kiosk adds for each session:
https://play.lindenhall.example/lindenhall-autumn-kiosk?c=<touchpoint-id>&l=en&fci=<scanned-value>Here play.lindenhall.example is the experience domain. It's your default address, such as lindenhall.topage.co, or your own custom domain. The rest comes from Studio and doesn't change. See Touchpoint URLs & slugs.
| When the visitor | The kiosk adds |
|---|---|
| Scans a loyalty card | l, then fci= and the scanned value |
| Starts without a card | l, then login=0, so they don't carry on as the previous visitor |
Your developer has the exact rules in Kiosk URLs and parameters.
Pass a loyalty member in
The fci parameter carries the value printed on the member's loyalty card. With a recognition integration for the campaign, the member goes straight into the experience, with no form. Without it, they sign in with their customer account.
It works only when:
- your customer identity system is connected to OmniLab: see About customer accounts;
- your Customer Success Manager has set up a recognition integration for this campaign, if members must skip the sign-in;
- the scanned value matches the identifier your system holds. If it doesn't, the visitor sees a message that the account couldn't be found, and can't continue.
Test the unknown-card case
An unrecognised value blocks the session; it never falls back to an anonymous one. During testing, scan a card that shouldn't work. You'll see what a visitor sees when a card is mistyped, expired or from the wrong programme.
Let new visitors sign up instead
Use the address with login=0 instead of fci, and put an acquisition form on the touchpoint. The visitor fills it in on the kiosk keyboard, then plays. See Set up an acquisition form and the keyboard points in Kiosk requirements.
What to give your technical team
- The touchpoint link from Studio, or the campaign link if a landing page presents several touchpoints.
- The kiosk's default language.
- If you use loyalty cards, the format of the value the scanner produces.
- The address of every campaign that runs on the kiosk, for the idle script.
Your developer then follows Build the kiosk shell. Your kiosk provider checks the device against Kiosk requirements.