Why use a custom domain

Updated July 2026 · 2 min read

Serving your container from a subdomain you own — like tags.yourstore.com — makes tracking first-party: cookies last longer, fewer requests get blocked, and browsers treat data collection as part of your site.

It makes tracking first-party

When your tagging server runs on tags.yourstore.com, every request from yourstore.com stays within the same site. To the browser, tracking is no longer a third-party service bolted onto your pages — it's part of your website. That one change drives every benefit below.

Cookies survive longer

Browsers with tracking prevention — Safari is the strictest — cut the lifetime of cookies set by third-party scripts down to a matter of days. Cookies set from your own subdomain count as first-party, so returning visitors keep the same identity for far longer. In practice that means better attribution, longer conversion windows and more complete remarketing audiences.

Fewer blocked requests

Ad blockers and privacy tools work from lists of known tracking domains — google-analytics.com and connect.facebook.net are on all of them, and shared tagging domains tend to get added over time. A subdomain of your own site isn't on any list, so events that would otherwise be dropped still reach your server.

Your subdomain vs a shared domain

A new container starts on TagVolt's own domain, which is fine for testing. For production, your own subdomain wins on every front:

• Cookies — set from a shared domain they're third-party to your site; from tags.yourstore.com they're first-party.
• Blocklists — popular shared tagging domains eventually get listed; a domain only you use stays clean.
• Trust — visitors and browsers see requests going to your brand, not to an unknown third party.

Set it up

It takes one CNAME record, and SSL is handled for you — start with Add your custom domain, then follow DNS records setup. New to the topic? How server-side tagging works has the full picture.