ClickHelm
clickhelm.com
- Free plan
- Open source
- Web
- Self-hosted
What ClickHelm is
ClickHelm provides click-fraud protection that identifies devices and can block people rather than relying only on IP addresses. It assesses device characteristics, network type, click identifiers, and on-site behavior to assign a risk score. Blocking remains under customer control: nothing is blocked automatically unless a rule enables it. The free edition records and scores visitors, identifies VPNs and crawlers, and counts calls, WhatsApp messages, forms, and orders, but does not block visitors. Paid plans add blocking and may include Google Ads reporting, rules, alerts, or client reporting. Detection and blocking cover traffic from Google Ads, Meta, Microsoft Ads, TikTok, organic search, and direct visits; campaign spend matching applies to Google Ads. ClickHelm is available on the web or self-hosted on WordPress, requiring WordPress 5.6 or newer, PHP 7.2 or newer, and MySQL or MariaDB. Visitor data is stored in the customer's WordPress database, though addresses may be sent for network classification. ClickHelm begins recording after installation and does not import historical traffic. Paid plans start at $29 a month.
Who it suits
ClickHelm suits website operators who want to score suspicious traffic and control blocking through rules. Self-hosting is an option for customers running a compatible WordPress setup.
Good to know, and what to watch
- Scores traffic using device and network characteristics.
- Blocking can be controlled with customer-defined rules.
- Free edition identifies VPNs and crawlers.
- Visitor data stays in the customer's WordPress database.
- Detection covers several ad and non-ad traffic sources.
- The free edition never blocks visitors.
- Requires WordPress 5.6 or newer when self-hosted.
- Historical traffic is not imported.
- Address lookups may be sent for network classification.
Plans
Every plan and priceFree edition
Local
Starter
Growth
Free plan
The verdict
ClickHelm combines visitor scoring with rule-controlled blocking and supports traffic beyond Google Ads, while campaign spend matching is specific to Google Ads. Check the WordPress requirements, plan visit allowance, and lack of historical import before choosing it.
What the maker publishes
- Behavior signals
- It records time on page, scrolling, interactions, forms, calls, WhatsApp taps and WooCommerce orders as behavioral evidence. source
- Blocking control
- Nothing is blocked automatically unless the customer writes a rule enabling automatic blocking. source
- Changelog change
- Version 6.93.0 removed an automatic-blocking control from the edition that contains no blocking capability. source
- Click reconciliation
- Google Ads click identifiers are matched with clicks Google charged to distinguish arrived, missing and fabricated clicks. source
- Compliance statement
- The maker says its Google API data handling follows Google API Services User Data Policy and Limited Use requirements. source
- Crawler checks
- It compares claimed crawler identities with network ownership to identify impostor crawlers. source
- Data location
- Visitor records remain in tables in the customer’s own WordPress database rather than being proxied through ClickHelm. source
- Data storage
- Visitor data is stored in the customer's WordPress database and is not copied to ClickHelm. source
- Deployment model
- Installation is a WordPress plugin uploaded to the customer’s own hosting, with database tables created on activation. source
- Detection
- It measures device characteristics, network type, click identifiers and on-site behavior to produce a named risk score. source
- Developer API and SDKs
- The cited documentation describes Google Ads API use but does not publish a ClickHelm REST API, SDK or developer portal. source
- Device fingerprinting
- It identifies returning devices across browser changes, cleared storage and network changes instead of relying only on IP addresses. source
- Documentation
- The help material covers installation, tracking-template setup, missing data, risk scores and blocking behavior. source
- False-positive handling
- Possible device matches can be rejected manually, which immediately lifts a carried-over block. source
- Free edition
- The free edition records and scores visitors, identifies VPNs and crawlers, and counts calls, WhatsApp messages, forms and orders, but never blocks anyone. source
- Free-edition limitation
- The WordPress listing says the free edition records and explains traffic but does not block visitors; blocking and rules are in a separate paid edition. source
- Google Ads integration
- The optional Google Ads connection reads click reporting, campaign, ad group and keyword names, and cost figures once a day. source
- Google Ads integration
- The Google Ads connection reads click reports, campaign names, ad-group names, keyword names and cost figures once daily. source
- Google Ads write scope
- When enabled, ClickHelm can add its tracking template and maintain an account-level IP exclusion list, but it does not change campaigns, ads, budgets or bids. source
- Google data security
- Google access tokens are encrypted with AES-256-GCM during the server exchange and requests use TLS. source
- History limitation
- ClickHelm starts recording when installed and does not import historical traffic or backfill earlier data. source
- Independent directory status
- WP PlugIndex lists version 6.92.0, active status, testing through WordPress 7.1 and no WordPress.org ratings. source
- Independent installation count
- The WordPress developer profile lists fewer than 10 active installations. source
- Independent rating
- Rating on WordPress.org: 0 out of 5 from 0 reviews. source
Checked against the maker's pages on 14 Oct 2026.