First-party proxy

Ad blockers and browser tracking prevention block requests to analytics hosts they recognize. A visitor who blocks them is invisible to your funnels, and their purchase is credited to no campaign. Route the SDK's requests through a path on your own domain instead, such as https://www.example.com/vh, and they reach Voidhash like any other request your site makes.

The proxy forwards requests unchanged to https://api.voidhash.com. Everything the SDK sends, both API calls under /api/v1/ and events under /i/v1/, goes through it.

export default {
  async rewrites() {
    return [{ source: "/vh/:path*", destination: "https://api.voidhash.com/:path*" }];
  },
};

{
  "rewrites": [{ "source": "/vh/:path*", "destination": "https://api.voidhash.com/:path*" }]
}

export default {
  async fetch(request: Request): Promise<Response> {
    const url = new URL(request.url);
    url.hostname = "api.voidhash.com";
    url.pathname = url.pathname.replace(/^\/vh/, "");
    return fetch(new Request(url, request));
  },
};

location /vh/ {
  proxy_pass https://api.voidhash.com/;
  proxy_set_header Host api.voidhash.com;
  proxy_ssl_server_name on;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

const voidhash = createVoidhashClient({
  baseUrl: "https://www.example.com/vh",
  publishableKey: "vh_pk_…",
});

Moving an existing site to the proxy keeps returning visitors as they are: their anonymous ID, consent choice, session, and queued events are stored per project, not per baseUrl.

Location behind a proxy

Voidhash derives a visitor's coarse location from the address of the request that reaches it. Behind a proxy, that address is the proxy's, so events sent through a proxy currently carry the proxy's location rather than the visitor's. Campaign attribution, sessions, identity, and revenue are unaffected.

Only some traffic through the proxy

To send only analytics through the proxy and keep API calls direct, set analytics.baseUrl instead:

const voidhash = createVoidhashClient({
  analytics: { baseUrl: "https://www.example.com/vh" },
  publishableKey: "vh_pk_…",
});

The proxy then only needs to forward /vh/i/v1/…. Ad blockers that block the API host still block feature flags and identify(), so forwarding everything is usually the better choice.

Self-hosted Voidhash

A self-hosted deployment already runs on a domain you control. Point baseUrl at it, or put it behind the same kind of proxy with your deployment's URL as the destination.