Domain setup
Point a subdomain at your client portal, verify the CNAME, and wait for HTTPS to go active.
A custom domain gives clients an address such as portal.youragency.com. You add one CNAME record, Trakkr checks it, then provisions the certificate for that hostname.
Domain setup starts from the banner at the top of Settings: White-Label. You need to be a team owner or admin on an account with white-label access. Do this before you invite anyone: Trakkr refuses a client invite until the domain is verified and its certificate is active.
Choose a subdomain
The setup form takes a subdomain and a root domain separately and joins them. It suggests portal, aisearch, geo, insights, and data, and starts on portal.
It must be a subdomain. A bare root domain is rejected with "Please use a subdomain", because a CNAME at the apex would collide with the records that serve your website.
One domain belongs to one team. If another team has already verified the same hostname, setup returns a conflict and you need a different subdomain.
The CNAME record
After you submit the domain, the DNS step shows the exact record to copy:
| Field | Value shown |
|---|---|
| Type | CNAME |
| Name | Your subdomain, for example portal |
| Value | The target Trakkr shows you |
| TTL | Auto or 3600 |
| Proxy | DNS only, shown when your nameservers are Cloudflare |
Copy the target out of the wizard rather than from an old runbook. It comes from configuration and can change. The panel also prints the whole record as one line, and every field has a copy button.
Remove any A, AAAA, or CNAME record already using that host before you add the new one. An A record on the same host is a named verification failure, not a slow propagation.
Verify and activate HTTPS
The wizard has three steps: Domain, DNS, and Verify. On the DNS step, continue once the record is saved at your provider. The banner then reports one of these states.
| State | What it means |
|---|---|
| DNS pending | The expected CNAME is not visible yet. Add it, then use Check DNS |
| Still verifying DNS | Trakkr is re-checking every ten seconds |
| SSL provisioning | The CNAME resolved and the certificate is being issued, usually 2 to 5 minutes |
| Custom domain active | The portal is live, and the banner links to it |
| Domain setup failed | The banner prints the error and Manage reopens the wizard |
You can close the wizard while it works. Trakkr emails the admin who ran verification the moment the domain flips to active, so DNS propagation does not have to be watched.
Once the status is active, open the link from the banner, confirm the browser shows no certificate warning, then load the login page in a private window and check the portal name, logo, and favicon.
When DNS will not verify
Work down this list before assuming propagation:
- The record type is CNAME, not A or ALIAS.
- The Name field holds the subdomain shown in the wizard, in whatever form your provider expects.
- The value matches the target exactly, with no
https://prefix and no path. - No A or AAAA record is left on the same host.
- Cloudflare proxying is off for that record.
Check it from a terminal:
dig portal.youragency.com CNAME +shortThe answer should match the target in the wizard. A trailing dot in the output is normal and is ignored during verification.
When HTTPS stays in provisioning
If DNS verified but the certificate has not landed, leave the record exactly as it is. Repointing it mid-issue makes the next check fail and restarts the wait. Recheck that Cloudflare proxying is off, open Manage to read the current error, and contact support if the same hostname was previously used by another Trakkr team.
Change or remove the domain
Manage Domain in the White-Label header reopens the wizard on a live domain. From there, Delete & restart removes the current setup and takes you back to the first step so you can enter a different subdomain, which starts a fresh DNS check and a fresh certificate.
Removing the domain deletes the certificate and the domain record. Client sign-in and every outstanding invite link on that hostname stop working immediately. Portal settings, client accounts, and brand data are untouched, but no client can get back in until another domain is verified.
Common questions
Can I use my main website domain?
No. Setup requires a subdomain of at least three labels, such as portal.youragency.com. A CNAME at the root would conflict with the records serving your site.
Can two agencies use the same custom domain?
No. Once a hostname is verified for one team, setup for another team returns a conflict.
Why does the target differ from an older guide?
It is read from configuration at setup time. The value printed in your wizard is the only one to trust.
Can I invite clients before HTTPS is active?
No. The invite button stays hidden and the API rejects the invite, because the invite link and the client login both live on that hostname. Prepare branding and features while you wait.
How long should the whole thing take?
Most DNS providers publish the record within a few minutes, and the certificate follows 2 to 5 minutes after verification. Slow resolvers can stretch that to hours, which is why Trakkr emails you when it is done.