Domains & integrations
Domains and HTTPS
Point DNS to your tracker, add the domain and verify the complete HTTPS path.
Prepare DNS
Create the required address record at your DNS provider, pointing the domain to the tracker's public IP. Check both A and AAAA records; an incorrect IPv6 address can produce inconsistent failures.
Add the domain
- Open Domains in the panel.
- Add the intended hostname without a URL path.
- Follow the domain's available status and certificate controls.
- Confirm the server can receive the HTTP/TLS traffic required by that setup.
- Select the verified domain in a campaign and regenerate its URL.
Check externally
dig +short A track.example.com
dig +short AAAA track.example.com
curl -I https://track.example.com/
These read-only checks inspect DNS and HTTP. A tracker root may intentionally not display a public homepage; verify your generated tracking URL and configured login entry as well.
Continue with a campaign
After the domain is ready, select it in your first campaign and copy the newly generated Campaign URL. Open one controlled visit and confirm the actual hostname, HTTPS connection and final destination. A successful DNS lookup alone does not verify the tracking route.
Continue with click and conversion verification. Use the incoming Postback URL generated by this installation and check its domain as well; changing a campaign domain does not update links already saved in external platforms.
Proxy and TLS
If you place a reverse proxy in front of the tracker, verify its TLS mode, forwarded request properties and query-string handling. A valid certificate at a proxy does not prove the proxy-to-server connection or tracking path works.
Switching domains
Do not remove an old domain while active ads or partner postbacks still use it. Inventory those links, update the external platforms and verify clicks and conversions through the replacement domain before retiring the old entry.