Plausible Analytics for Astro with Cloudflare Workers

Plausible Analytics is a privacy-first, open-source alternative to Google Analytics. It’s lightweight (under 1KB script), uses no cookies, and tracks no personal data. With over 19,000 paying subscribers and 260 billion pageviews tracked, it’s the most popular privacy-focused analytics tool among developers.

You can self-host Plausible on your own servers. Check Install Plausible With One Click for a quick setup, or use one of the best self-hosted server panels for easy deployment.

Astro is a web framework built for speed, and it now runs natively on Cloudflare. After Cloudflare acquired Astro in January 2026, the @astrojs/cloudflare adapter dropped Pages support entirely. v13+ deploys exclusively to Cloudflare Workers. You can deploy your Astro site on Cloudflare or build a free blog with Astro & Cloudflare to get started. For a deeper look at framework choices, see the Astro vs Next.js vs TanStack Start comparison.

In this guide, you’ll set up Plausible Analytics for your Astro site using Cloudflare Workers as a proxy. The result: accurate analytics that bypass ad blockers, served from your own domain, on a free plan.

Why proxy Plausible Analytics through Cloudflare Workers?

Ad blockers and privacy-focused browsers routinely block requests to plausible.io. This can cause you to lose 20-30% of your analytics data. If you’re using tools like NextDNS or browser-level ad blockers on your own devices, you already know how aggressively they block analytics scripts.

A proxy solves this by routing Plausible requests through your own domain. To your visitors’ browsers, the analytics script looks like part of your site, not a third-party tracker. Ad blockers can’t distinguish it from regular site traffic.

For more on blocking ads and trackers at the DNS level, see how to block ads and tracking with DNS protection.

Why use Cloudflare Workers instead of redirects?

If you’re deploying to Cloudflare Pages, you might think you can use the _redirects file to proxy Plausible requests. You can’t. Cloudflare Pages only supports relative-path redirects. It cannot proxy to external URLs.

Attempting to add a proxy redirect like this will fail:

Found invalid redirect lines:
09:59:12.187	  - #1: /js/script.js https://domain.com/js/plausible.outbound-links.js 200
09:59:12.187	    Proxy (200) redirects can only point to relative paths. Got https://domain.com/js/plausible.outbound-links.js
09:59:12.187	  - #2: /api/event https://domain.com/api/event 200
09:59:12.187	    Proxy (200) redirects can only point to relative paths. Got https://domain.com/api/event

Cloudflare Workers don’t have this limitation. They can fetch from any external URL and return the response, making them the right tool for proxying Plausible on Cloudflare.

Proxying Plausible through Cloudflare Workers (step by step)

Cloudflare Workers offers a free plan with 100,000 requests per day. That’s more than enough for most sites. All you need is a free Cloudflare account.

Step 1: Create a Worker

Go to the Workers & Pages section in your Cloudflare dashboard and click Create application. Then click Create Worker in the Workers tab. Give your worker a name that doesn’t suggest analytics. Something like theme-assets or cdn-helper works well. Click Deploy.

Create Cloudflare Worker:

Deploy Cloudflare Worker:

Step 2: Add the Worker code (ES Modules)

Click Edit Code, delete the default code, and replace it with the code below.

// Replace 'pa-XXXXX.js' with your site-specific script ID
// Find it in Plausible: Site Settings → General → Data Snippets
const ProxyScript = 'https://plausible.io/js/pa-XXXXX.js';
const ScriptPath = '/theone/script';
const Endpoint = '/theone/event';

export default {
  async fetch(request, env, ctx) {
    ctx.passThroughOnException();
    const url = new URL(request.url);
    const pathname = url.pathname;

    if (pathname.startsWith(ScriptPath)) {
      return getScript(request, ctx);
    } else if (pathname === Endpoint) {
      return postData(request);
    }

    return new Response(null, { status: 404 });
  }
}

async function getScript(request, ctx) {
  let response = await caches.default.match(request);
  if (!response) {
    response = await fetch(ProxyScript);
    ctx.waitUntil(caches.default.put(request, response.clone()));
  }
  return response;
}

