Protect any website with one line in the head
AdProtektor installs as one script tag in your site-wide head. It loads asynchronously and scores every visit for fraud. Your dashboard generates the snippet for each website and suggests the instructions for the platform it detects.
Free trial, no credit card required.
How to connect Any website
Copy the snippet
Add your website, then copy the snippet from Settings → Install code. Always use the one from your dashboard, because some platforms get a variant.Paste it in the head of every page
Put it in the shared layout, theme header or site-wide code setting, as early in the head as practical. Your ad landing pages need it, not only the home page.Publish
Site builders and Google Tag Manager stage changes until you publish. An unpublished change is the most common reason verification fails.Verify
Visit your site in a normal browser tab. The status in Settings → Install code changes to verified within seconds of the first page view arriving.
What the integration does
- One script tag in the head of every page, loaded asynchronously. Optional modules load only when you turn them on.
- No account key in the standard tag: the script resolves your website from the hostname it runs on, so it is safe in a shared theme.
- Guided installs for Wix, Squarespace, Webflow, BigCommerce and Google Tag Manager, plus any custom HTML site.
- Single-page apps are tracked across route changes without re-firing the script.
- Optional first-party tracking: a small PHP proxy serves the script and relays its requests through your own domain under /_adp, so ad-blocker domain filters do not match it.
- Search engine and AI crawlers are recognised and always whitelisted, never blocked.
- Server-to-server conversion ingestion through a custom API for ConversionOS, for conversions that never touch a browser.
Any website questions
Where exactly should the script go?
In the head, as early as practical, on every page. A script in the footer, or one fired late, can miss short visits, and short visits are what bot traffic often looks like.
Can I install it with Google Tag Manager?
Yes. Create a Custom HTML tag with the snippet and fire it on All Pages, or on the Initialization trigger, which runs earlier. Tag Manager loads the script slightly later than a direct tag, so a direct install in the head gives the best coverage.
How does first-party tracking work?
You host the AdProtektor PHP proxy on your own server, route the /_adp path to it, set your site key in it, and load the script from /_adp/t.js. Ad-block filter lists block AdProtektor by domain, so serving the same script from your own domain avoids those rules.
Does the first-party proxy keep every signal?
The visitor IP, browser fingerprint and behaviour are preserved. The TLS fingerprint (JA4) is only forwarded when your site sits behind an edge such as Cloudflare or nginx that provides it; without one, it is absent for proxied traffic.
Will it slow my site down?
The script loads asynchronously and optional modules load only when enabled. Tracking still adds some work, so measure performance on your own site with the features you use.
Other ways to connect AdProtektor
Set up AdProtektor on your own traffic
Install the script, connect the integrations you use and review the evidence behind any block whenever you need it.
Free trial, no credit card required.