Sign up

Custom domain (bypass ad blockers)

Serve the tracking script from your own subdomain so ad blockers can't block it — and recover the visitors they quietly hide.

Ad blockers and privacy extensions block requests to known analytics domains like piqo.app. When the tracker loads from piqo.app/piqo.js, a slice of your visitors — often 10–40% for developer or tech-savvy audiences — is never counted. Serving the script from your own subdomain (e.g. data.yoursite.com) makes it first-party: blockers have nothing to match, so those visits come back. HTTPS is set up automatically — you only add one DNS record.

1. Add the domain in Settings

Open your site's Settings → Custom domain and enter the subdomain you want to use:

  • Pick something neutral, like data.yoursite.com or metrics.yoursite.com.
  • Avoid stats., analytics., and tracking. — a few blocklists flag those prefixes.

2. Add the DNS record

Piqo shows you a CNAME record to add at your DNS provider. Add it exactly as displayed.

On Cloudflare? Set the record to DNS only (grey cloud), not Proxied — otherwise Cloudflare serves it from your own zone and verification can't complete.

3. Verify

Click Check status. Once DNS propagates (usually a few minutes), the TLS certificate is issued automatically and the domain flips to Active. You don't manage any certificates — renewals are handled for you.

4. Update your tracking snippet

When it's active, Settings shows your new snippet. Replace the existing one so the script loads first-party from your domain:

<script defer src="https://data.yoursite.com/piqo.js" data-site="YOUR_SITE_KEY"></script>

That's it — pageviews and events now flow through your own domain, out of reach of domain-based blockers.

Good to know

  • Works with both cookie and cookieless modes — still no PII, no third-party scripts.
  • Your existing analytics data is unaffected; this only changes where the script loads.
  • You can disconnect any time in Settings — tracking falls back to the piqo.app endpoint, and your old snippet keeps working.
A custom domain defeats domain-based blocking, which is the vast majority of it. A handful of aggressive lists also match on generic paths — that's rarer and a separate topic. For most sites a custom domain recovers nearly all the blocked traffic.
NextCookie consent