Overview

Custom domains let you replace generic Intempt-hosted URLs with a domain you own. Verify a root domain once at the organization level, then assign it to individual projects for the capability you need.

Each domain can be enabled for one or more of these:

📘 Media pending

Screenshot of the domain list hasn't been captured yet.

Adding a domain

Open the org/project selector at the top of the sidebar, select Settings, then go to the Domains tab. Select Add domain.

1. Domain name. Enter a domain you own (e.g. book.yourcompany.com). It must be a valid domain; a plain top-level name like yourcompany won't validate.
2. Capability. Choose one: Booking, Click tracking, Privacy center, or Email sending.
3. Mail-from subdomain (Email sending only, optional). Sets the address your emails send from. For example, entering mail sends from mail.yourcompany.com.

📘 Media pending

Screenshot of the Add Domain dialog hasn't been captured yet.

📘 Good to know

Adding a domain doesn't activate it immediately. You still need to verify DNS ownership before it's usable.

Verifying DNS

After you add a domain, its DNS records dialog opens automatically. You can reopen it any time from the domain's menu (View DNS records).

Add the listed records at your DNS provider, then select Verify DNS. DNS changes can take up to 72 hours to propagate, so a domain can sit at Pending DNS for a while even after you've added the records correctly. That's expected, not a failure.

📘 Media pending

Screenshot of the DNS records dialog hasn't been captured yet.

Domain status

Managing project access

A verified domain isn't automatically available to every project. From the domain's Projects button, choose which projects in your organization can assign it.

📘 Media pending

Screenshot of the project access dialog hasn't been captured yet.

📘 Good to know

Granting project access doesn't assign the domain by itself. A project admin still has to pick it from Project → Connectors → Domains. Per-project email addresses (e.g. hello@yourdomain.com) are configured at the project level, not here.

Removing a domain

From the domain's menu, select Remove domain and confirm. This disables all traffic routing for that domain immediately.

Use cases

• Booking pages under your own brand. Assign book.yourcompany.com as a Booking domain so prospects never see an intempt.com URL.
• Branded click tracking. Use a tracking subdomain so links in your marketing emails resolve under your own domain instead of a shared one.
• A dedicated privacy center URL. Point privacy.yourcompany.com at Intempt's hosted consent/preference pages.
• Improving email deliverability. Verify a sending domain with a mail-from subdomain so outbound email authenticates against your own DNS instead of a shared default.
• Multi-project domain reuse. Verify a domain once at the org level, then grant access to only the specific projects that should be able to assign it. Useful when one org runs several customer-facing projects that shouldn't share a domain by default.

Where to go next

See Organizations & Projects for how projects relate to your organization, and API Keys for other org-level settings.