Browser API Blocking: No Tracking Before Consent

Consenta blocks Push Notifications, Background Sync and Cache API until the user has consented — automatic restoration after consent included.

Get started — from 3 €/mo Explore features

14-day money-back · Cancel anytime · GDPR-compliant · Local in WordPress

Consenta WordPress Cookie Consent Dashboard

What is Browser API Blocking?

Modern browser APIs like Push Notifications, Background Sync and the Cache API enable persistent tracking — even without classic cookies. Consenta blocks these APIs completely in full-consent mode until the user has explicitly consented. This ensures that no service worker, push subscription or cache-based fingerprinting takes place before consent. After consent, all APIs are automatically and transparently restored.

Features

Browser API Blocking in Detail

Block Push Notifications

Notification.requestPermission is blocked until consent is given. This prevents push notification popups from being triggered before consent.

Block Background Sync

SyncManager.register is deactivated until the user has consented. No service worker can silently initiate background synchronizations.

Control Cache API

caches.open is blocked, preventing cache-based fingerprinting and unwanted data persistence in the browser cache before consent.

Block Push Subscriptions

PushManager.subscribe is blocked until consent is given. No push service can subscribe the user without their knowledge.

Intelligent Whitelist

Technically necessary caches are not blocked. The whitelist allows prefixes like "consenta", "wp-" and "workbox" so WordPress core and plugin caches continue to work.

Automatic Restoration After Consent

Once the user has consented, all blocked APIs are fully and transparently restored — without page reload or manual configuration.

How it works

Browser API Blocking in 3 Steps

Activate full-consent mode

Activate full-consent mode in Consenta. Browser API Blocking is automatically part of this mode — no additional configuration needed.

APIs are automatically blocked

On page load, Consenta overrides browser APIs via JavaScript proxy. Calls to Notification, Push, Sync and Cache are intercepted until the user consents.

Consent given — APIs released

Once the user consents, all blocked APIs are restored. Pending calls are automatically replayed, new calls can proceed immediately.

Pricing

Subscribe monthly or pay once.

Monthly Yearly 3 months free

STARTER

Starter

€

/month

cancel monthly · 1 WordPress site

€

/year

2.25 €/mo · 3 months free

✓ 1 WordPress site
✓ Consent dialog & banner
✓ Cookie & script blocking
✓ Cookie scanner
✓ Google Consent Mode v2
✓ IAB TCF 2.2
✓ GPC signal (Do Not Sell)
✓ Live editor (colors, logo)
✓ Import/export
✓ Browser API Blocking
✗ Webhooks
✓ Email support

Buy now

Cancel anytime

Questions about Browser API Blocking

Which browser APIs are blocked?

Consenta blocks four APIs in full-consent mode: Notification.requestPermission (push popups), PushManager.subscribe (push subscriptions), SyncManager.register (background sync) and caches.open (Cache API). Whitelisted prefixes like "consenta", "wp-" and "workbox" are exempt from cache blocking.

What happens after consent?

All blocked APIs are automatically and fully restored. No page reload is required. Pending API calls can be replayed immediately.

Does this affect my website's performance?

No. The API blocking is implemented via lightweight JavaScript proxies set up in milliseconds. Whitelisted caches like WordPress core caches or Workbox are not affected.

Is Browser API Blocking a paid feature?

No. Browser API Blocking is included in all Consenta plans — including the free plan. It is active by default in full-consent mode.

No API tracking before consent.

4 APIs blocked · Intelligent whitelist · Automatic restoration · HTTPS-only · GDPR-compliant

Get started — from 3 €/mo All features

14-day money-back guarantee · Cancel anytime · Available in 30+ languages