About custom domains

By default, experiences are served from an address such as lindenhall.topage.co. With a custom domain, they're served from a subdomain you own, such as play.lindenhall.example. Only the address in front of the campaign path changes: you build campaigns the same way.

What changes

When you need one

If you embed experiences in your own website, a custom domain is required. A browser treats a frame from another domain as third-party and blocks or isolates its cookies, so participants can't stay signed in. Serve the experience from a subdomain of the site it appears on, and the frame counts as part of that site. See Website integration.

When it's worth it anyway

• Printed placements. A QR code on a poster or a receipt outlives the campaign. An address you own can be re-pointed later; one you don't own can't.
• Trust at the point of scan. A shopper reads the address before typing anything into a form.
• Analytics and consent. A subdomain of your main site keeps the experience under the same parent domain. That affects how your analytics and consent tools treat it.

For a short internal pilot or a one-off test, skip it: the default address launches immediately and costs nothing.

What happens to the default address

Adding a custom domain doesn't retire the default one. lindenhall.topage.co keeps serving the same campaigns, so nothing you've already published breaks. Once the new address is live, the links Studio shows for your campaigns use it.

A printed QR code, though, keeps whichever address it had on the day it went to print, long after the campaign ends. Choose the domain before anything physical is produced.

What it involves

You choose a subdomain, and your Customer Success Manager emails the DNS records to add. Whoever manages your DNS adds them: see Set up the DNS records.

Next steps

• Set up the DNS records
• Custom domain checklist
• Subdomain & custom domain