Subdomain & custom domain
Understand the default OmniLab domain, aliases, and delegated custom domains used to publish Pages.
This article explains the three public-domain models you may see in an OmniLab rollout: the default OmniLab-hosted domain, additional aliases, and a delegated custom domain on your own website.
Understand the three domain terms
The default OmniLab-hosted domain is sometimes described as the generic domain. It is the standard Pages hostname OmniLab provides when you launch without a branded domain.
| Term | What it means | Typical example | Best fit |
|---|---|---|---|
| Default hosted domain | 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 |
| Alias | An extra public hostname that points to the same Pages deployment as the main domain. Teams use aliases when different brands, locations, or channels need their own entry URL. | https://paris-centre.topage.co | Multiple entry points for the same rollout |
| Custom domain | A branded subdomain on your own website delegated to OmniLab through DNS. | https://experience.example.com | Final branded launch, embedding under your own site domain |
How aliases and custom domains relate
A custom domain is a branded form of alias. The practical difference is who owns the hostname: OmniLab-hosted aliases usually stay on .topage.co, while custom domains use your own domain and DNS.
Recommended rollout path
The onboarding recommendation is to start on .topage.co, add aliases if needed, and move to a branded custom domain once the rollout is stable.
How OmniLab chooses the main public base URL
At organisation level, Pages uses one main base domain for public campaign URLs. 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 Studio
- Use the organisation
Domainsettings for the main Pages subdomain when your rollout uses the default hosted domain. - Treat additional aliases and delegated custom domains as deployment work that may involve OmniLab, your DNS team, and your certificate or infrastructure owners.
- After any domain change, retest landing pages, touchpoint URLs, QR codes, and embedded Pages experiences before sharing the final links.
When to choose a delegated custom domain
Choose a custom delegated domain when:
- you want 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.
Related
Organisation domain settings
See what the organisation Domain screen manages directly in Studio.
Embedding
Use the right implementation pattern for iframe, WordPress, WebView, or delegated-domain embeds.
Touchpoint URLs & slugs
See how the base domain combines with the Campaign Public Link and touchpoint parameters.