See which analytics tools your users never reach.

Measure block rates per provider, get alerted when they spike, and see the vetted fix for each one. Open-source client, first-party reporting, no personal data.

Free for 10,000 events/monthUnder 2 KB gzippedOpen source on GitHub

From missing data to the fix

The measurement is only the beginning.

Know what is missing, learn when it changes, and decide what is worth recovering.

01

Measure the gap

See the actual block rate for GA4, PostHog, Segment, Optimizely, and every provider in your stack.

See the live data
02

Catch the spike

Turn a one-time check into continuous monitoring. Pro alerts reach email, Slack, or your webhook.

Compare plans
03

Fix what matters

Rank blocked providers by impact and follow a vetted first-party or server-side remediation path.

See how it works

First-party by design

Two small pieces. One honest rate.

The client checks your providers. Your server forwards the result with the API key, so the browser never posts to a third-party measurement domain that blockers can hide.

  1. 1

    Install the client

    Choose only the providers your app actually uses.

  2. 2

    Add your own route

    Keep the API key server-side and the reporter first-party.

  3. 3

    Read the rate

    The dashboard starts ranking providers once samples arrive.

Pick your framework
client.ts + app/api/block-rate/route.ts
1// Client — posts to your own route.
2import { BlockRate, beaconReporter } from "blockrate";
3
4new BlockRate({
5 providers: ["optimizely", "posthog", "ga4"],
6 reporter: beaconReporter("/api/block-rate"),
7}).check();
8
9// Server — attaches your key and forwards the result.
10import { createBlockRateHandler } from "blockrate/next";
11
12export const POST = createBlockRateHandler({
13 forward: { apiKey: process.env.BLOCKRATE_API_KEY! },
14});

Trust the number

Detection is hard. We maintain it for you.

A confident-looking wrong rate is worse than no rate. blockrate publishes only after a minimum sample floor and tests every provider shape as the underlying tools change.

  • Provider-specific probes test the real CDN, not a generic ad-block bait file.
  • Post-load checks distinguish a loader stub from a bundle that actually executed.
  • First-party reporting keeps blocked visitors in the measurement instead of silently losing them.
Read the methodology

Find the gap before it grows.

Start free with 10,000 measured events each month. No credit card required.

Start measuring free