Domain Setup

A custom domain gives clients an address such as ai.youragency.com. You add one CNAME record, Trakkr checks it, then provisions HTTPS for the domain.

Domain setup is the banner at the top of Settings: White-Label. You must be a team owner or admin with white-label access.

Choose a subdomain

Use a subdomain of a domain you control, such as:

ai.youragency.com
portal.youragency.com
insights.youragency.com

Do not use the root domain that serves your main website. The setup form combines the subdomain and root domain and checks the format before continuing.

Add the CNAME

After you submit the domain, Trakkr shows the exact DNS record:

Field	What to enter
Type	CNAME
Name	The subdomain shown in setup
Target	The target shown in setup
TTL	Your provider's default is usually fine

Copy the target from Trakkr. Do not assume a target from an older setup or this guide, because infrastructure can change.

At your DNS provider, remove any A, AAAA, or CNAME record already using the same host before adding the new CNAME.

Verify and activate HTTPS

Return to the domain setup and continue to verification. The wizard has three stages: Domain, DNS, and Verify.

You may see these states:

DNS pending: the expected CNAME is not visible yet.
Still verifying DNS: Trakkr is checking automatically.
SSL provisioning: the CNAME is correct and the certificate is being prepared.
Custom domain active: the portal is live at the HTTPS address.
Domain setup failed: the page shows the error and lets you manage the setup.

HTTPS setup usually takes a few minutes after DNS verifies. DNS changes can take longer to reach every resolver. You can close the wizard while it works; Trakkr can email you when the portal is ready.

Check the result

When the status is active:

Open the domain link from White-Label settings.
Confirm the address starts with https:// and the browser shows no certificate warning.
Open a private browser window so your agency session does not mask the client login.
Check the portal name, favicon, logo, and login copy.
Sign in with a test client and follow links to Dashboard, Pages, Results, and Reports as enabled.

Troubleshooting DNS

If verification stays pending, check:

The record type is CNAME.
The host matches the full domain entered in Trakkr.
The target matches the value shown by Trakkr, with no https:// prefix.
No A or AAAA record uses the same host.
Cloudflare proxying is off.
The record has had time to propagate.

You can inspect it from a terminal:

dig ai.youragency.com CNAME +short

The answer should match the target in the setup wizard. Some DNS tools show a trailing dot; that is normal.

Troubleshooting HTTPS

If DNS verifies but HTTPS remains in provisioning:

Recheck that Cloudflare proxying is off.
Leave the CNAME in place while certificate setup completes.
Use Manage Domain to review the current error.
If the same domain was used by another Trakkr team, contact support so ownership can be checked.

Do not point the record elsewhere while provisioning. That makes the next verification fail and delays the certificate.

Change or remove the domain

Open Manage Domain and choose the change or delete action. Changing the domain starts a fresh DNS and HTTPS setup. Deleting it removes the custom domain configuration.

Removing the domain stops client access through that address. The portal settings, client accounts, and brand data remain, but you need another active portal address before clients can return.

Common questions

Can I use my main website domain?

Use a subdomain. A CNAME at the root can conflict with your website and is not the intended setup.

Can two teams use the same custom domain?

No. A portal domain must resolve to one team.

Why does the setup target differ from an old guide?

The target is configuration-driven. The value shown in your setup is the source of truth.

Can I invite clients before HTTPS is active?

You can prepare clients and settings, but wait to send the live portal address until the domain is active and tested.