TrueTracked

Documentation

Setup guides and reference documentation to help you get the most from TrueTracked.

Custom Domain Setup

Set up a custom subdomain to enable fully first-party tracking. This improves cookie lifetime, bypasses most ad blockers, and ensures more accurate attribution data.

Prerequisites: You need access to your domain's DNS settings (usually through your domain registrar or DNS provider like Cloudflare, GoDaddy, or Namecheap).

Why Use a Custom Domain?

  • Bypass ad blockers: Requests to your own subdomain are treated as first-party and won't be blocked by most ad blockers.
  • Extended cookie lifetime: First-party cookies set by your subdomain last longer than third-party cookies, improving cross-session tracking.
  • Better data accuracy: Fewer blocked requests means more complete attribution data.

Step 1: Choose a Subdomain

Pick a subdomain on your primary domain. For example, if your site is mystore.com, you might use st.mystore.com or data.mystore.com.

Important: Avoid words like track, analytics, pixel, or tag in your subdomain name. Some ad blockers maintain keyword-based blocklists and may still block these.

Step 2: Add the Domain in TrueTracked

  1. Go to Settings > Custom Domain in your TrueTracked dashboard
  2. Enter your chosen subdomain (e.g., st.mystore.com)
  3. Click Add Domain
  4. You'll see a DNS record that you need to add to your DNS provider

Step 3: Configure DNS

Add a CNAME record in your DNS provider:

TypeHost / NameValue / Target
CNAMEst (your subdomain prefix)edge.ttrkd.com

How to add DNS records by provider:

  • Cloudflare: Go to DNS > Records > Add Record. Set Type to CNAME, Name to your subdomain prefix, and Target to edge.ttrkd.com. Turn off the proxy (orange cloud) — it must be DNS-only (gray cloud).
  • GoDaddy: Go to DNS Management > Add New Record. Select CNAME, enter the host and value.
  • Namecheap: Go to Advanced DNS > Add New Record. Select CNAME, enter the host and target.

Step 4: Wait for Verification

After adding the DNS record, TrueTracked will automatically verify the domain. This typically takes a few minutes, but DNS propagation can take up to 24 hours depending on your provider.

You can check the status in Settings > Custom Domain. The domain will show as:

  • Pending: DNS record not yet verified. Double-check your CNAME configuration.
  • Active: Domain is verified and SSL certificate has been provisioned. You can start using it.

Step 5: Update Your Pixel Code

Once your domain is active, update your tracking pixel to use the custom domain. Go to Settings > Pixel Installation, select your custom domain from the dropdown, and copy the updated script.

The script URL will change from:

https://t.ttrkd.com/tt.js?w=YOUR_WORKSPACE_ID

To:

https://st.mystore.com/tt.js

With a custom domain, the workspace ID is no longer needed in the URL — it's resolved from the domain automatically.

Troubleshooting

  • Domain stuck on Pending: Verify that your CNAME record points to edge.ttrkd.com and DNS proxy is disabled (if using Cloudflare). Use a tool like dig st.mystore.com CNAME to verify DNS propagation.
  • SSL errors after activation: SSL certificates are provisioned automatically. If you see errors, wait a few minutes and try again. If the issue persists, delete and re-add the domain.
  • Cloudflare proxy conflict: If you use Cloudflare for your main domain, make sure the CNAME record for your tracking subdomain has the proxy disabled (gray cloud icon). The orange cloud proxy will interfere with SSL provisioning.

FAQ

Can I use multiple custom domains?

Yes, depending on your plan. Each domain can serve as an independent tracking endpoint for different sites or brands.

Will removing a custom domain break my tracking?

If you remove a custom domain, any pages still using it will stop collecting data. Update your pixel code to use the default domain or another active custom domain before removing.

Does this work with Shopify?

Yes. After setting up your custom domain, update the tracking script in your Shopify theme to use the new domain URL.