Dns configuration for custom domain

In this guide

Choose the subdomain The record types Steps Check from the command line Common problems If you use Cloudflare Why a first-party subdomain matters Terms you will see Frequently asked questions

Key takeaways

Use a subdomain such as data.yourstore.com, not your main domain. Add the record your host gives you, then press Verify.
Record types: A (to an IP), CNAME (to a name) and TXT (proof of ownership). Use exactly what the host shows.
Most failures are a typo, a record at the wrong DNS provider or a proxy setting. Check with dig before you change anything else.

A custom domain for server-side tracking means a subdomain of your own website points to the tagging server. That way the browser talks to your domain, and cookies set by the server belong to your site. Getting the DNS right takes minutes if you know what to look for. This page explains the records, the settings that matter and how to check your work. It sits with the setup checklist and server container not receiving requests.

Choose the subdomain

Use a neutral name: data, go, t, metrics. Avoid track, analytics, ads, pixel if blockers might match them. See avoiding ad-blocker blocking.
Use a subdomain of the same site you track, so cookies are first-party.
One subdomain per site, unless you use Multi-Domains.

Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

The record types

Type	Points to	Typical use
A	An IPv4 address	When the host gives you an IP address
AAAA	An IPv6 address	When the host gives you an IPv6 address
CNAME	Another name	When the host gives you a hostname to point to
TXT	A text value	Proof that you own the domain, sometimes needed before the host will serve it

Use the type and value the host shows. In Open Tracked: Settings, Domains, add your subdomain, then copy the record it shows into your DNS provider and press Verify.

Steps

Add the domain in the host

The host shows the record to create.

Open your DNS provider

Where your domain's name servers point: your registrar, Cloudflare, Route 53 or similar.

Create the record

Name: the subdomain part only (for example data). Type and value as shown.

Lower the TTL

A TTL of 300 seconds makes changes show up faster.

Verify

Press Verify in the host. Wait a few minutes and retry if needed.

Data in, clean out

Raw events in. Clean events out.

Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, Google Ads, TikTok.

Check from the command line

dig +short data.yourstore.com
dig +short CNAME data.yourstore.com
curl -I https://data.yourstore.com/healthy

dig shows what the name resolves to. The curl on /healthy should answer status 200 once the server and certificate are ready.

Common problems

SymptomVerify keeps failing

Likely causeThe record is at a DNS provider that is not authoritative, or has a typo.

FixCheck which name servers your domain uses, and add the record there.

SymptomThe record includes the full domain twice

Likely causeSome panels add the domain automatically, giving data.yourstore.com.yourstore.com.

FixEnter only data as the name.

SymptomCertificate warning

Likely causeThe certificate is still being issued.

FixWait a few minutes after DNS verifies.

SymptomA conflicting record exists

Likely causeAn old A or CNAME record on the same name.

FixRemove the old record. A name cannot have both a CNAME and an A record.

SymptomWorks for you, not for others

Likely causeDNS has not propagated everywhere, or a proxy blocks it.

FixWait, and test from another network.

If you use Cloudflare

Cloudflare can proxy a record (the orange cloud) or just answer DNS (grey cloud). Follow the setting your host recommends for the tagging subdomain, and do not enable extra rules such as bot challenges on it, because a challenge page returned to a tracking request breaks the event. Check that firewall rules do not block your host's servers or legitimate crawlers.

0 of 7 done

The subdomain has a neutral nameThe record type and value match what the host showsThe name is only the subdomain partThere is no conflicting recordThe host shows Verified/healthy answers 200No bot challenge is on the tagging subdomain

Why a first-party subdomain matters

A tagging subdomain is part of your own website, so a cookie your server sets from it belongs to your site. Browsers and blockers tell the difference between your own domain and a third-party one, and are far more relaxed about the first. That is why a record that looks like a small technical detail has such a large effect on how much data survives. A server on a vendor's domain, even a friendly one, would be treated as a third party. The same server behind data.yourstore.com is treated as part of your site.

It also explains why the choice of name matters a little. A plain name draws no attention. A name that contains a word from a filter list invites blocking. Pick a name, test it with a couple of common blockers, and keep it stable. Changing the name later means new cookies and new paths, so choose carefully once.

Terms you will see

Apex domain: Your main domain without a prefix, such as yourstore.com.
Subdomain: A prefix in front of your domain, such as data.yourstore.com.
TTL: How long, in seconds, other servers may remember a DNS answer.
Propagation: The time it takes for a DNS change to reach everyone.
Authoritative name server: The server that holds the real DNS records for your domain.

Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

Frequently asked questions

Which DNS record do I need for a custom tagging domain?

The one your host shows: usually an A or CNAME record for the subdomain, and sometimes a TXT record for verification.

Can I use my main domain?

Use a subdomain. It keeps your website and tracking separate and works with first-party cookies.

How long does DNS take?

Usually minutes, sometimes a few hours. A low TTL helps.

Why is my domain not verifying?

Typo, wrong DNS provider or a conflicting record. Check with dig.

Should I proxy the tagging subdomain in Cloudflare?

Follow your host's instructions and avoid bot challenges on that subdomain.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Guides →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...