Subdomain & custom domain
Understand the default OmniLab subdomain and how a branded custom domain replaces it for OmniLab Pages.
Decide which web address your campaigns appear under, from a quick OmniLab-hosted link to your own branded domain. This page covers the two options: the default OmniLab-hosted subdomain, and a custom domain on your own website.
The two domain options
The default hosted subdomain is the standard OmniLab Pages web address OmniLab gives you when you launch without a branded domain.
| Term | What it means | Typical example | Best fit |
|---|---|---|---|
| Default hosted subdomain | The standard OmniLab Pages hostname on .topage.co. This is the fastest launch option. | https://example-brand.topage.co | Pilot launches, internal review, first public rollout |
| Custom domain | A branded address on your own website, pointed to OmniLab by your IT or web team. | https://experience.example.com | Final branded launch, embedding under your own site domain |
An organisation holds one of these at a time
An organisation has exactly one hosted subdomain at a time. Turning on a custom domain replaces the subdomain option rather than adding to it — it doesn't create an extra entry point alongside it.
Recommended rollout path
Move through two stages:
- Start fast on the default hosted subdomain — launch on
.topage.coto keep things simple while you build and test. - Add a branded custom domain when ready — switch to your own domain once the rollout is stable and your branding is confirmed.
If you need to change your hosted subdomain later, remove the existing one first — an organisation can't hold two at once.
How OmniLab chooses the main public base URL
At organisation level, OmniLab Pages uses one main base domain for public campaign URLs. OmniLab Campaigns and touchpoints then append their own public path and query parameters after that base domain.
| Organisation state | Main public base URL |
|---|---|
| A custom domain is configured | https://<custom-domain> |
| No custom domain is configured | https://<organisation-subdomain>.topage.co |
That means the same Campaign Public Link can stay unchanged while the organisation changes the host in front of it.
What you typically manage in OmniLab Studio
- Use the organisation Domain settings for the main OmniLab Pages subdomain when your rollout uses the default hosted domain.
- Treat a custom domain as deployment work that may involve OmniLab plus your IT and web teams.
- After any domain change, retest landing pages, touchpoint URLs, QR codes, and embedded OmniLab Pages experiences before sharing the final links.
When to choose a custom domain
Choose a custom domain when:
- you want OmniLab Pages to appear under your own brand domain
- your website team wants the embedded experience to sit under the same top-level domain as the host page
- final QR codes, campaign links, or media placements must use the branded public hostname
If you do not need those constraints yet, the default hosted domain is usually the quickest and lowest-friction way to launch.