Custom tracking domain

Run pb.js and ingest on your own subdomain so cookies are truly first-party — they survive Safari's 7-day cap and ad blockers can't blanket-block them.

Why it matters

By default, pb.js and its events run on AdsPing’s host — a third-party context to your site. Two things happen there:

  • Safari / Brave / Firefox cap client cookies at ~7 days. The _pb_id visitor cookie pb.js writes gets evicted, so a returning visitor after a week looks brand new.
  • Ad blockers can target a shared third-party host.

A custom tracking domain (track.yourdomain.com) makes both the script and every event first-party. AdsPing then sets _pb_id as a server-side cookie that browsers keep for up to 2 years, and the traffic rides your own domain.

Combined with AdsPing’s identity graph — which re-matches cookieless events by hashed email/phone — you get durable cookies and recovery when a cookie is missing. Very few setups do both.

Availability

Custom tracking domains are included on the Pro plan and above (one domain on Pro, unlimited on higher tiers). If your pixel is on Starter, the card on the pixel’s Settings tab will prompt to upgrade.

Set it up

  1. Open your pixel → Settings Custom tracking domain.
  2. Enter a subdomain you control, e.g. track.yourdomain.com, and click Add domain.
  3. At your DNS provider, add the two records AdsPing shows you:
    TypeHostValue
    CNAMEtrack.yourdomain.comingest.adsping.io
    TXT_adsping-challenge.track.yourdomain.comadsping-verify-…
  4. Click Verify. Once DNS has propagated (usually a few minutes), the domain turns active and SSL is issued automatically.
  5. Copy the install snippet again from the pixel page — it now loads from your domain. Replace the old one on your site.
The CNAME routes traffic to AdsPing; the TXT record proves you own the domain. Both are required before a domain can go active — this prevents anyone else from pointing a domain at your pixel.

How it works

Nothing about your event code changes — pb.js derives its endpoint from wherever the script itself is loaded. Once the snippet loads from track.yourdomain.com, both the script and every adsping('track', …) call are first-party automatically. Your destinations (Meta, TikTok, Google Ads) receive the exact same events — only the cookie durability and delivery path improve.

Was this page helpful?