ConvertNow Analytics

Changelog

1.5.0

The trust release: the plugin now tells you when it is not counting, and counts more exactly when it is.

Tracking health. Every hour the plugin checks that pageviews are arriving at your site’s usual rate, that yesterday was summarised and that scheduled maintenance runs; once a day it loads your home page to find the tracker and posts a signed test beacon, never recorded, to both collector addresses. Results are in Settings, in Tools, Site Health, and in one notice on the Stats screen while something is actually wrong. It runs once a minute after activation.

Alerts, by email and optionally to a webhook: tracking stopped, traffic well below or above the same hours on recent same weekdays, a wave of bots, AI assistant traffic moving sharply, and a surge of missing pages. Each is judged against the site’s own numbers, stays quiet below a minimum volume and fires at most once a day. Off until switched on.

Site icons. Referrers, campaign sources, assistants and crawler operators show the site’s own icon instead of a coloured letter, so Google, GitHub, ChatGPT and Claude no longer look alike. Icons for the major sites are fetched in the background on install, a site seen for the first time gets its icon within the hour, and everything is stored under uploads so an update never removes it.

The weekly email could skip weeks. A site whose scheduled run missed the send day rolled into the next calendar week and waited a week more; a mail server that timed out mid send left the week marked as sent. Both are fixed: a late run sends the week it missed, a failed send is retried, and the settings card shows when the next one goes and, after a failure, the reason the mail system gave. When WP-Cron has stopped altogether, the plugin now runs its own maintenance from visitor traffic where the server allows, and the health check says so.

Settings survive updates by construction. Every upgrade snapshots the settings and restores anything a step did not explicitly mean to change, a copy of the settings is kept and restored if the row is ever lost, and updating by deactivating and reactivating now runs the upgrade instead of skipping it. The shared dashboard link is kept and shown on the Settings screen for as long as it is valid, rather than shown once and never again, and it keeps working if the site’s security salts change.

Accuracy. Signed in administrators and editors were being counted: the beacon posts without a login cookie, so the collector saw everybody as anonymous. They are excluded again. Safari readers using iCloud Private Relay were refused as data centre traffic; Apple’s published exit list is now downloaded weekly and they are counted. Every pageview carries a small proof of work, a few milliseconds for a browser, so forged pageviews posted straight at the collector are refused; pages cached before this update are accepted for a week. Two pages opened in the same moment by one reader no longer start two visits.

Speed. A pageview is answered before the rest of WordPress starts (the cnwa_fast_collect filter turns this off for code that adds cnwa_should_count late, from inside init), which cut the time a collect request takes to about a third in testing and more than doubled how many a server can take at once. Refused requests are appended and folded into their counters in batches, so a crawler wave no longer queues on shared rows. Rate limiting moved out of wp_options into a small table of its own, one query instead of four option writes per pageview. Summaries are built one transaction per day under a lock, and two redundant indexes were removed from the pageview table.

1.4.1

Charts that disagreed with the numbers above them now agree. The trend on every AI screen was drawing its summarised days and silently dropping the current one, so AI at a Glance showed a headline of twenty four views above a line that added up to twenty one, and the line fell to zero on today whatever the traffic was. The same gap left today out of the stacked charts on Authors, Landing Pages and Exit Pages. Both are fixed, and the trend, the ranked rows and the stacked chart on every screen are now checked against each other.

Biggest assistant was measuring its share against the whole site rather than against assistant traffic, so a single assistant sending every AI visit on the site was reported as 0%. It now reads as a share of the views it is a share of.

The weekly summary email no longer loses a week to a mail server having a bad hour. The week was being marked as sent before wp_mail was asked, and a refusal left it marked, so the email never went and nothing said why. A refused send is now retried on the following hourly runs, and the settings card says when the last one went out, or that the last one was refused and by what.

Count a view after offers one second again, alongside two, three, five and ten.

The four Maintenance buttons no longer shift sideways when one of them reports back: the answer goes in a fixed slot below the row, so the button you were about to press is still where you were looking. The same applies to the shared link and weekly email buttons.

On the screens a filter cannot reach, because a refused request carries no country or device, the filter chips say so instead of sitting there looking active. Every trend panel is now drawn by one piece of code, which is how the revenue one had quietly lost its download control.

1.4.0

The human only release. Pageviews from data centre addresses are refused: two bundled tables of cloud and hosting ranges, about 45,000 of them, let the collector tell a headless browser on AWS from a reader at home even when everything else about the request looks right. It is on by default and switchable in Settings, and the refused requests are counted under Filtered Traffic as Data centre address. A pageview now waits two seconds for a reader who does nothing, up from one, and only trusted device events count as an interaction: a click dispatched by script proves nothing. A page that merely stayed on screen in a browser that also reports oddly is refused and filed as headless, and Headless Chrome is recognised from its client hints even under a rewritten agent string. Settings gains an interaction only rule for sites that want the strictest count there is.

