Custom Domains

By default your tracked links use the platform's hostname (click.yourdomain.com). For white-label deployment or branded campaigns, you can add your own domain — visitors and inspectors see your URL instead of ours.

Two types of custom domain. Pick based on what you need it for:

Type	Use For
Click Redirect Domain	The /c/<slug> redirect URL. Customers paste https://yourdomain.com/c/promo. Server-side redirect.
Pixel Domain	The Tracking Pixel's <script src="...">. Customers paste <script src="https://yourdomain.com/<slug>.js">. Cloudflare-managed cert and routing.

You can have both types on the same domain (e.g. click.yourdomain.com for redirects AND track.yourdomain.com for pixels) — they're separate entries in the Domains tab.

Adding a Domain​

Open Click Tracking → Domains → Add Domain.

Pick the Type:

• Click Redirect Domain for /c/<slug> redirect links.
• Pixel Domain for the tracking pixel's script source.

Enter the subdomain you want to use (e.g. click.yourbusiness.com or track.yourbusiness.com). Click Add.

The system creates the entry and shows you the DNS records to add at your DNS provider.

Click Redirect Domain Setup​

This type is CNAME-based. The flow:

1. Add the domain in the dashboard with type Click Redirect Domain.

2. Dashboard shows a CNAME instruction:

3. At your DNS provider (Cloudflare, AWS Route 53, GoDaddy, etc.), create:

   Type:   CNAME
   Name:   click.yourdomain.com   (just the subdomain part — e.g. "click")
   Value:  api.platform.com       (whatever the dashboard tells you)
   Proxy:  Off / DNS Only
   

4. Wait 1–60 minutes for DNS propagation.

5. Back in the Domains tab, click Verify. The system checks the CNAME and marks the domain verified if it points correctly.

Once verified, you can:

• Pick this domain on any link's Domain field (in Links).
• Share https://click.yourdomain.com/c/<slug> URLs.

TLS for Click Redirect Domains​

Click redirect domains use whatever TLS your DNS / proxy setup provides. Most customers point their CNAME directly at our endpoint (no TLS work on your side) or front it with their own Cloudflare account (which then handles the cert).

If you front the domain with Cloudflare yourself, set the proxy to ON in Cloudflare and CF auto-issues a Universal SSL cert for free. Without proxy, the cert is the platform's responsibility — works for shared platform-managed certs.

Pixel Domain Setup (Cloudflare for SaaS)​

Pixel Domains use Cloudflare for SaaS — Cloudflare auto-issues a TLS cert for your domain and routes traffic to our edge worker. More setup steps than redirect domains, but it gets you a Cloudflare-managed cert.

1. Add the domain with type Pixel Domain.

2. Dashboard shows a DNS Configuration modal with three records to add:

3. At your DNS provider, create:

   ① Type:   CNAME
     Name:   track.yourdomain.com
     Value:  click.platform.com    (whatever the dashboard says)
     Proxy:  Off / DNS Only
   
   ② Type:   TXT
     Name:   _cf-custom-hostname.track.yourdomain.com
     Value:  <unique value from dashboard>
   
   ③ Type:   TXT
     Name:   _acme-challenge.track.yourdomain.com
     Value:  <unique value from dashboard>
   

4. Wait 2–5 minutes after adding all three records.

5. Back in the Domains tab, click Verify. The system polls Cloudflare for the verification status. Once Cloudflare validates the TXT records and issues the cert, status flips to verified.

The domain is now ready to use as the Pixel Domain in the Tracking Pixel snippet.

Why Three Records?​

• CNAME — routes browser traffic for track.yourdomain.com to our edge.
• TXT (cf-custom-hostname) — proves to Cloudflare that you own the domain.
• TXT (acme-challenge) — used by Let's Encrypt to issue the TLS cert (Domain Validation method).

All three need to be in place for verification to succeed. The cert auto-renews every 90 days; no further action.

Using a Pixel Domain on a Link​

Once verified, the pixel domain appears in the Pixel Domain dropdown on any link's Pixels section:

Selecting your domain updates the snippet's <script src="..."> URL. Customers see your URL instead of the platform default.

Verification Status​

Status	What It Means
Pending	Just added; DNS records not yet detected. Wait and click Verify.
Verified	DNS records present, cert issued (for pixel domains). Domain is usable.
Failed	DNS records missing or wrong. Re-check at your DNS provider, then Verify again.

Click Verify anytime to recheck. The system caches the last result; pending domains re-verify automatically every few minutes too.

Domain Field Reference​

Domain​

The hostname you're adding. No https://, no path. Just the subdomain.

Valid: track.acme.com, click.yourbusiness.com, c.short.link Invalid: https://track.acme.com, track.acme.com/path, acme.com (apex)

Apex (root) domains aren't supported as tracking domains — always use a subdomain. (Apex domains can't have CNAME records due to DNS spec; you'd need ALIAS or A records, which don't work for our setup.)

Type​

Click Redirect Domain or Pixel Domain. See sections above.

CNAME Target​

Read-only after add. The CNAME value you need to point your subdomain at. Different per domain type and per environment.

Status​

Read-only. pending / verified / failed. Click Verify to recheck.

Last Checked​

Timestamp of the most recent verification attempt. Updates every time you click Verify.

Removing a Domain​

In the Domains tab, click the trash icon on a row. The domain is soft-deleted (recoverable for 30 days, then permanent). Any links that were using it as their Domain field automatically fall back to the platform's default tracking domain.

For Pixel Domains, the corresponding Cloudflare custom hostname is also removed when you delete — the cert is released, no further $0.10/month charge.

---

Next Steps​

• Links — Pick which domain serves a link's redirects
• Tracking Pixel — Use a verified pixel domain in the snippet
• Reports — Reporting works the same regardless of which domain a click came in on