Collect signals
The loader reads 30+ signals. IP, user agent, browser traits, request timing and more. No personal data is stored.
How it works
Configure advertising traffic checks. Monitor campaign quality or stop publisher ad tags from loading when visits fail your rules.
AdPurify evaluates traffic and ad quality signals around your existing ad tags. The right operating mode depends on how you use the platform.
Advertisers use monitor mode to record verification results while ad delivery continues. Publishers can use blocking mode to stop selected visits before the wrapped ad tag runs, preventing the ad request from reaching their ad server.
Open the dashboard. Pick the rules per slot. See all rules.
Use the wrapper generator. Replace your original tag. AdPurify runs the code inside only when the visit is clean. Here's an example:
<div class="adpurify-verified-ad">
<template data-adpurify-tag>
googletag.cmd.push(function () {
googletag.display('div-gpt-ad-top');
});
</template>
<script async src="https://{your_name}.adpurify.io/js"></script>
</div>
Clean and blocked visits show up in minutes. Compare them with your ad server numbers.
Four steps run on every visit. Scans are evaluated on edge nodes worldwide for reduced latency.
The loader reads 30+ signals. IP, user agent, browser traits, request timing and more. No personal data is stored.
Signals go to the geographically closest of 6 data centers. Latency stays low worldwide.
The rule engine checks the visit against your rules. It returns allow or block.
In monitor mode, the original tag runs and the result is logged. In publisher blocking mode, a blocked visit skips the original tag.
Want to see the rules you can set? Browse the rules →
Manage wrappers and rules from your own tools with the REST API. Pull reports into your own dashboards. Connect AI assistants to your account with the MCP server.
The REST API and MCP server are included in the Professional and Enterprise plans.
The original ad tag never runs. No ad request is sent. The visit is logged as blocked.
AdPurify fails open. After a 300 ms timeout, your tag loads as normal.
No. You only wrap the tag on the page. Your ad server setup stays the same.
Yes. Any tag that runs in the browser can be wrapped, including GAM, CM360, and Prebid.js.