Custom Tracking Domain (CNAME) Overview

What is a Custom Tracking Domain?

With Rockerbox, you can use a Custom Tracking Domain so Rockerbox trackers and pixels are loaded from your website’s domain (e.g. rb.mysite.com) instead of getrockerbox.com.

What are the benefits of using a Custom Tracking Domain?

A Custom Tracking Domain improves Rockerbox’s ability to accurately track users & connect all their touchpoints. Because a Custom Tracking Domain will load trackers and drop cookies in a “first-party” context using your own domain, browsers will enable those cookies to stick around longer and be more easily accessible.

How do Custom Tracking Domains work?

You will have to add a CNAME record to point a subdomain of your site (e.g. rb.mysite.com) to a special endpoint provided by Rockerbox. This will enable all traffic to the subdomain to be forwarded to Rockerbox, while still appearing to browsers/ad blockers like a built-in part of your site.

A Canonical Name, or CNAME record, is a type of Domain Name System (DNS) record that maps an alias name to a true canonical domain name. Rockerbox Your system administrator, or whoever has set up your domain name, can help create a CNAME record.

The subdomain will only need to be added to your external DNS, not your internal DNS.

How do I set this up for my account?

1) Go to Settings > Account in your dashboard and click “Start Set Up” under the Custom Tracking Domain section

2) Enter a subdomain of your website that you would like to use for the custom tracking domain. It must be unique & new (not already in use). For example, if your website is example.com, you might choose rbx.example.com for your custom tracking domain.

The domain you enter must be in all lowercase characters. Capital letters are not allowed.

3) Click the “Set Up Instructions” button to view the CNAME record you need to add in your DNS provider.

In certain DNS providers, you may need to only enter the host subdomain (the first section before the dot), e.g. rbx.example.comrbx.

If you need help adding a CNAME, here are instructions for some popular domain providers: • GoDaddyGoogle DomainsNamecheapCloudflare

TTL: Certain domain providers will require a TTL. Please set this to the lowest value that the DNS provider will allow. If a custom value is available for seconds set it to 60 seconds.

4) Once you have added the CNAME record in your DNS provider, go back to Rockerbox and click “Test” under Custom Tracking Domain.

If everything is set up correctly, you will see a “Verified” message.

Please note that DNS records may take up to 24 hours to update, so you may need to come back and try testing again if it doesn’t work at first.

Updating Existing Pixels

Now that your Custom Tracking Domain is configured, you will need to update the pixels on your website to use the new domain you just set up.

Shopify Updates Automatically
If you are using a Shopify-hosted site and don’t have any custom pixels or conversions, the pixel will be automatically updated via the Rockerbox-Shopify integration.

If you are running a headless Shopify site or have custom pixels implemented in GTM, please continue reading for the updates you’ll need to make.

You can grab your updated pixel by heading over to Settings > Pixels and copying the code to use in your website or tag manager.

Note that the URL used in the code is now using your Custom Tracking Domain. All scripts and pixels will now use that domain for Rockerbox tracking.

If you are using Segment, please follow the instructions here to update your Rockerbox destination settings in Segment to use your custom tracking domain.

If you already have Rockerbox pixels on your site, you just need to update one of the fields in your code with the new script tag that uses your custom tracking domain. You can make this update across all your pixels without having to reimplement the entire thing.

This field you’ll need to update is a.src.

For example, if the field was originally: a.src="https://getrockerbox.com/assets/wxyz.v2.js"; then you will update that to: a.src="https://rbx.example.com/assets/wxyz.v2.js";


How did we do?