go.acme.com serves dl.js, event ingest, and your
tracking links from your own origin. This page explains what changes. The setup procedure
lives on Domains.
What the subdomain serves
A hostname that is not verified in your workspace returns
404 for every path. Datalyr
writes the routing entry only after Cloudflare confirms ownership and issues the
certificate.
What changes when it goes live
The server-set cookie is the point of the whole exercise. Safari caps a script-set cookie
at 7 days, and it doesn’t apply that cap to a cookie the server sets.
What does not change
Consent still governs collection. The edge suppresses the__dl_visitor_id cookie when
the request carries Sec-GPC: 1, DNT: 1, or X-DL-Consent: denied.
Serving from your own origin doesn’t opt you out of GDPR, ePrivacy, or your own consent
banner.
Requirements
- A subdomain. An apex domain cannot carry a CNAME, so it never activates.
- A CNAME set to DNS only. A proxied Cloudflare record blocks certificate issuance.
- One SSL validation record, shown on the domain card.
datalyr.com, lyr.link, and dlyr.link.
Verify
- Open Settings → Install after the domain reads
Active. - Confirm the snippet
srcreadshttps://go.acme.com/dl.js. - Deploy the updated snippet.
- Load a page in a private window.
- Open the browser network panel.
- Confirm the
dl.jsrequest goes togo.acme.comand returns200. - Open Live and confirm the pageview arrives.
When it does not work
Next
- Domains: the full add, verify, and remove procedure.
- Cross-domain tracking: what the shared cookie reaches.
- Tracking links: build redirects on the new host.