Custom loader
Load the FunnelTrack pixel from your own subdomain instead of funneltrack.com. Same pixel, same events, same destinations — served from a hostname you control so it looks and behaves like a first-party script.
Why use a custom loader
Three concrete wins, all of which directly affect attribution quality and conversion match rates.
- Defeats privacy-browser blocklists. Brave, Safari, Firefox Strict, uBlock Origin, AdGuard, and the rest maintain filter lists that block known tracking domains and generic
/collect-style endpoints. When the pixel loads from your own subdomain (e.g.load.ft.acme.com), those lists no longer match — the request looks like a first-party script owned by the site itself. - First-party cookies that actually last. Safari ITP caps third-party cookie lifetime at 7 days. When the FunnelTrack pixel runs from funneltrack.com, the
_ftsession cookie + every platform cookie (_fbc,_gcl_aw,_ttp, etc.) get capped. With a custom loader, the cookies are set on the customer's own domain — full 90-day lifetime, no ITP cap.
Setup
Three steps. ~5 minutes of your time plus ~15 minutes of DNS propagation + TLS cert provisioning.
Enable Custom Loader on the Pixel page
Go to Tracking pixel in your dashboard. Find the Enable custom loader card and flip the toggle on. A text input appears.
Enter your tracking subdomain
Type the subdomain you want to use, e.g. ft.yourdomain.com. Click Add domain. FunnelTrack registers the hostname pair (collect + loader) at Cloudflare for SaaS and shows you the two CNAME records to add at your DNS provider:
| Type | Host | Value |
|---|---|---|
| CNAME | ft.yourdomain.com | c.edge.funneltrack.com |
| CNAME | load.ft.yourdomain.com | l.edge.funneltrack.com |
Note: load. is added automatically — you only entered the base subdomain; both records are derived from it.
Add the two CNAMEs at your DNS
Open your DNS provider (Cloudflare, Route 53, GoDaddy, Namecheap, etc.) and add both CNAME records exactly as shown in the dashboard. Don't enable proxy (orange cloud) if you're on Cloudflare DNS — these records need to resolve all the way through to our edge.
The dashboard polls Cloudflare every 15 seconds. Once both records propagate and Cloudflare finishes issuing TLS certs (typically 5–30 minutes), the status pill on the card flips from Verifying to Active.
When status flips to Active — update your FunnelTrack script deploy
The pixel script shown on the Pixel page automatically updates to load from your custom hostnames. Copy it and replace the existing FunnelTrack snippet everywhere on your site — every page, plus your GTM Custom HTML tag if you deploy it through GTM. Until you swap the snippet, pages keep loading the pixel from funneltrack.com.
Troubleshooting
Common issues and what they mean.
Status stuck on Verifying
DNS propagation hasn't finished. CNAMEs typically propagate within 5–30 minutes but some DNS providers can take several hours. Look up your hostname at dnschecker.org and confirm it shows the CNAME chain ending at our edge hostname (c.edge.funneltrack.com or l.edge.funneltrack.com).
Status flipped to Error
Cloudflare reported a permanent failure. Read the inline error message — most commonly it means one of the CNAMEs is pointing at the wrong target. Double-check the exact values in the CNAME table on the Pixel page and re-add at your DNS provider, then click Verify.
Custom loader is Active but my snippet still loads from funneltrack.com
You need to re-copy the snippet from the Pixel page and replace every existing installation of the old snippet. The pixel page generator emits your custom hostnames once verified, but it's your site's installed snippet that determines what URL the browser actually fetches.
I want to remove the custom loader
Click the toggle on the Custom Loader card to flip it off. The dashboard will confirm and tear down the Cloudflare hostnames. Your pixel snippet immediately falls back to loading from funneltrack.com — re-copy and re-deploy the snippet. You can re-enable custom loader at any time with the same or a different hostname.