If there is an issue authenticating your domain for custom tracking, there are a few things that could be going on.
First and foremost, please ensure you have properly set up your CNAME record inside of your DNS settings. There is an article here for reference on setting this up.
Second, you will want to ensure that the CNAME record is not proxied. If the proxy status next to the CNAME record in your DNS Settings says proxied, please try turning the proxy status off and rechecking your domain authentication inside of Uptics.
Third, some providers like CloudFlare, for example, are forcing usage of https for all subdomains in DNS settings. If this is the case, this option needs to be turned off. The reason behind it is that we as a 3rd party are unable to control SSL certificates for your domain/subdomains, and at the same time divert your traffic to our domain for tracking purposes. To check if your up. subdomain CNAME record is pointing to our domain, you can quickly enter http://up.your-domain.extension/info and if all is set, you should see a response from our proxy server.
Lastly, there are some top-level domains like .dev where SSL is mandatory and can’t be used with custom domain tracking turned on, and thus custom tracking will not be able to be turned on for those domains.
If you have confirmed all of the above, and are still facing issues, our suggestion would be to reach out and ask your hosting provider how to properly set up a CNAME record with the values we have provided in this article.
