Proxy installation

Forward exact tracker and collector routes without exposing server credentials.

Forward exact tracker and collection paths

Use your own website’s /zijra/tracker.js, /zijra/api/collect and /zijra/api/privacy/withdraw routes to forward to the configured Zijra tracker and collector. Preserve the siteId query, exact UTF-8 body, browser Origin, original User-Agent, content type and response status. A custom relay must forward the browser’s User-Agent unchanged in the standard header; a server default such as Node.js, Python or an uptime agent may be filtered as automation. X-Original-User-Agent and similar override headers are not trusted. Never forward authorization cookies or server credentials from the analytics app.

Web server options

Next.js, Astro, Vue development proxies, Express, Django, Flask, FastAPI, Laravel and PHP can implement bounded server routes. Nginx, Caddy, Firebase Hosting and DigitalOcean can route those same exact paths to the HTTPS collector. Prefer an explicit route over an open URL proxy.

// Next.js rewrites: allow only tracker, collector and consent withdrawal.
async rewrites() { return [
  { source: '/zijra/tracker.js', destination: 'https://zijra.com/tracker.js' },
  { source: '/zijra/api/collect', destination: 'https://zijra.com/api/collect' },
  { source: '/zijra/api/privacy/withdraw', destination: 'https://zijra.com/api/privacy/withdraw' }
]; }

Set the tracker’s src to /zijra/tracker.js; it resolves collector and withdrawal paths relative to that script. Keep consent and privacy signals intact. Proxy traffic is observed at the collector edge and may locate the proxy rather than the original visitor. A browser header never becomes verified location.

Verify the route

Install the website-specific public ID, load a tracked page, inspect collector status and use Verify installation. A cached script or successful proxy response alone does not prove that an event reached the database.