Custom CNAME (first-party tracking)

By default, events go to track.pixelmili.com. When you route them through your own subdomain instead — track.yourshop.com — two things get better: and ad blockers that work from domain blocklists stop matching your tracking.

How it works

You add a CNAME DNS record pointing your subdomain to our edge. We issue a TLS cert (via Let's Encrypt) on-demand. Browsers see a first-party request to your own domain — everything else flows identically.

Step 1 — Create the CNAME record

In your DNS provider (Cloudflare, Namecheap, GoDaddy, etc.):

DNS record

Type:   CNAME
Name:   track
Value:  edge.pixelmili.com
TTL:    Auto (or 300)
Proxy:  DNS only (important on Cloudflare — grey cloud, not orange)

Step 2 — Verify in PixelMili

Dashboard → Domains → [your domain] → Enable custom CNAME.
Enter the subdomain you chose, e.g. track.yourshop.com.
Click Verify. We'll check DNS + issue a cert (usually takes 30–120 seconds).

Step 3 — Update the script

Swap the src to your subdomain:

html

<script async src="https://track.yourshop.com/t.js"
        data-tracking-id="pm_YOUR_TRACKING_ID"></script>

Why it matters

Ad-blocker bypass — blocklists match connect.facebook.net, not track.yourshop.com.
Cleaner reports — Meta assigns higher match quality to first-party requests.