Proxy Admaxxer Through Cloudflare Workers

Running /js/script.js and /api/event through your own domain closes the gap that most browser-based ad blockers exploit: they block requests to known third-party tracking hostnames, not to your own domain. A Cloudflare Worker lets you relay those two paths on the edge — zero latency added, no origin server needed.

Why Proxy the Pixel?

• Ad-blocker bypass. Requests to admaxxer.com may be blocked by uBlock Origin, Brave, and similar tools. Requests to yourdomain.com are not.
• First-party data. The browser sees a same-origin request; cookies set on the event endpoint carry your domain's SameSite context.
• No DNS penalty. Cloudflare Workers run at the edge closest to your visitor — the additional hop is typically under 1 ms.

Prerequisites

• A Cloudflare account with your domain proxied through Cloudflare (orange cloud in DNS).
• Workers Bundled or Paid plan (the Free plan allows 100,000 requests/day which is enough for most sites).
• Your Admaxxer workspace ID, available in Connections › Install.

Step 1 — Create the Worker

In the Cloudflare dashboard go to Workers & Pages › Create application › Create Worker. Name it admaxxer-proxy and deploy the default hello-world script first so you have a worker to edit.

Step 2 — Paste the Worker Script

Open the worker editor and replace the entire script with:

const UPSTREAM = 'https://admaxxer.com';

export default {
  async fetch(request) {
    const url = new URL(request.url);

    // Only proxy the two Admaxxer paths; pass everything else through
    if (
      url.pathname === '/js/script.js' ||
      url.pathname.startsWith('/api/event')
    ) {
      const target = new URL(url.pathname + url.search, UPSTREAM);
      const proxied = new Request(target.toString(), {
        method: request.method,
        headers: request.headers,
        body: request.method !== 'GET' ? request.body : undefined,
        redirect: 'follow',
      });
      return fetch(proxied);
    }

    // All other paths are served by your origin
    return fetch(request);
  },
};

Step 3 — Add a Route

In the worker settings click Triggers › Add route. Enter:

yourdomain.com/js/script.js
yourdomain.com/api/event*

Set the Zone to your domain. Save. Cloudflare will now send matching requests to the worker instead of your origin server.

Step 4 — Update the Snippet in Admaxxer

Go to Connections › Install and enable Custom proxy domain. Enter https://yourdomain.com. Admaxxer regenerates the snippet so that script.js and /api/event resolve to your domain.

Step 5 — Test

Open a browser DevTools Network tab and reload your site. You should see a 200 for https://yourdomain.com/js/script.js and a 200 (or 204) for /api/event POST requests. Then run:

curl -I https://yourdomain.com/js/script.js

Expect: HTTP/2 200, content-type: application/javascript.

Troubleshooting

• 404 on the route. Verify the route pattern matches — Cloudflare route wildcards use *, not regex. Make sure your domain is proxied (orange cloud), not DNS-only (grey cloud).
• CORS errors. Add Access-Control-Allow-Origin: * in the worker response headers if your pixel loads cross-origin. Most setups don't need this.
• Worker returns 524 timeout. The upstream call to admaxxer.com exceeded 30 seconds. This should not happen in normal operation — check the Admaxxer status page.
• Events not appearing in dashboard. Confirm the workspace ID in the snippet matches your workspace. Use the Live Events tab in Admaxxer to watch events arrive in real time.

Rollback

Delete the route in Workers › Triggers or set the worker to return fetch(request) unconditionally. Then in Admaxxer disable the custom proxy domain to revert the snippet to pointing at admaxxer.com.

Other Proxy Guides

Vercel · Next.js · Nuxt · Netlify · WordPress · Apache · NGINX

See also: Connections › Install for the base snippet.