Setting up a custom domain
Replace the {slug}.trackofferz.com URL with your own brand domain (e.g. panel.yourcompany.com).
Updated 2026-05-21
Out of the box your network runs on {slug}.trackofferz.com. If you want a fully white-labelled experience, you can point your own subdomain at the platform.
Choose a hostname
Use a subdomain — not the apex of your main marketing domain. Common patterns:
panel.yourcompany.compartners.yourcompany.comaffiliates.yourcompany.com
Don't use the apex (e.g. yourcompany.com) — the panel and your marketing site can't co-exist on the same hostname.
Add the DNS record
In your DNS provider, create a CNAME record:
| Type | Name | Value |
|---|---|---|
| CNAME | panel | app.trackofferz.com |
Don't use an A record — the platform's IPs may change. CNAME tracks correctly.
Cloudflare-proxied CNAMEs (the orange-cloud icon) can break TLS issuance because we use on-demand Let's Encrypt. Set the record to DNS-only (grey cloud) until verification completes; you can re-enable proxy after.
Verify and activate
- In your panel, go to Branding → Custom domain.
- Enter the hostname you set up (e.g.
panel.yourcompany.com). - Click Verify. The panel does a DNS lookup; the value must resolve to
app.trackofferz.com(or whatever the platform brand host is). - Once verified, the panel issues a TLS certificate on-demand the first time someone visits the hostname. This usually completes in 5–10 seconds.
- Your subdomain and custom domain both work for the same network — same login, same data. Subdomain is never removed; the custom domain is additive.
Common failure modes
- "DNS lookup failed" — wait 10 minutes after creating the CNAME. Some providers cache aggressively.
- "Resolved to wrong host" — double-check the CNAME value. If you typed
trackofferz.cominstead ofapp.trackofferz.com, it'll fail. - TLS issuance hangs — usually Cloudflare proxy still on. Disable proxy, retry, re-enable after.
- Custom domain works, subdomain stops — never happens. The platform serves both indefinitely.