Custom ingest endpoint

By default the PixelFox tag loads from, and sends events to, PixelFox's own hostname. Ad blockers and browser privacy lists target exactly such third-party tracking hosts. A custom ingest endpoint moves both onto your domain, t.yourstore.com, so tracking requests look like your site's own traffic. Keys, dashboards, destinations and the event contract stay the same.

Set up

1. Add a CNAME record at your DNS provider. Any subdomain works (t., track., data.) as long as it is on the same registrable domain as your storefront. Keep it DNS-only if your provider offers proxying.

   Type	Name	Value
   CNAME	t	connect.pixelfox.app

2. Save the hostname in PixelFox. The fastest place is during onboarding: the Install step has an optional card, Serve from your own domain, that shows your exact record, pre-fills t.<your domain> and switches the install snippet to your domain the moment you save. For an existing site, open Dashboard → Settings → First-party Domain, enter the hostname and press Save.

3. Use the updated snippet. Both the script and the event host now point at your domain:

   <script src="https://t.yourstore.com/pixelfox.min.js"
           data-pixelfox-key="pfx_live_…"
           data-pixelfox-host="https://t.yourstore.com" defer></script>

   If you installed the tag before saving the domain, re-paste the snippet from the Settings tab. The certificate is issued automatically on the first request, with nothing to upload or renew.

Verifying the setup

The First-party Domain tab checks the hostname whenever you open it, and on demand with Check again:

• DNS record - the CNAME resolves to PixelFox. Flattened A records, as Cloudflare creates, are detected too. If the record points elsewhere, the check shows what it currently resolves to.
• HTTPS / certificate - the hostname answers over TLS. A fresh record can sit at DNS OK · certificate pending for a minute, because the certificate is issued on the very first request.

The badge turns Active when both pass. Not detected means the record has not propagated yet; DNS changes can take up to 48 hours, usually minutes. Clear removes the hostname; the standard PixelFox host keeps working.

What changes

• Script and events are first-party. t.yourstore.com/pixelfox.min.js and t.yourstore.com/v1/ingest are not on third-party blocklists.
• Vendor tags follow. With a custom ingest endpoint saved, the tag loads Google Tag Manager, gtag, the Meta Pixel, the TikTok Pixel and the Reddit Pixel through your domain as well, and their collect calls go the same way. See Custom loader for the details and the two things it cannot proxy.
• Attribution cookies live two years. Safari and Firefox cap cookies written by JavaScript at about seven days, which silently truncates any attribution window longer than a week. On your own hostname PixelFox refreshes _fbp, _fbc and _ga from the server on every event, with a two-year lifetime on your registrable domain. _fbc is rebuilt from a landing fbclid when the cookie is missing, so paid clicks keep their click id for the whole window. On a two-part suffix such as .com.bd the cookies stay on the tracking hostname itself.
• Same-site identifiers. The tag's own identifiers live under your domain.

Using it from the SDKs

Every integration takes the hostname where it takes the API key:

Hosted forms on your domain

Full-page surveys and forms can be served from your domain too. In the survey editor, under Hosted form link, set a Custom form domain such as forms.yourstore.com, CNAME it (DNS-only) at connect.pixelfox.app, and every active form on the site becomes https://forms.yourstore.com/<key>. The setting is site-wide and the certificate is issued the same way. See Surveys and forms.

Notes

• One tracking domain per site, and a hostname can belong to only one site. The hostname must be on your own domain; names under pixelfox.app are refused.
• A site can have a custom ingest endpoint and shared sGTM hostnames; they are claimed separately and both CNAME at the same target.
• Certificates are only issued for saved hostnames. Pointing DNS at PixelFox without saving the domain does nothing.