From finding Bot visits
to taking action in your ad platforms.
Detect Bots visiting your site and use ad platform integrations to prevent repeat delivery. Start by installing the tag and setting up platform exclusions.
Is your ad budget paying “non-humans”?
Retargeting chases anyone who visited once and re-shows ads to them. If that first visit was a Bot, you keep paying to chase the Bot. Bots get smarter daily, spoofing IPs and browser names to slip past legacy defenses.
What changes once it’s in
Review visit verdicts, their reasons and integration status. You can also estimate Bot-equivalent amounts using your own assumptions.
Ad budget keeps leaking to Bots
- A Bot’s first visit is counted as a “prospect”
- Retargeting re-shows ads chasing that Bot
- Spoofed IP/browser name slips past legacy tools
- No visibility into why the waste happened
See Bot detection and connections together
- Review Normal traffic, Suspicious traffic and Bot
- Connect eligible Bot visits to ad platforms
- Review connection status, then check exclusions in Ads Manager
- Inspect reasons for individual verdicts
Estimate from assumptions
Bot-equivalent value under your assumptions
Estimate value from assumed clicks, CPC and Bot share. These are not measured results.
Bot-equivalent value (assumptions)
¥400,000
/ month
Per year ¥4,800,000
A simulation calculated as clicks entered × assumed Bot rate × CPC entered. This is not actual ad spend or measured savings.
What you can do in your day-to-day work
Find Bot and suspicious visits
Browser and browsing information are considered together. Detection of every Bot is not guaranteed.
Help avoid excluding real visitors
A short visit or a shared network alone does not make a visit a Bot. Visits without sufficient grounds are not forced into ad exclusions.
Understand the verdict
Review the reasons for each visit’s classification and use them when explaining results to clients.
View details for technical teams
Review the available evidence from several angles
These groups explain the information used for Bot detection. After detection, ad-platform connections depend on connection settings, destinations, pauses and duplicate prevention.
Automation declarationsObservation
Records of automated browser control are assessed alongside other information for Bot detection.
Behavior analysisObservation
Interaction, dwell and scrolling provide supporting evidence. A short visit alone does not mean Bot.
Request frequency
Observe concentrated requests within an internally managed window. Frequency alone does not authorize excluding users on shared networks or in-app browsers.
Network context
Use context such as data-center networks as supporting information. IP or network characteristics alone do not establish a Bot verdict or authorize media exclusion.
Browser information consistency
Compare available user-agent, platform and Client Hints information. Missing information is not treated as observed evidence.
Known Bots and verified crawlers
Check evidence of known automation. Verified official crawlers are separated from Bot counts and media exclusion.
Decoys (invisible traps)
Interactions with elements not used during normal browsing are assessed with other information for Bot detection. They are not required again after a Bot has been detected.
Interaction records and missing information
Review interaction types, timing and scrolling. An ad click ID or a short visit alone does not establish a BOT verdict; insufficient evidence remains unclassified.
Transport information not currently collected
TCP TTL, TLS JA4 and HTTP/2 SETTINGS require edge collection and are not currently collected in this deployment.
Connect Bot detections to your ad platforms
Use Bot detections in Meta, TikTok and Yahoo! JAPAN Ads / SmartNews exclusion workflows. For Google Ads, automatically sync IP exclusion candidates after checks for shared-network risk.
Bot visits detected
Check Bot detection, connection settings, destinations, pauses and duplicates
Start platform connection
Start a connection to the configured ad platform
Platform configuration
Build an exclusion list from the signal, add it to the campaign’s exclusions
Apply ad exclusion
Retargeting is reduced when the platform receives the signal and applies it through audience and campaign settings
Connect detected Bot visits to platforms such as Meta and TikTok to prevent repeat ad delivery (Pro and above). Set up an exclusion audience in the ad platform. Check connection status in your dashboard.
IP exclusion candidates are checked for shared-network risk and synced to Google Ads hourly. Review candidates, sync results and connection status by account. Available on Starter and above.
Help avoid excluding real customers
Help avoid excluding real customers
It has exclusion logic so real readers arriving via in-app browsers (LINE / Instagram / Yahoo!) or shared mobile networks aren’t mistaken for Bots by a shared IP.
This is not an achieved result or guarantee. We evaluate BOT errors using sessions confirmed as Human, reporting sample sizes, environment composition and confidence intervals. Natural production traffic is not automatically labeled Human.
Safeguards protect in-app browsers and shared networks. Eligible exclusions added by AdFraud are removed during a successful Google Ads sync. Check connection errors on the Integrations page.
Compare evidence under the same conditions
Compare detection reasons, platform connections and ease of daily review. You can measure the same site alongside your existing tools to see how AdFraud fits your workflow.
| Dimension | AdFraud Shield | What to verify in other products |
|---|---|---|
| When it protects | Classify visits and integrate when platform-specific safety conditions passCapability | Distinguish detection, sending, platform receipt and exclusion application |
| Catching new Bots | Use browser and interaction evidence; continue independent accuracy evaluationCapability | Compare recall and human false positives on the same evaluation set |
| Explaining a flag | Discloses each reason (white box)Capability | Check per-visit explanations and how missing evidence is reported |
| Known-Bot coverage | Distinguish known Bots and verified crawlers; evaluate unfamiliar traffic using observed evidence | Check Bot families covered, update methods and evaluation scope |
Compare the same sites over the same period. Detection counts alone do not establish accuracy. Check each provider’s current features and terms.
We collect “Bot clues,” not people’s names
We do not collect visitors’ names, email addresses or phone numbers. We handle technical information on the site operator’s behalf and normally delete raw visit data after seven days. Aggregated statistics, ad-platform connection records and invalid-click evidence have separate retention rules.
Name, email, phone, purchase/payment information
Raw visit data is normally deleted after seven days. Aggregates, media safety checks, ownership and unresolved operations, and invalid-click evidence have separate retention rules. See the privacy policy for details.
Notifying visitors and maintaining your own privacy policy remain the site operator’s responsibility.
Start measuring for free, then choose a plan for your needs
<script async src="…adfraud-shield.min.js" data-site-id="…" data-endpoint="…"></script>Try one store first, side-by-side with your current tools?
Try it on your site to review Bot traffic, detection reasons and the platform connection workflow.
Start measuring for freeBot counts are detection results. Amounts are estimates based on your inputs or CPC, not measured savings. Check ad exclusion status in your platform’s Ads Manager.