Overview

This guide walks you through setting up a custom tracking domain (CNAME) to improve your tracking reliability and deliverability in Sona. By using your own subdomain instead of a generic tracking URL, you reduce the likelihood of your tracking being blocked by ad blockers or security software. With this setup you get more complete data collection and a more presentable tracking approach.

When to use a custom tracking domain

Configure a custom CNAME when you want to:

Improve tracking pixel reliability and reduce blocking.
Maintain brand consistency in your tracking URL.
Meet corporate security requirements that restrict third-party domains.

Before you begin, make sure you have:

DNS access: access to your domain's DNS management, through a provider such as GoDaddy, Cloudflare, or Namecheap.
Admin permissions: administrative permissions to modify DNS records.
A Sona account: an active Sona account with tracking pixel access.

Setting up your CNAME

Work through these steps to configure your custom tracking domain:

Log in to your DNS provider. Sign in to the platform where your domain is managed, for example GoDaddy, Cloudflare, or Namecheap.
Create a subdomain. We recommend using sl as the subdomain. For example, if your domain is mystore.com, the subdomain should be sl.mystore.com. Set the target value to t.sonalabs.com.
Turn off DNS proxying, if applicable. In providers like Cloudflare, make sure the proxy is turned off for the CNAME record.
Wait for DNS propagation. Changes typically take up to 24 hours to propagate.
Verify your CNAME in Sona. Go to General > Tracking Pixel > CNAME Setup, enter your subdomain under Add CNAME, then click Verify DNS. Once verified, the status shows a green checkmark and your code snippet automatically updates to use your custom CNAME.
Click Save. Finalize your CNAME configuration by saving the changes.

Best practices

Understanding CNAME records: a CNAME (Canonical Name) record creates an alias that points your subdomain to another domain. Here it makes your tracking appear to come from your own domain while actually routing to Sona's servers.
Subdomain naming: use short, memorable subdomains like sl, track, or analytics. Avoid www or subdomains that might conflict with existing services, and keep it professional and brand-appropriate.
Cloudflare users: always disable the proxy (the gray cloud icon) for CNAME records.
Corporate domains: you may need IT approval for DNS changes.
Propagation timing: changes can take anywhere from a few minutes to 24 hours depending on your provider.

FAQs

What is a CNAME record?

A CNAME, or Canonical Name, record is a DNS entry that creates an alias pointing one subdomain to another domain. For Sona tracking, it makes your tracking script appear to load from your own subdomain while routing to Sona's servers, which improves reliability and reduces blocking.

Why do I need to disable the proxy on Cloudflare?

When Cloudflare's proxy (the orange cloud) is enabled on a CNAME record, it routes traffic through Cloudflare rather than resolving directly to Sona's servers, which can prevent verification and tracking from working. Setting the record to DNS-only (the gray cloud) lets the CNAME resolve correctly.

How long before my custom domain works?

DNS changes can take anywhere from a few minutes to 24 hours to propagate, depending on your provider. After propagation, verify the subdomain in Sona under General > Tracking Pixel > CNAME Setup. Once it shows a green checkmark, your snippet updates automatically to use the custom domain.

Installation: Create a Custom Tracking Domain (CNAME)