In this article
Make ownership part of setup
A collection domain often begins as a small task on a tracking checklist. Someone adds a record, the test event arrives, and the project moves on. Months later, a website migration or agency handover can make that seemingly finished task relevant again.
Treat the domain as a maintained dependency. Record which organization controls it, which team approves changes, and who can restore service if the configuration changes unexpectedly. This is especially useful for agencies: the person who created the setup may not be the person responsible for it next quarter.
Choose the route deliberately
Google documents a same-origin path, such as www.example.com/metrics, and a subdomain, such as metrics.example.com, for first-party server-side tagging. The same-origin route involves forwarding requests through a CDN or load balancer; the subdomain option involves DNS configuration.
Use that difference to start a conversation with the website team. Which route fits the infrastructure they already manage? Who reviews routing changes? Which environment will you test first? Avoid deciding from the URL's appearance alone. The maintainable choice is the one your team understands and can support.
Write a small handover record
Keep the record short enough to stay current. Include the collection address, its destination, the relevant container, the DNS provider, and the responsible teams. Add the last successful test and the steps for checking the route after a website change. Store access instructions through your normal access-management process, without copying secrets into the document.
- Name the person or team responsible for domain and routing changes.
- Record which environments use each collection address.
- Identify the test that confirms the intended container receives an event.
- Explain who should review a migration, removal, or ownership transfer.
Test the next change, too
A working domain is one part of a working measurement setup. Revisit it during hosting changes, CDN changes, site launches, and client handovers. Use the same known test event before and after the change so the comparison has a stable reference.
TagVolt's domain guide starts in the container's Domains tab and tells you to create the exact DNS record shown in the app. Keep those provider-specific steps alongside your own operational record. Confirm the current instructions when making changes, so the implementation can evolve while responsibility for it remains clear.
