How it works

DataUnlocker allows you to set up an end-to-end protected networking layer to protect your marketing tools, analytics, and any network requests from being blocked or modified by ad blockers, privacy software, VPNs, etc.

Once DataUnlocker is installed on your website, you will be able to configure JavaScript and network protection for specific network requests. Protected resources doesn't contain recognizable patterns that blockers can utilize, as well as some of the JavaScript magic is used to ensure the environment isn't compromised.

DataUnlocker integrates with your existing code, data collection methods, or compliance standing – it doesn't change the way your website or analytics tools are programmed.

Architecture

DataUnlocker embeds into one of your JavaScript bundles, creating the secure networking channel. Once installed, you can configure what traffic (network requests) go through this channel in the Network Protection.

How DataUnlocker protects your web app from ad blockers

From the web application perspective, DataUnlocker initilizes and enables its protection asynchronously.

Sequence diagram showing how DataUnlocker loads analytics resources over the network

The diagram above illustrates the sequence of network requests and Defender actions during page load. There's the following sequence:

  1. Website HTML starts loading. The browser requests your website's main HTML document (GET site.com/).

  2. Defender script begins loading. A JavaScript file containing Defender is requested (GET site.com/script.js) and begins execution.

  3. Defender initializes and loads configuration. Upon execution, Defender initializes and loads its Network Protection configuration asynchronously (GET site.com/abcd/z2nxiv0..).

  4. Patching and environment checks. Defender applies necessary JavaScript patches and performs environment checks to detect ad blockers, privacy tools, or hostile conditions.

  5. Secure Enclave loads protected resources. Defender's Secure Enclave code is invoked starts fetching additional asynchronous resources, applying protection where required.

  6. Defender readiness notification. Once fully initialized, Defender signals readiness to your web application so it can fully initialize.

  7. Remaining resources load normally. Any website assets that do not require protection (theme.css, chunk.abc.js, etc.) load without modification.

Key takeaway: Defender initializes early in the page load process, applies targeted protection to sensitive network requests, and ensures all other resources load without delay or interference.

If your website uses Cloudflare as a transport endpoint, you get the minimal possible latency of Defender async initialization, where Secure Enclave code execution adds no more than a few hundreds of milliseconds of latency.

Web app protection at a glance

Once DataUnlocker Defender is integrated into your app, selected third-party requests on your domain are encoded and proxied, bypassing interference from ad blockers and network filters. The proxy is end-to-end tamper-proof—any attempt to modify it will pause your web application, preventing blockers from loading content improperly.

This built-in safeguard makes it virtually impossible for ad blockers to target your site at any point in the future, while having no impact on your website's users, even those with ad blockers enabled.

Explore the diagram below to see how DataUnlocker operates under the hood.

How DataUnlocker works scheme

Network protection is enabled once Defender initializes. You can configure which network requests are protected in the network protection settings.