Embedding options overview
When to show a campaign inside your own website, app or kiosk instead of on its own page, and which guide to follow.
1 min read
A campaign can open on its own page, from a link or QR code, or appear inside something you already run: your website, your app or an in-centre kiosk. Embedding keeps visitors in your own journey. The campaign's own page is simpler, and it's what QR codes and social links use.
Pick the way in
| Where it appears | How | Guide |
|---|---|---|
| A page of your website | An iframe, or the JavaScript tag that reads the campaign from the page address | Website integration |
| Your mobile app | A WebView inside the app | Mobile app integration |
| A kiosk or totem | A full-screen shell that also handles inactivity | Kiosk integration |
Each guide gives your developers the address to load, from the campaign and touchpoint links.
Before you go live
- Decide the domain first. The standard
topage.coaddress works for most embeds. Use your own domain when the campaign must sit under your website's: see Subdomain & custom domain. - Test inside the real host page, on a phone too: sign-up, cookies, the camera for scanning games, and links that open outside the frame.