Kiosk URLs
Understand what a kiosk URL does and what to give your technical team to set one up.
Set up the web address a kiosk loads so the device always opens the right OmniLab experience. This page is for whoever configures the kiosk and the developer who wires it up.
A kiosk URL is the address you load inside a kiosk screen, tablet, or managed device to show an OmniLab experience. Instead of a visitor choosing where to go, the device always opens the same address — pointing directly at a specific campaign, touchpoint, or space.
Getting the URL right matters: if visitors should land on a specific activity, the URL must point to that touchpoint. If the device should show different experiences over time, the URL may use a parameter that controls which experience loads.
What the URL controls
- Which experience loads — a full campaign landing page, a specific touchpoint, or a targeted space.
- Whether the experience runs in embedded mode — kiosk screens typically use an embedded context so the OmniLab experience adapts its layout for the enclosure.
- Language and variant — you can lock the kiosk to a specific language or experience variant via the URL.
What to give your technical team
Your developer needs the OmniLab campaign URL from OmniLab Studio, plus a note on whether the kiosk should land on a campaign page or go directly to a specific experience.
Hand this to your developer: Kiosk integration (technical deep-dive)
That guide covers the URL patterns in full, the query parameters used in kiosk deployments, and the technical wrapper requirements for device and browser integration.