Description
Clicksora Click Fraud Protection connects a WordPress site to Clicksora, a click fraud protection service for Google Ads, Meta Ads and Microsoft Ads advertisers. Paste one Tracking ID and every paid click that lands on your site is scored as the page loads: the network it came from (home, mobile carrier, hosting or VPN), the device, whether the page actually rendered, how many times the same address or phone opened your ads, and whether the click ID was re-fired from somewhere else. Addresses that fail are blocked and, on the plans that include it, written to your Google Ads IP exclusion lists automatically, so the same address cannot cost you a second click.
The plugin itself is deliberately small. It adds the small Clicksora tracker (about 4 KB compressed) to the page head, a no-script fallback pixel, and a WooCommerce hook that reports real purchases. All detection, blocking and reporting happen in your Clicksora dashboard, not inside WordPress.
What you get
- Click scoring on the landing page — every click with a Google, Meta or Microsoft click ID is examined the moment it arrives
- Hosting, VPN, proxy and Tor detection — clicks from rented servers and anonymising networks are identified before they cost a second click
- Bot and headless-browser detection — automation that never renders the page or shows no human interaction is caught
- Repeat-click and click-burst rules — your own thresholds for how often one address or one phone may open your ads
- Automatic Google Ads IP exclusions — blocked addresses are synced to your campaigns (Professional plan and above); the Starter plan exports them for a manual sync
- Conversion verification — call, WhatsApp, form and purchase events are checked against the click that produced them; conversions judged fraudulent are never uploaded to Google
- Cache-safe — the tracker is emitted for every visitor, so full-page caches (WP Rocket, W3 Total Cache, LiteSpeed, Cloudflare APO) never strip protection; your own admin visits are filtered out server-side instead
- WooCommerce compatible — the order-received page reports the order value and currency to Clicksora, once per order
- AMP-aware — the external script is skipped on AMP requests, where it would be invalid; the no-script pixel still records the visit
- No code editing — install, paste the Tracking ID, save
How it works
- Install and activate the plugin.
- Enter your Clicksora Tracking ID (a 16-character code from your Clicksora dashboard).
- The tracker loads on every front-end page and sends the click, page-load and page-exit signals to Clicksora.
- Clicksora scores the click. Hosting networks, replayed click IDs and repeat clickers are blocked; genuine visitors from your market are never blocked on one click alone.
- Blocked addresses are synced to your Google Ads account as IP exclusions.
- You read everything — networks, devices, pages, calls — in the Clicksora dashboard, with the reason for every block.
Who it is for
- Businesses running Google Ads to a WordPress or WooCommerce site
- Agencies managing paid search for clients on WordPress
- Local service businesses in competitive markets, where competitors and paid clickers are a daily cost
- Anyone who wants to know what, exactly, is clicking their ads before paying for it again
What it is not
The plugin does not block visitors from reaching your site and does not change your pages. It records and reports; the blocking is done in Google Ads through IP exclusions, where it stops the next paid click. Clicksora is an independent service and is not affiliated with or endorsed by Google.
Pricing
Clicksora is a paid subscription with a 7-day free trial (a card is required and nothing is charged if you cancel before day 7) and a 14-day money-back guarantee. Plans start at $59 a month. Current prices are on clicksora.com/pricing.
External Services
This plugin connects to the following external services operated by Clicksora:
Clicksora Tracking API
- Service: Clicksora
- What it does: The plugin loads a lightweight tracking script (
https://app.clicksora.com/t.js) on your site’s frontend pages. This script analyzes incoming ad clicks to detect click fraud in real-time. It communicates with the following Clicksora endpoints:https://app.clicksora.com/api/track/click— click, page-load and page-exit signals used for fraud analysis.https://app.clicksora.com/api/track/pixel— a<noscript>fallback pixel for visitors with JavaScript disabled.https://app.clicksora.com/api/track/config— read on each page load to determine whether session replay is enabled for your account.https://app.clicksora.com/api/track/conversion— conversion events (for example WooCommerce purchases) when you or the plugin fire them.https://app.clicksora.com/api/track/session-recording— links a session replay to its click when replay is enabled.
- Data transmitted: Click and device metadata including IP address, user agent, referrer URL, UTM/GCLID ad parameters, a lightweight browser fingerprint, on-page interaction signals (scroll depth, mouse/keyboard activity), and timestamps. For WooCommerce conversions, the order total, currency and order ID are sent. No names, emails, or passwords are collected by the plugin.
- When data is sent: On every frontend page load. The tracker is emitted for all visitors (including logged-in admins) so it stays correct behind full-page caches. To keep your own visits out of your reports, list your office address under Internal IPs in the Clicksora dashboard: traffic from it is marked internal, never blocked and never counted as a paid click.
- Terms of Service: https://clicksora.com/terms
- Privacy Policy: https://clicksora.com/privacy
PostHog Session Replay (optional)
- Service: PostHog, loaded on Clicksora’s behalf.
- What it does: If — and only if — session replay is enabled server-side for your account (Pro/Enterprise plans),
t.jsadditionally loads the PostHog recording library fromhttps://us-assets.i.posthog.comand sends masked session recordings tohttps://us.i.posthog.com(or the PostHog host returned by/api/track/config). Recordings mask all input fields by default. If replay is disabled for your account, PostHog is never loaded. - Data transmitted (when enabled): Masked session recordings — page interactions, clicks, scrolls and network metadata — with input values masked. Controlled entirely from your Clicksora dashboard.
- Privacy Policy: https://posthog.com/privacy
Installation
- Upload the
clicksora-click-fraud-protectionfolder to the/wp-content/plugins/directory, or install directly through the WordPress plugins screen. - Activate the plugin through the Plugins screen in WordPress.
- Go to Settings → Clicksora in the WordPress admin.
- Enter your Tracking ID (a 16-character code such as
aB3dEf6hJ9kLmN2p). Find it in your Clicksora Dashboard → Settings → Protected Domains. - Click Save Tracking ID — you’re protected!
FAQ
Do I need a Clicksora account?
Yes. The plugin connects your site to Clicksora’s detection engine; the dashboard, the blocking and the Google Ads sync live there. Start at clicksora.com.
Where do I find my Tracking ID?
Log in to your Clicksora dashboard, open Settings → Protected Domains, and copy the 16-character Tracking ID for the domain this WordPress site serves.
Does the plugin slow my site down?
The tracker is about 4 KB compressed and is loaded in the page head so that a visitor who bounces in under a second is still recorded. Clicksora’s own marketing pages, which carry the same tracker, score 90+ on mobile in Lighthouse; the plugin adds no styles, fonts or images to the front end.
Does it block fraudulent visitors from my website?
No. The plugin records; Clicksora decides; Google Ads does the blocking through IP exclusions, which stop the same address from being served (and billed for) your ad again. Your pages are never altered and no visitor is turned away by the plugin.
Will it block my real customers?
Clicksora is built around not doing that. A click from a home or mobile address inside your target market is never blocked on one click alone; it needs hard evidence (a hosting network, a replayed click ID, a repeat pattern you set), and a verified conversion from an address lifts a block. The dashboard shows the reason for every block so you can judge it.
Does it track my own visits?
The tracker is emitted for everyone, including logged-in administrators, so that cached pages stay identical for all visitors. Your own addresses are filtered on Clicksora’s side: add them under IP Management → Internal IPs in the dashboard and they are recorded as internal traffic, never scored and never synced.
What ad platforms does it work with?
Google Ads (including the Google Ads IP exclusion sync), Meta Ads, Microsoft Ads, TikTok Ads and LinkedIn Ads clicks are recognised by their click parameters. Automatic exclusions are written to Google Ads; the other platforms are reported.
Does it work with WooCommerce?
Yes. On the order-received page the plugin reports the order total, currency and order number to Clicksora once per order, so a purchase can be verified against the click that produced it.
Does it work with caching plugins and CDNs?
Yes. The tracker is emitted for every visitor, so WP Rocket, W3 Total Cache, LiteSpeed Cache, Cloudflare APO and similar full-page caches serve the same HTML to everyone and protection is never stripped.
Is it GDPR compliant?
The tracker records click and device metadata (IP address, user agent, referrer, ad click parameters, on-page interaction) for fraud prevention, which is a legitimate-interest purpose; no contact details are read from your pages, and lead identifiers you choose to pass are hashed before storage. Session replay is off unless you enable it in the dashboard, and inputs are masked when it is on. Review Clicksora’s privacy policy and your own notice before enabling it.
Is my data safe?
Data is encrypted in transit and at rest and is only ever shown in your own dashboard. See the privacy policy and the security page.
The settings page says “not verified” — is something wrong?
No. The plugin can check that the Tracking ID is well-formed and that the tracker is reachable (the Test Connection button); it cannot check that the ID belongs to your account. Confirm that in the Clicksora dashboard, where your domain shows its first clicks within minutes of installing.
Screenshots




Changelog
1.9.2
- Readme corrected: the tracker is about 4 KB compressed (not 3 KB), and your own visits are kept out of reports through Internal IPs in the dashboard
- No change to the plugin’s code or behaviour
1.9.1
- Readme rewritten: what the plugin does and does not do, pricing and trial terms, GDPR and caching answers, platform list
- Screenshots added (settings, connection test, How It Works, Plugins list)
- Translation template regenerated from the 1.9 source
- No change to the plugin’s code or behaviour
1.9.0
- Fixed: Tracker and noscript pixel no longer skip output for logged-in administrators. That skip made the emitted HTML vary by login state, so under a full-page cache (WP Rocket/W3TC/LiteSpeed/Cloudflare APO) an admin-primed page could strip tracking for all visitors. Admin self-clicks are filtered by Clicksora server-side instead.
- Fixed: The tracking script is now skipped on AMP pages (which strip arbitrary scripts); the valid noscript pixel still covers AMP views.
- Fixed: The settings status box no longer claims “Protection Active” for any non-empty value. It distinguishes Not Connected, an invalid-looking Tracking ID, and a well-formed (but unverified) ID, and validates the real Tracking ID shape.
- Fixed: Hardened option sanitization against a crafted array Tracking ID (prevents a PHP 8 TypeError).
- Added: “Test Connection” button (admin-only, nonce-protected) that checks the Clicksora tracker is reachable and the Tracking ID is well-formed. It honestly notes it cannot verify the ID against your account.
- Added: WooCommerce purchase conversion tracking on the order-received page (fires once per order via
window.alm.purchase). - Added:
referrerpolicy="no-referrer-when-downgrade"on the noscript pixel so GCLID/UTM attribution survives for no-JavaScript visitors. - Improved: External Services / privacy disclosure now documents all tracker endpoints and the optional PostHog session-replay hosts (
us.i.posthog.com,us-assets.i.posthog.com). - Changed: “Requires at least” raised to WordPress 5.2 (required by
wp_body_open).
1.8.0
- Removed: Deprecated
load_plugin_textdomain()call — WordPress.org auto-loads translations since WP 4.6 - Improved: Plugin Check passes clean with zero errors
1.7.0
- Added:
load_plugin_textdomain()for proper translation loading - Added: Security
index.phpfiles to prevent directory listing - Fixed: Translation template
.potfile updated with all translatable strings - Fixed: Readme “free trial” corrected to “14-day money-back guarantee”
- Improved: Full WordPress Plugin Check compliance
1.6.0
- Fixed: Constants now wrapped in
defined()checks to prevent fatal errors - Fixed: Removed unnecessary escaping in
wp_enqueue_script()andwp_enqueue_style()parameters - Fixed: Settings section callback now uses a proper named function
- Fixed: Added
wp_unslash()before sanitizing form input - Fixed: Noscript pixel moved from
wp_headtowp_body_openwithwp_footerfallback - Fixed: Uninstall cleanup now uses
uninstall.phpinstead ofregister_uninstall_hook() - Fixed: CSS version synced with plugin version, removed duplicate header comments
- Fixed: Removed frontend CSS class from admin-only stylesheet
- Improved: Added
@packagePHPDoc tag to all files
1.5.0
- CRITICAL FIX: Removed
deferscript loading strategy — deferred scripts execute AFTER HTML parsing, causing fast-bouncing ad visitors to leave before tracking activates (ghost clicks). Script now loads in<head>for immediate execution. - Fixed: Tracking script URL reference updated to
app.clicksora.com/t.js - Fixed: Pixel URL updated to
app.clicksora.com/api/track/pixel
1.3.0
- Fixed: Text domain now correctly uses
clicksora-click-fraud-protectionthroughout - Fixed: All output is properly escaped using
esc_html(),esc_attr(), andesc_url() - Fixed: Script injection now uses
wp_enqueue_script()instead of direct HTML output - Fixed: Inline styles replaced with external CSS file (
css/admin.css) - Fixed: Added
rel="noopener noreferrer"to all external links - Fixed: PHPDoc blocks added to all functions
- Fixed:
register_setting()now uses array configuration format - Improved: Sanitization uses
sanitize_text_field()in addition to regex - Improved: Added proper
widthandheightattributes to noscript pixel image
1.2.0
- Added: Admin tracking skip — logged-in administrators are excluded from tracking
- Added:
deferattribute for non-blocking script loading - Added: Settings link on the Plugins page for quick access
- Added: How-it-works guide panel on settings page
- Added: Privacy policy link and version footer
- Added: Uninstall cleanup — removes all options when plugin is deleted
- Improved: Better input sanitization for Tracking ID
1.1.0
- Added: Noscript pixel fallback for visitors with JavaScript disabled
- Improved: Settings page UI with status indicator
1.0.0
- Initial release
- Tracking script injection via data-id attribute
- Settings page with Tracking ID input
