Skip to content

Custom tracking domain

Send your analytics through a subdomain of your own website, so fewer events are lost to ad blockers.

By default, the web snippet sends events to your region's address, such as https://app.myjourneyanalytics.com. Some ad blockers and privacy tools block requests to analytics services, which means some visits are never counted.

A custom tracking domain sends those requests through a subdomain of your own site instead, such as t.example.com. We run the domain for you: you add one DNS record, and we handle routing and the HTTPS certificate.

1. Add your domain in the app

  1. Open Settings → Managed reverse proxy.
  2. Add a new domain and enter the subdomain you want to use, for example t.example.com. Choose a neutral name; names containing words like "analytics" or "tracking" are more likely to be blocked.
  3. Save. The app shows the DNS record to create.

2. Create the CNAME record

In the DNS settings for your domain, create the CNAME record exactly as the app shows it:

TypeNameTarget
CNAMEt (your subdomain)the target shown in the app

3. Wait for verification and the certificate

The app checks for your record and then issues an HTTPS certificate for the subdomain. The domain's status changes as each step completes.

  • DNS changes usually appear within minutes, but can take up to a day or two depending on your provider.
  • Once the status shows the domain is live, it is ready to use.

4. Update your snippet

Change the address in your snippet's start-up options from your region's address to your new subdomain, for example from https://app.myjourneyanalytics.com to https://t.example.com. The updated snippet is shown in Project settings once the domain is live.

Then check that events are arriving, as you did when you first installed the snippet.

Troubleshooting

  • Stuck waiting for verification: check the record's name and target for typos, and that it is a CNAME rather than an A record.
  • Certificate not issued: make sure the record is not proxied, and that no CAA record on your domain prevents certificates from being issued.
  • Still blocked: some privacy tools block by behaviour rather than by address, so a custom domain reduces, but cannot eliminate, lost events.

Can't find what you need? Contact support