Connect a custom domain
Create the domain, verify its CNAME, and link it to the Pixel.
Use a subdomain you control, such as track.example.com, to receive Pixel events. You need access to domain DNS records, which route requests to their destination.
Create and verify
- Open Setup → Domains and select Add domain. Enter only the hostname, without
https://or paths. - Select the new domain in the list.
- Copy the displayed Type / Name / Value table.
- Add the CNAME record in your DNS panel using CJM's displayed name and destination. Do not copy a target from another project or an example.
- Save, wait for propagation, and select Verify in CJM.
- Once Verified appears, link it to the Pixel and verify website events.
Some DNS panels expect only track as Name and append example.com automatically. Check that the final hostname is track.example.com.
Project domain and Pixel link
Domains are managed at project level. Create and verify them in Setup → Domains. Then open the Pixel's Domains tab and select the existing verified domain to link it. The domain detail lists its Linked pixels. Until a domain is verified and linked, the Pixel keeps using the standard destination.
A custom domain changes the collection endpoint used after it is verified and linked. It does not replace the Pixel installation or automatically change the cookie domain. The current snippet does not need manual editing.
Change or unlink
Open the Pixel's Domains tab and use Unlink to remove its link, then optionally select another domain. Reload the website to check the destination. Delete in Setup → Domains is separate: inspect Linked pixels first to understand which Pixels use it.
Troubleshooting
- Pending verification: check Name and Value, allow propagation, and repeat Verify. Read the last-check error if shown.
- CNAME cannot be verified: check conflicting records and whether the provider exposes the required CNAME. Ask your DNS administrator for help.
- Verified but old destination: check the correct Pixel link and reload.
- No events: DNS verification alone does not prove end-to-end delivery. Follow Verify installation.
A custom domain does not guarantee bypassing all ad blockers or browser restrictions.