Getting Started
Custom domain setup
Why custom domains matter, what records you need, and how to validate a first-party tracking domain
Doc #6 Reviewed Mar 8, 2026
A custom domain gives your signal pipeline a brand-controlled first-party surface instead of relying on a shared endpoint. For serious production use, that is the default recommendation.
Why it matters
- Improves credibility with operators and security reviewers
- Reduces reliance on a generic shared hostname
- Creates a cleaner first-party setup for browsers, tags, and internal teams
- Keeps rollout paths consistent across storefronts, product sites, and server calls
What you need
- A gateway in Anacoic
- Access to your DNS provider
- A subdomain you can dedicate to tracking, such as
signals.yourdomain.com
Recommended rollout
- Create and validate the gateway first on the shared endpoint.
- Add the custom domain in the dashboard after the core destination path is working.
- Point the DNS record to the value Anacoic provides during setup.
- Wait for DNS propagation, then confirm the gateway health view reflects the custom hostname.
- Move your production snippet or server calls to the custom domain only after validation.
Operational guidance
- Use a dedicated subdomain instead of your root domain.
- Keep one custom domain per major traffic surface when you need cleaner isolation.
- Validate one high-value path first before migrating every destination.
- If health data does not appear after DNS changes, check propagation and then use the troubleshooting guide.