Filtered Traffic is rebuilt. Refused requests are now counted by hour and by page as well as by name, so the screens carry a dated chart with an axis, an hourly chart for today, a stack of what the traffic was over time, a chart of people against machines, the pages machines fetched most, and when in the day they come. AI Visibility gains Pages AI Reads, the pages the models are fetching, next to the pages assistants send people to. Proof of Presence shows every counted view by what proved a person was there, and the Overview carries a Not people card. The weekly email says how much was refused.

Setup is now nothing: click, download, contact link, missing page and site search capture are on from install, and the settings screen shows only what matters, with the fine tuning folded away on its most accurate defaults. Saving one settings form can no longer reset a field on another, and the delivery settings (script mode, endpoint name, proxy header, allowed domains) finally have a save button of their own. The weekly email sends on the first cron run on or after its day rather than only on the day, so a quiet site no longer skips a week.

Bugs fixed: on a site without pretty permalinks every dashboard request was a 404 and the screens sat on Loading; the upgrade routine logged a database error on every run under WP_DEBUG; the sidebar collapse button and the section dropdowns shared a style, which left two controls fighting each other and pushed the menu off the screen on tablets. The collapse button is gone and the sidebar is one menu with section dropdowns, becoming a single dropdown below 960 pixels. The engagement table scrolls sideways on phones instead of widening the page.

1.3.2

A pageview now has to prove somebody was there: the page has to render on screen, and then either somebody does something on it or it stays in front of them. The collect endpoint no longer accepts anonymous POSTs, and a route change only counts after an interaction. Expect lower numbers after this update, and nothing already recorded is rewritten.

Everything refused is counted by name under Stats, so a low figure can be checked rather than taken on trust. AI crawlers and AI assistant fetches are kept apart from each other and from your visitors: a person who follows a citation out of ChatGPT is still a visitor, the machine that fetched the page on their behalf never was.

The bot list was also making the opposite mistake. It matched company names rather than crawler names, so it refused the DuckDuckGo browser, Yandex’s and Naver’s phone apps, Petal Search, the Pinterest app and anyone reading a page inside Slack: seven of the fifty two real browsers now in the test set. There is one list instead of two overlapping ones, it has to be able to name a machine before it will refuse it, and Do Not Track exclusions are counted so a site honouring that signal can see where its traffic went.

1.3.0

Revenue reporting: WooCommerce and Easy Digital Downloads orders are read from the shop and attached to the visit that produced them, across seven new screens. Correct counting behind a page cache or a CDN, which was losing whole pages of traffic: the beacon now ships to everybody and exclusion happens on the collect request, page optimisers are told to leave it alone, and a shared CDN address no longer throttles the site.

1.2.3

Accuracy release, and your figures will get smaller. Four faults were inflating visitors and views: the no script image was counting machines, forwarded IP headers were believed on sites with no proxy, a retried beacon could store the same pageview twice, and bot filtering was an agent list and nothing else. All four are fixed and the stored history is cleaned in the background. Ranked reports also page and search properly now, so a site with thousands of pages can see past the top twenty.

1.2.2

An optional anonymous usage report, off on every install and never sent unless you agree. You are asked once, shown the exact payload from your own site first, and never asked again if you say no. Nothing about your visitors is included under any circumstances.

1.2.1

Data, then AI insights, runs a statistical read of the selected period on demand and returns ranked findings with the figure and the confidence behind each one. Everything is computed on your own server against your own rows. Also adds an optional longer visitor recognition window for counting returning readers, off by default.

1.2.0

Fewer requests, and a beacon that stops when your host says stop: it reads 429 and 503, honours Retry-After, holds a budget per visit, and a page read now costs one request instead of two with nothing lost. Counting is more complete too: readers whose browser ran no JavaScript are recorded, a blocked REST route no longer means lost traffic, and Do Not Track is no longer skipped by default on new installs.

1.1.1

Deleting the plugin keeps your settings, your shared link and your history by default, so updating by hand no longer wipes them. The AI screens now describe assistant traffic and nothing else, and authors, content types, assistants, cited pages and campaigns can all be filtered on.

1.1.0

AI Visibility: visits arriving from an assistant become their own channel with four screens of their own, and Gemini is no longer miscounted as organic search. Four optional statistical layers for the main chart, every one off until you switch it on. Goals and funnels read their own rules back as a sentence and funnel steps can be reordered.

1.0.0

First public release. Editorial reporting is the point of it: traffic by author, posts separated from pages and archives, and read depth per post. Real bounce rate and time on page from an engagement beacon rather than guessed from timestamps. Cookieless, self hosted, no account, no API key and no paid tier.