Your own booking domain

Serve your booking pages on a hostname you own, such as book.yourdomain.com, instead of your Calemander address.

By default your booking pages live at yourworkspace.calemander.com. A booking domain puts the same pages on a subdomain of your own website. The page, the prices, the theme and the booking itself are unchanged — the address in the browser bar is yours, and so is the address in the confirmation email, the reminder, the calendar invite and the receipt. You do not rewrite any of those: once the domain is live, every new link we send carries it, including the single-use links you create for one person.

What you need

A Pro or Studio workspace. Pro includes one booking domain and Studio includes three. Free includes none.
A domain you already own, and access to wherever its DNS records are edited.
A subdomain to give it, such as book, schedule or appointments. A root domain like yourdomain.com cannot be used yet; that is usually where your own website lives.

Adding your domain

Open Dashboard → Settings → Booking domain and type the hostname you want, for example book.yourdomain.com.
The page then shows one DNS record to add at your domain registrar or DNS host:

CNAME book → customers.calemander.com

The page shows the same four fields your DNS host asks for — type CNAME, the name (book), the value (customers.calemander.com) and DNS only for the proxy setting — with a button that copies the record.

If your DNS host supports Domain Connect, you may not need to copy anything. When we can detect that (Cloudflare does today, and so do NameSilo and Domain Chief), the page shows an Approve at <your DNS host> button instead. It opens your DNS host, which asks you to sign in, pick the domain, and confirm the record it is about to add. You then land back on this page. Nothing is written until you confirm, and the copy-and-paste record stays available underneath if you would rather add it yourself.
If your DNS is at Cloudflare, leave the record unproxied. The cloud icon next to it must be grey, not orange. A proxied record puts your own Cloudflare account in front of ours and the certificate cannot be issued. Every other DNS host adds a plain CNAME with no such setting, and nothing extra is needed there.
Once that record resolves, the certificate for your hostname is issued at the edge, and the status moves from Waiting for DNS to Issuing certificate to Live. The page shows the current status and the time it was last checked, and you can re-check it yourself with Check now.

No certificate is installed anywhere, and there is nothing to renew. On the first domain we set up this way, the certificate was issued a few minutes after the CNAME record started resolving. How long that takes for you depends on how quickly your DNS host publishes the record, which is outside what we can see.

Occasionally the certificate cannot be validated from the DNS record alone, and the page then shows a second record — a TXT record with a long name and value — to add alongside the CNAME. If it is not shown, it is not needed.

Checks keep running for seven days. If the DNS record has not appeared by then, the domain is marked Not set up and the remedy is to remove it and add it again.

What stays on your Calemander address

Only the pages your clients see move. These stay on yourworkspace.calemander.com, and opening one on your booking domain sends you back there:

Your dashboard, sign-in and sign-up.
The API and anything a webhook or integration calls.
Door screens. A paired tablet stores its pairing against the address it was paired on, so the pairing instructions keep naming your Calemander address on purpose.
The “connect your calendar” option on the booking page, which needs a sign-in that can only happen on a Calemander address. It is hidden on a booking domain rather than shown and then failing.

Links you have already sent

Your yourworkspace.calemander.com address keeps working. Every cancel, reschedule and manage link is tied to your workspace rather than to a hostname, so links in emails you sent before adding the domain still open the right booking. New links use the booking domain.

Search engines are told that the booking domain is the address to list, so the same page on two addresses is treated as one page.

Embedding on your own site

Booking pages refuse to be framed by another site, so you cannot put book.yourdomain.com in an <iframe> on your homepage. Use the embed snippet from Dashboard → Embed, which is built for that. Embedding your booking page covers it.

One thing to know about the hostname

HTTPS is enforced on it. Pages served on your booking domain carry a Strict-Transport-Security header with a one-year lifetime. It applies to that hostname alone and does not include subdomains, so it cannot affect www.yourdomain.com or anything else you run.

Google Analytics on your booking domain

If you have set a Google Analytics Measurement ID in Dashboard → Profile, your tag is on your booking pages, and it is on them whether they are served from your Calemander address or from your booking domain. Nothing there changes when you add the domain.

Your website and your booking domain already count as one visitor. Because a booking domain is a subdomain of a domain you own, Google's tag stores its _ga cookie on yourdomain.com itself, which is the same cookie your website's tag reads. Somebody who reads www.yourdomain.com and then books on book.yourdomain.com is one person in one session, rather than a new visitor arriving from somewhere else. There is nothing to switch on for that.

Two things on your side can break it, and both are worth checking once:

Use the same measurement ID on both. The ID you give us must be the one your website uses. A second property, or a second data stream, is a second set of numbers by definition.
Leave the cookie domain automatic on your own site. This is the default. If your site's tag or tag manager pins the cookie to one hostname, such as www.yourdomain.com, the cookie is no longer shared and the same person starts being counted twice, with your own site appearing as a referrer.

Optional, and recommended by Google

Google suggests listing both hostnames even when they are subdomains, which costs nothing and covers the case above:

In Google Analytics, open Admin, and under Data collection and modification click Data streams.
Click Web, then your web data stream.
Click Configure tag settings, then Configure your domains.
Add yourdomain.com and book.yourdomain.com.

The screen beside it, Configure tag settings → List unwanted referrals, is where a payment processor goes if one ever shows up as a traffic source in your reports. That is what the setting is for, and it is worth knowing about rather than acting on in advance.

What you will and will not see

Your reports will show both hostnames, and the Hostname dimension is how you tell your booking traffic apart from the rest of your site.

Your tag measures your booking pages the way it measures any other page on your site. We add no events of our own to your property, so a completed booking does not appear there as a conversion unless you set one up yourself.

The page people land on after paying does not carry your tag, and neither do the cancel, reschedule and manage links we email. If you send people to a thank-you page of your own after a booking — the Redirect after booking option on an event type — that page is yours and your tag measures it normally.

If you embed your booking page instead

The embed snippet in Dashboard → Embed points at your booking domain once you have one, so the embedded frame is on your own domain and is measured like the rest of your site.

Without a booking domain that frame is on yourworkspace.calemander.com, which is a different site from yours. Firefox and Safari keep cookies for a frame like that separate by default, so the same person can be counted twice, and the page address reported from inside the frame is the Calemander one rather than the page it sits on. Adding your booking domain is what fixes that.

Removing it

Dashboard → Settings → Booking domain → Remove stops serving your pages on that hostname. Links already sent keep working, because they resolve through your Calemander address. You can then delete the CNAME record at your DNS host.

Embedding your booking page — putting it inside your own site.
Billing and plans — what each plan includes.

Last checked 2026-09-11.