This guide walks you through setting up a custom tracking domain (CNAME) to improve your tracking reliability and deliverability. By using your own subdomain instead of a generic tracking URL, you'll reduce the likelihood of your tracking being blocked by ad blockers or security software. With this setup, you'll have improved data collection and a more presentable tracking approach.
When to Use This
When to Use This
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
Prerequisites:
Access to your domain's DNS management (through providers like GoDaddy, Cloudflare, Namecheap, etc.)
Administrative permissions to modify DNS records
An active Sona account with tracking pixel access
Step-by-Step Instructions
Step-by-Step Instructions
Configure a Custom Tracking Domain (CNAME)
Step 1: Log in to your DNS provider
Step 1: Log in to your DNS provider
Sign in to the platform where your domain is managed (e.g., GoDaddy, Cloudflare, Namecheap).
Step 2: Create a subdomain
Step 2: Create a subdomain
Recommended: use
slas the subdomain.Example: If your domain is
mystore.com, the subdomain should besl.mystore.com.Set the target value to
t.sonalabs.com.
Step 3: Turn off DNS proxying (if applicable)
Step 3: Turn off DNS proxying (if applicable)
In providers like Cloudflare, ensure the proxy is turned off for the CNAME record.
Step 4: Wait for DNS propagation
Step 4: Wait for DNS propagation
It typically takes up to 24 hours for changes to propagate.
Step 5: Verify your CNAME in Sona
Step 5: Verify your CNAME in Sona
Go to General > Tracking Pixel > CNAME Setup in the Sona platform.
Enter your subdomain under Add CNAME, then click Verify DNS.
Once verified, the status will show a green checkmark and your code snippet will automatically update to use your custom CNAME.
Step 6: Click Save
Step 6: Click Save
Finalize your CNAME configuration by saving the changes.
Key Concepts / Best Practices
Key Concepts / Best Practices
Understanding CNAME Records: A CNAME (Canonical Name) record creates an alias that points your subdomain to another domain. In this case, it makes your tracking appear to come from your own domain while actually routing to Sona's servers.
Subdomain Naming Best Practices:
Use short, memorable subdomains like
sl,track, oranalyticsAvoid using
wwwor subdomains that might conflict with existing servicesKeep it professional and brand-appropriate
DNS Provider Considerations:
Cloudflare users: Always disable the proxy (gray cloud icon) for CNAME records
Corporate domains: You may need IT approval for DNS changes
Propagation timing: Changes can take anywhere from minutes to 24 hours depending on your provider