Custom domain checklist
Verify a custom domain works end to end before you point campaigns, QR codes, and embeds at it.
2 min read
Run through this before the new address appears anywhere a participant can reach it. A problem found after the posters are printed costs you the print run.
Check the address
- OmniLab has confirmed the address is live.
- The records resolve in a public lookup tool, not just in your own browser.
- The certificate validation record is still in place.
- The padlock shows with no certificate warning, in a fresh browser session.
- A published campaign opens on the new address and runs through to a reward.
- The default address still opens the same campaigns, so nothing already published breaks.
Update everything that uses it
- Embedded pages: change the address in every page that embeds an experience. See Website integration.
- Apps: a WebView address ships inside an app release, so plan the app update.
- QR codes: download again any code that hasn't been printed yet.
- Email templates: check any fixed links in your email platform.
- Customer sign-in: if participants sign in with your own customer accounts, register the new callback address with your identity system. Your Customer Success Manager gives you the address.
Before you print anything
- Scan a test QR code with a real phone on mobile data, not office wi-fi.
- Check your corporate network filter doesn't block the address. It catches out in-store tablets and staff devices.
Where to send a problem
| What's happening | Contact first |
|---|---|
| The address doesn't resolve | Your DNS or IT team |
| A certificate warning won't clear | Your DNS team, to check the validation record, then your Customer Success Manager |
| The address resolves but the campaign won't load | OmniLab support |
| Participants can't stay signed in on an embedded page | Your web team: the page still frames the default address, which the browser treats as third-party. It must use your own subdomain. |