Overview
This guide walks you through the steps to manually install the Sona SDK and to configure a Custom Tracking Domain (CNAME) to improve data capture. You will learn how to set up the Sona tracking pixel, understand why using a custom CNAME enhances data accuracy, and see how to install the script directly in your website's HTML. With this guide, you will be ready to implement first-party, cookieless web visitor tracking and to boost the reliability of your visitor insights.
Configure a Custom Tracking Domain (CNAME)
Step 1: log in to your DNS provider. Sign in to the platform where your domain is managed, such as GoDaddy, Cloudflare, or Namecheap.
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. In providers like Cloudflare, ensure the proxy is turned off for the CNAME record.
Step 4: wait for DNS propagation. It typically takes up to 24 hours for changes to propagate.
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. Finalize your CNAME configuration by saving the changes.
Manually install the Sona SDK
Step 1: select your setup type. Under Setup for Websites, choose whether the script should capture form data. The tracking code will adjust based on your selection.
Step 2: copy the tracking script. Click Copy to Clipboard to grab the code snippet.
Step 3: paste the script in your HTML. Place the script inside the <head> tags of your website's HTML code.
Step 4 (optional): set up for web apps. If you are tracking user activity in a login-based web app, select Setup for Web Apps and follow those instructions.
Key concepts and best practices
Manual installation avoids common tracking disruptions caused by ad blockers.
Using a custom CNAME improves script deliverability and reduces the risk of script blocking.
Always test your implementation in a staging environment before pushing live.
FAQs
Why should I configure a custom CNAME for the tracking pixel?
Why should I configure a custom CNAME for the tracking pixel?
A custom CNAME points a subdomain you own, such as sl.yourdomain.com, at Sona's tracking infrastructure. This improves script deliverability and reduces the risk of the script being blocked, since it is served from your own domain rather than a shared third-party one.
How long does it take for my CNAME to work after I set it up?
How long does it take for my CNAME to work after I set it up?
DNS changes typically take up to 24 hours to propagate. After making the change with your DNS provider, go to General > Tracking Pixel > CNAME Setup in Sona and click Verify DNS. Once verified, the status shows a green checkmark and your code snippet automatically updates to use the custom CNAME.
Why install the Sona SDK manually instead of using a tag manager?
Why install the Sona SDK manually instead of using a tag manager?
Manual installation, placing the script directly in your website's HTML head tags, avoids common tracking disruptions caused by ad blockers that can interfere with tag manager-loaded scripts. Always test your implementation in a staging environment before pushing it live.