Skip to Content
Link Routing & EdgeCustom Tracking Domains

Custom Tracking Domains

Your tracking links live on a tracking domain — the https://<domain>/t/<id> part. You can use the shared default host out of the box, or bring your own for better branding, deliverability, and ad-network trust.

The default host

Every account can use the shared platform host immediately — no setup:

trk.kmsboxpm.cc

trk.kmsboxpm.cc  ·  SYSTEM — shared default tracking host. It works instantly and does not count toward your plan’s domain limit.

Bring your own domain

You can connect any domain or subdomain you own — there’s no required prefix. All of these are valid:

ExampleNotes
go.yourbrand.comA subdomain
track.yourbrand.comAnother subdomain
r.yourbrand.comA short subdomain (great for SMS / clean links)
links.yourbrand.comAny label you like
yourbrand.comYour root / apex domain works too

Add as many as you want (within your plan’s limit). Mix and match across campaigns — each campaign’s Domain node picks which one to use.

You are not limited to a trk. subdomain — that’s just the convention used by the shared default host. Use whatever subdomain (or your bare domain) fits your brand.

Why use your own domain?

  • Branding — your links read go.yourbrand.com, not a shared host.
  • Deliverability & trust — some ad networks favor (or require) a branded domain, and your domain reputation is isolated from other users.
  • Resilience — a domain you control gives you more routing flexibility.

Setting one up

Add the domain

In Sources → Domains , add your domain or subdomain.

Create the DNS record

Add the DNS record the dashboard shows you, at your DNS provider.

Verify

Synaptyx verifies ownership and issues the TLS certificate automatically — you never touch a certificate, and it renews itself.

Use it

Once it’s verified and active, select it on a campaign’s Domain node. Your /t/ links now use it.

Notes

  • TLS is automatic — certificates issue on first use and renew before expiry.
  • The shared default host is always available as a fallback and never counts toward your plan’s domain limit.
  • Your plan caps how many custom domains you can have (see Plans).
  • The dashboard host deliberately refuses /t/* traffic, so your ad clicks never hit the login/brand domain.

Next