async function postData(request) {
  const req = new Request(request);
  req.headers.delete('cookie');
  return await fetch('https://plausible.io/api/event', req);
}

// Replace with your self-hosted Plausible domain
const ProxyScript = 'https://plausible.yourdomain.com/js/pa-XXXXX.js';
const ScriptPath = '/theone/script';
const Endpoint = '/theone/event';

export default {
  async fetch(request, env, ctx) {
    ctx.passThroughOnException();
    const url = new URL(request.url);
    const pathname = url.pathname;

    if (pathname.startsWith(ScriptPath)) {
      return getScript(request, ctx);
    } else if (pathname === Endpoint) {
      return postData(request);
    }

    return new Response(null, { status: 404 });
  }
}

async function getScript(request, ctx) {
  let response = await caches.default.match(request);
  if (!response) {
    response = await fetch(ProxyScript);
    ctx.waitUntil(caches.default.put(request, response.clone()));
  }
  return response;
}

async function postData(request) {
  const req = new Request(request);
  req.headers.delete('cookie');
  return await fetch('https://plausible.yourdomain.com/api/event', req);
}

Edit Worker:

Add Code:

Once you’ve added the code, click Save and Deploy in the top right.

Step 3: Verify the Worker is working

Test your worker by accessing it directly:

https://your-worker-name.your-cloudflare-username.workers.dev/theone/script

You should see JavaScript code returned (the Plausible script). If you get a 404, double-check the ScriptPath variable in your worker code matches the URL path you’re testing.

Step 4: Run the proxy as a subdirectory

Running the proxy under a subdirectory of your main domain (e.g., example.com/theone/) is better than using a separate subdomain. It keeps requests first-party, which avoids cookie restrictions and looks cleaner in network logs.

To set this up, add a Worker route in the Routes section of your Worker settings:

Route: *example.com/theone/*

Replace theone with whatever path segment you chose in your worker code. Select your domain in the zone dropdown.

Step 5: Add the Plausible snippet to your Astro site

Add this snippet to your Astro site’s <head>. In Astro, you can place it in your main layout file (e.g., src/layouts/Layout.astro):

<script async src="https://yourdomain.com/theone/pa-XXXXX.js"></script>
<script>
  window.plausible=window.plausible||function(){(plausible.q=plausible.q||[]).push(arguments)};
  plausible.init=plausible.init||function(i){plausible.o=i||{}};
  plausible.init({
    endpoint: "https://yourdomain.com/theone/event"
  })
</script>

Replace the following:

• yourdomain.com: your actual site domain
• theone: the subdirectory path you configured in Steps 2 and 4
• pa-XXXXX.js: your site-specific script ID from Plausible (Site Settings → General → Data Snippets)

The endpoint URL must match the Endpoint variable in your Worker code, and the script src must match the ScriptPath. The script URL goes through your Worker (serving the cached Plausible script), and the endpoint URL routes analytics events through your Worker to Plausible’s API.

You should now have Plausible Analytics proxied through Cloudflare Workers, served from your own domain.

Plausible pricing (2025)

Plausible offers several cloud tiers. All plans include the core analytics features: pageviews, visitors, bounce rate, visit duration, referral sources, and more.

Higher pageview tiers are available at each level. The Enterprise plan includes a Managed Proxy where Plausible handles the proxy for you via a CNAME record. No Worker needed.

If you want to skip the cloud pricing entirely, the Community Edition is free.

Plausible Community Edition vs Cloud

Plausible Community Edition (CE) is a free, self-hosted version under the AGPL license. It follows an open-core model. CE includes the core analytics engine, but some advanced features are exclusive to the cloud Business and Enterprise plans.

Troubleshooting common issues

What’s new in Plausible since 2023

Plausible has shipped a lot of features since this article was first published. Here are the highlights:

If you’re also working on your Astro site’s performance, check how to optimize Astro build speeds or migrate Astro to Bun on Cloudflare for faster builds.

Frequently asked questions