ClickHelm

ClickHelm watches who arrives on your site from Google Ads and works out which of them are costing you money without ever becoming a customer. No limit, no time limit, no card, and nothing to unlock. There is no visit cap, no site count and no key to enter. Everything described below runs on every install, for as long as you keep the plugin. It recognises the person, not the address. Identity comes from a device fingerprint resolved on your own server, so the same visitor is still the same visitor after clearing their storage, switching browser, or moving from home WiFi to mobile data. An address on its own tells you little: it changes when a phone's data is turned off and on. What it shows you

• Dashboard — the traffic you paid for, what it cost, and which visitors are worth a second look today, ranked, each with the reasoning in plain language
• Visitors — everyone seen, searchable and filterable, with the evidence behind each score: the fingerprint, the addresses, the networks, and what they did on each visit
• Google Ads — spend, waste and profit per campaign, ad group, keyword and placement, with your own click log beside the clicks Google actually charged you for
• The exclusion list — every address worth excluding, ready to copy into Google Ads
• Possible Duplicates — fingerprints that probably belong to someone you already know

What this edition does not do It does not block anyone. It shows you who is costing you money and leaves the acting to you. Copying addresses into Google Ads by hand works, and is what the exclusion list is for. Automatic blocking, your own rules, the breakdown reports and heatmaps are a separate plugin sold from clickhelm.com. None of that code is in this one — it is not here and switched off, it is not here at all. What it measures Revenue is read from the actual WooCommerce order on the server, so it counts even when a shopper blocks scripts, and it is the real total rather than an estimate. That is what makes genuine per-campaign profit and loss possible. Calls, WhatsApp taps, form submissions, thank-you pages and your own buttons all count as leads, so the plugin works for a service business as well as a shop. Email A weekly or monthly report summarising what the plugin saw, what it cost you, and which visitors are worth a look, with a link straight to each one. Switch it on under Settings, and tell it not to write when there is nothing to say. Privacy Visitor data stays in your own database. One thing can leave it, and only if you say so: visitor IP addresses, for address classification. They go to api.clickhelm.com, which asks proxycheck.io and keeps none of them. It is off until you switch it on - the setup asks, in plain words, and Settings has the switch. Say so in your site's privacy policy if you do switch it on. Old data is cleaned up automatically on a schedule you set.

6.92.0

• Classifying a visitor's address is now off until you ask for it. The setup asks in plain words what is sent and what saying no costs, and Settings carries the switch. It was on from the first page view of a fresh install, which is what WordPress.org's guideline 7 forbids and what their review pulled us up on - rightly.
• Heatmaps are out of this edition entirely. The recording, the settings and the flag that held them shut are all gone from the file rather than disabled inside it.
• The plugin's own description on the Plugins screen described the paid edition - blocking, rules and automatic Google Ads exclusions, none of which are here. It describes this one now.
• This edition no longer deactivates another copy of ClickHelm, and no longer carries the code that did.
• The one script printed into the page markup moved into the plugin's own JavaScript file.
• Translations come from translate.wordpress.org for this edition, so no catalogues ship inside it and nothing loads them early.
• The readme no longer says the address record is used to count how many sites run the free edition. It is not, any more.

6.91.0

• Tested against WordPress 7.1.
• The plugin is credited to the ClickHelm account, which owns it, with its developer listed alongside so support questions reach a person.
• Fixed: an admin page load could erase the campaign behind arrivals it had already recorded. The backfill that reads ad parameters out of each stored landing-page URL wrote its answer for every field, including the ones the URL said nothing about - so any arrival whose campaign came from somewhere else lost it. Measured on a test site: one page load erased the campaign, ad group, keyword, match type, network and device from 487 of 1,689 arrivals. It now fills blanks and never overwrites.
• Fixed: the free edition's tab strip linked to three screens it does not have. Reports, Rules and Your plan were still printed above every screen; opening one answered "you are not allowed to access this page".
• The free edition no longer carries the paid features at all. Blocking, rules, reports and heatmaps used to ship inside it behind a licence check, and the month was capped at 500 visits. Both are gone from this build: the code is not there to unlock, and nothing counts down. What the free edition does, it does without limit.
• Percentages, and the three words under every dashboard figure - no change, nothing to compare, flat - are translated. They were English in every language.
• The renewal-date arithmetic no longer depends on PHP's default timezone.
• A search containing an apostrophe now finds what it should on the Visitors screen.
• Escaping, unslashing and the code comments that explain both, throughout - for the WordPress.org review.

6.90.2

• Housekeeping only: the plugin is credited to its developer’s WordPress.org account. Nothing in the plugin itself changed.

6.90.1

• Fixed: a keyword running in more than one ad group reported clicks as coming from before ClickHelm was installed. The Keywords tab counted only the last ad group’s share of the charged clicks, so the rest were labelled "before tracking started" on sites where every click was inside the window. The rest of the 6.89.0 keyword fix was correct; this one column is built elsewhere and was missed.
• Fixed: every install and every upgrade logged two database errors. Comments written inside the table definitions were read as columns, producing two invalid statements that added nothing — harmless, but the first thing anybody debugging a real problem would meet. The releases before 6.90.0 are in changelog.txt, which ships with the plugin.