White Label Your Account & Content

To White Label the content in your account and to receive contact-level engagement data, you'll need to head to your domain/network (DNS) settings

Step 1: Choose your white-label subdomain and add it to Domain Setup in Tourial

🛑 You must be an admin in your account to complete this step.

To use any of the MAP/CRM Engagement Integrations, you'll need to serve your tours from your own domain rather than the Tourial domain.

First, create a new subdomain from which to serve the Tourial such as tourial.yourcompany.com. This subdomain can only be used for your Tourials and should not be used for anything else.

Note: Visitors will not interact with the subdomain itself; creating it simply allows you to serve the tour from your domain rather than Tourial's domain.

In the Tourial app, click on the user icon in the upper right-hand corner of your screen and head to Domain Setup.

Once there, you'll see a field where you can enter your subdomain; note that you do not need to include "https://" or "www."

Note: Your CNAME record will point to [youraccount].tourialdns.com

Step 2: Configure CNAME Record

Once you've determined a subdomain, you'll need to log in to your domain provider and point a CNAME record for your chosen subdomain to [youraccountname].tourialdns.com.

For example, a CNAME record for the account, Acme (acme.com), where they've chosen the subdomain to be "tours" would be:

Subdomain: tours

CNAME: acme.tourialdns.com

Setting up a CNAME record works a little differently depending on your hosting provider (GoDaddy, HostGator, etc.). Below are guides for some common providers: ​

If you need assistance setting up a CNAME record and pointing it to Tourial, please reach out to your Customer Success Manager or submit a ticket here.

Note: If you had a Tour(s) embedded anywhere prior to adding a subdomain and configuring your DNS see below.

The embed code changes once you've created a subdomain. So make sure you use the updated version wherever you have tours already embedded to ensure it properly loads from the new subdomain.


Last updated

Was this helpful?