How to Verify Your Custom Domain

Last updated: January 30, 2026 • 5 min read

Setting up a custom domain (e.g., data.yoursite.com) is the most critical step in server-side tracking. It allows your tracking script to bypass ad-blockers by appearing as "First-Party" traffic.

Why use a custom domain?

When you use a generic tracking URL (like analytics.google.com), ad-blockers instantly recognize and block it. By using a subdomain of your own website (like metrics.myshop.com), the browser treats the request as "internal," significantly increasing data accuracy.

Pro Tip: Using a custom domain also allows us to set "HttpOnly" cookies, which bypass Safari's 7-day ITP limit, extending attribution windows to up to 2 years.

Choosing a subdomain

You can pick any name, but we recommend something generic to avoid detection by aggressive blocklists. Good examples include:

  • servertrack.yoursite.com
  • metrics.yoursite.com
  • collect.yoursite.com
  • data.yoursite.com

Adding the CNAME Record

Log in to your DNS provider (GoDaddy, Namecheap, Cloudflare, etc.) and add a new record.

Instead of pointing to a specific IP address, you will point your subdomain to our secure ingress server. Use the following details:

Type Name (Host) Target / Value TTL
CNAME data ingress.servertrack.io Auto / 1 min

Note: Replace ingress.servertrack.io with the specific CNAME URL shown in your ServerTrack Dashboard.

Verification Process

Once you have added the record, go back to your ServerTrack dashboard and click "Verify Domain".

  1. Our system will check if your subdomain (e.g., data.yoursite.com) is correctly aliased to our server.
  2. If successful, we will automatically issue a Free SSL Certificate (HTTPS) for your subdomain via Let's Encrypt.
  3. This process usually takes 1-5 minutes, but DNS propagation can sometimes take up to 24 hours.

Troubleshooting

If verification fails:

  • Cloudflare Users: Ensure the cloud icon is Grey (DNS Only), not Orange (Proxied). We handle the SSL termination, so "Orange Cloud" (Proxy) often causes a "Too Many Redirects" error during the initial setup.
  • Check for Typographical Errors: Ensure you didn't accidentally type the domain twice (e.g., data.yoursite.com.yoursite.com). Most DNS providers only require the prefix (data) in the "Name" field.
  • Wait Longer: DNS changes are not instant. Use a tool like DNSChecker.org to see if your CNAME has propagated globally.

Was this article helpful?

Please log in to provide feedback on this article.