Website integration checklist
Test an embedded experience on a real page before launch, and know where to send each kind of problem.
2 min read
Work through this before the page goes live. Most embed problems are found in ten minutes of testing and cost a day if they surface on launch morning.
Before you build
- The campaign is published in OmniLab Studio, so a real address exists to test against.
- You know whether the page shows one experience or several.
- The experience is served from a subdomain of the site it will appear on, and that address is live. Sign-in does not work otherwise.
- Your developer has picked a loading method. See About website integration.
Test on the real page
Test on the actual page in a staging environment, not on a blank test page. Most of what goes wrong comes from the page around the embed.
- Run the full journey through to the reward or confirmation, including signing in.
- Sign in, reload the page, and confirm the participant is still recognised. This is what fails when the domains do not match.
- Watch the frame resize between steps — it should not jump, leave a gap, or show its own scrollbar.
- Check your footer sits directly below the experience at every step, rather than floating mid-page or being pushed off screen.
- Open a panel and scroll the page: the page behind should stay still.
- Test on a phone. A frame that looks fine at desktop width often crops on mobile.
- Test on the real site with its real security policy applied, not on a bare test page.
- If your site has a sticky header, confirm panels open below it and not behind it.
- If the experience uses the camera, test the permission prompt on a real device.
- Load the page with a slow connection and watch what the visitor sees before the experience appears.
Before you launch
- Swap the test address for the live campaign address.
- Confirm rewards and prize stock are configured and the campaign is published.
- Check the page on the browsers your analytics say your visitors actually use.
Where to send a problem
| What is happening | Who to contact first |
|---|---|
| The experience will not load, or the game misbehaves | OmniLab support |
| A reward is wrong, missing, or out of stock | Your marketing team, in OmniLab Studio |
| The frame is the wrong size, or panels open in the wrong place | Your web team |
| The camera prompt never appears | Your web team — the permission is granted by your page |
| The page is slow, or the embed is blocked | Your web team, then your hosting or security provider |