HapiGuard – Invalid Click Protection for AdSense, Ad Manager & Auto Ads

HapiGuard detects and blocks invalid ad clicks in real-time, protecting your AdSense and Ad Manager account from policy violations caused by click bombing, bot traffic, and accidental repeated clicks.

All core protection features are free and fully functional with no account required. The plugin stores blocked click data locally in your WordPress database and shows you a 7-day summary right in the admin dashboard — no external service needed.

Optionally, you can connect a free RevHapi account to add cloud-powered features such as geo-blocking, email alerts, and advanced analytics. These are provided by an external service that processes data on RevHapi servers. The core plugin works entirely without it.

How it works

1. Install and activate the plugin
2. HapiGuard immediately begins monitoring ad clicks on your pages
3. When a visitor exceeds your configured click limit within the time window, they are blocked from seeing ads
4. The plugin records each blocked click in your local WordPress database
5. Your Protection Summary shows blocked clicks and total click counts from the last 7 days — no account needed

Core features (free, no account needed)

• Real-time click detection and blocking
• Works with AdSense, Auto Ads, and Google Publisher Tag (GPT / Ad Manager)
• Preemptive CSS hiding — ads are hidden synchronously for blocked visitors before any network request
• Vignette and interstitial ad blocking — blocked visitors cannot see overlay ads
• Configurable click limit, time window, and ban duration
• Local 7-day stats: blocked clicks and total click count shown in admin without any external service
• Client-side fingerprinting using canvas, screen resolution, and timezone — no server round-trip required for blocking decisions

Optional cloud features — external RevHapi service

The RevHapi cloud service is a separate, optional offering. Connecting a free RevHapi account at app.revhapi.com adds:

• Server-side page view and session tracking
• Geo-blocking — block or allow specific countries
• Email alerts when a click spike is detected
• Anomaly detection across visitors
• Advanced analytics: page views, sessions, avg time-to-click

These features require server-side processing (cross-site fingerprint correlation, email delivery, geo IP lookups) that cannot be performed by the WordPress plugin alone, so they are provided as an external service under Guideline 6. The plugin’s local click protection is fully functional without them.

Third-party service disclosure

When you enter a RevHapi API key, the plugin sends anonymised click event data (fingerprint hash, page URL, click count — no IP addresses or personal data) to app.revhapi.com.

• RevHapi Privacy Policy
• RevHapi Terms of Service

RevHapi is operated by Waldroid Digital Ltd. The core plugin functionality works entirely without connecting to any external service.

1. Upload the plugin folder to /wp-content/plugins/
2. Activate the plugin through the Plugins menu in WordPress
3. Go to HapiGuard in the WordPress admin sidebar
4. You will immediately see local protection stats — no configuration needed
5. Set your preferred click limit, time window, and ban duration in the Settings card
6. Optional: enter a RevHapi API key to also send anonymised click data to the external RevHapi cloud service for cross-site analytics, geo-blocking and email alerts. The plugin works fully without this.

1. 

   HapiGuard settings page showing local protection stats and settings

2. 

   Protection Summary with 7-day blocked click count (no account needed)

1.0.4

• When a site is connected to the optional external RevHapi cloud service, rule settings (enable, click limit, window, ban duration) are now pulled from there and the local form is rendered read-only, with a notice linking back to the cloud dashboard. This removes the silent drift that could happen when the same setting was edited in both places.
• Local fallback values stay in lock-step with the cloud (refreshed every minute), so the in-WP local-mode counters continue to use the correct thresholds.
• No change in behaviour when the plugin runs disconnected from the cloud — every field stays fully editable in the WordPress admin.

1.0.3

• Fixed: PHP parse error on the Protection Summary heading caused by an unescaped apostrophe — the plugin could not be activated.
• Reworded all UI copy that referenced “unlocking” features to make clear that the external RevHapi service is optional and that every feature shipped in the plugin code is fully functional without any account, license, or API key.
• Replaced the 🔒 padlock icon next to the cloud-only features list with ☁️ so it reads as “cloud service” rather than “locked”.
• Added an explicit “External cloud service — separate from this plugin” label above the RevHapi promo card.
• Dashboard widget CTA renamed from “Unlock Advanced Protection” to “Learn about RevHapi Cloud”.

1.0.2

• Local stats now shown without any account — blocked clicks and total clicks from the local database
• RevHapi cloud analytics (page views, sessions, geo) clearly separated and labelled
• Plugin URI updated
• Text domain aligned with plugin slug

1.0.1

• Security and escaping improvements
• Improved readme documentation

1.0.0

• Initial public release
• Real-time click detection and blocking
• AdSense, Auto Ads, and Google Publisher Tag support
• Preemptive CSS hiding and vignette ad blocking
• Optional RevHapi integration for geo-blocking, email alerts, and analytics