Descripción

AnGo Scroll Analytics records how far visitors scroll through your content and displays the results on a dedicated “Readability” screen in wp-admin. It answers the question a pageview count cannot: did anyone actually read past the first screen?

Unlike heavy external analytics suites or heatmap SaaS tools, AnGo Scroll Analytics runs 100% natively on your server. There are no external scripts, no cookies, no third-party data sharing, and no complex event setups.

Why site owners and developers choose AnGo

Smart “Load-and-Die” Bot Filtering: automated hits (bots, scrapers, and Slack/Discord link previews) load the page and vanish instantly at 0% scroll. AnGo detects and excludes these zero-time visits by default so your reading averages stay accurate — and the Visits card always shows how many were left out.
Privacy-First & Cookie-Free (GDPR friendly): stores zero personal data, sets no cookies, and never logs raw IP addresses (only a temporary hash is used for the spam rate limit).
Ad-Blocker Resilient: neutral file and endpoint naming (scroll-depth.js and /wp-json/ango/v1/depth) that matched none of the EasyList, EasyPrivacy, uBlock Origin and AdGuard filter lists at the last check — and the FAQ explains why those names must stay plain.
100% Local & Self-Contained: the admin charts are powered by a locally bundled Chart.js build. Neither your front end nor wp-admin makes external CDN requests.
Every Public Content Type Tracked: posts, pages, WooCommerce products and custom post types from any plugin are measured the moment they exist — media attachments are the one exception, and a filter trims any type you don’t want counted.
Clean Database Citizenship: logged-in administrators and authors are ignored by default so you don’t pollute your own stats, and deleting the plugin removes its custom table and options completely — zero leftover database bloat.

What the Readability dashboard shows

Flexible date filtering — any custom range (the last 30 days by default), grouped by day or by month — plus a Device filter (All devices / Mobile / Tablet / Desktop) that narrows the whole dashboard to one class of visitor, because a phone flick reaches 100% far cheaper than a desktop scroll.
At-a-glance summary cards: total visits (with the count of excluded bot/preview hits), average scroll depth %, and median.
A full percentile breakdown — 5/10/25/50/75/90/100, phrased in plain English (“X% of visitors scrolled at least to Y% of the article”) — with a Reach / Classical switch between “how far did readers actually get” and the standard PERCENTILE.INC percentiles users know from Excel.
A visual trend chart: reading depth as a line against traffic volume as bars, over time.
A sortable per-article table: title, content type, visits, average scroll and a seven-column sortable Percentiles group per article (the 50% column is the median), with a live “Search articles” box and a # column numbering the current view.
A lightweight, server-rendered “Readability brief” widget on the Dashboard home screen: the same numbers for the last 7 days at a glance.

How it works under the hood

The tracking script loads on the single page of every public post type and measures depth through the scrollable height of the document — not the share of the article visible on screen, so a page that fits on one screen records 100%.

Initial arrival: a visit is registered as soon as the page loads. A visitor who reads the top screen without scrolling still gets a row, with 0%.
Efficient beacons: data is sent to the server only when reading progress actually advances (checked every 5 seconds), and when the visitor leaves the page or switches tabs (via navigator.sendBeacon, or fetch with keepalive). A failed send is retried at the next check. Each beacon also carries a coarse device class — mobile, tablet or desktop, computed in the visitor’s browser; no user-agent string is collected.
One row per visit: each visit occupies a single row in {prefix}_ango_visits, updated as the reader gets further down the page. A new tab or a new session is a new visit.

Performance & scale

Designed for small-to-medium blogs and content sites: the statistics are computed on the fly with direct SQL queries, and the REST endpoint is rate-limited to 60 requests per minute per IP hash (changeable via the ango_rate_limit filter). Without a persistent object cache each beacon costs two lightweight options-table queries — a spam brake, not a firewall. At hundreds of thousands of visits, transient caching or cron-based aggregation is worth adding; a typical blog does not need it.

Capturas de pantalla

The Readability dashboard: the filter bar, visits / average scroll / median cards, the percentile list ("X% of visitors scrolled at least to Y% of the article"), and the visits-plus-average-scroll trend chart. — The Readability dashboard: the filter bar, visits / average scroll / median cards, the percentile list (“X% of visitors scrolled at least to Y% of the article”), and the visits-plus-average-scroll trend chart.

Instalación

In wp-admin go to Plugins Add New Upload Plugin.
Choose the downloaded archive (ango-scroll-analytics-1.14.0.zip), click “Install Now”, then “Activate”.
On activation the plugin creates its table in the database, {prefix}_ango_visits (wp_ango_visits with the default prefix). If the schema changes in a later version, the table is brought up to date the next time wp-admin is opened (dbDelta).
A “Readability” entry appears in the left-hand menu — the dashboard lives there.

FAQ

Do visits with no scrolling really count?

Yes. Every arrival is a row, including the ones with 0% scroll: the percentiles describe all arrivals, not only those who read to the end. That is a deliberate decision, not lost data.

The dashboard does distinguish two kinds of zero-scroll visits. A visit that sent nothing after the initial page-load beacon (max_scroll 0 and time on page 0) is “load-and-die” — on a live site those are usually bots, crawlers and link previews, not people. They are excluded from the statistics by default (the Visits card shows how many were left out), while a person who loaded the page and stayed without scrolling — time on page above zero — always counts. The checkbox in the filter bar turns the exclusion off.

Is the tracking endpoint public?

Yes — it has to be, because visitors are not logged in. POST /wp-json/ango/v1/depth is limited to 60 requests per minute per IP; the limit is changed through the ango_rate_limit filter, and a value below 1 disables the check. The IP itself is not stored, only a hash of it, for the duration of the window. Behind a proxy (Cloudflare and similar) REMOTE_ADDR is the proxy address, so the limit is shared by all visitors — raise it in that setup.

Why do the numbers differ from my analytics tool?

This plugin measures depth through the scrollable height of the page, not the share of the article that was on screen: a short page that fits on one screen records 100%. And it counts visits, not unique readers — a new tab or a new session is a new visit.

What timezone are the numbers in?

Timestamps in the table (created_at) are stored in UTC, while the dashboard computes day boundaries in the site timezone. Keep that in mind when writing manual SQL against {prefix}_ango_visits.

Can I track custom post types?

They are tracked by default: the script loads on the single page of every public post type, so a WooCommerce product, a forum thread or a knowledge-base entry all get measured the moment they exist. Media attachments are the one exception — they are public but are media-library artifacts, not pages a reader scrolls. If a plugin registers a public type you do not want counted (a page-builder’s template library, a popup type), remove it with the ango_trackable_post_types filter:

add_filter( 'ango_trackable_post_types', function ( $types ) {
    unset( $types['my_popup'] );
    return $types;
} );

Does the admin screen load anything from outside my site?

No. The chart is drawn by Chart.js 4.5.1, bundled with the plugin (assets/vendor/chart.umd.min.js, MIT license), so wp-admin makes no external request and the chart works offline and behind a filtering proxy.

Why does the bundled Chart.js ship minified?

Chart.js 4.5.1 (MIT) ships here as the minified UMD build that upstream publishes — assets/vendor/chart.umd.min.js, licence banner intact. Upstream has no unminified UMD to use instead: dist/chart.umd.js and dist/chart.umd.min.js in its package are both minified. The readable code is published, just in another build: the unminified ESM bundle is dist/chart.js (https://unpkg.com/chart.js@4.5.1/dist/chart.js), and the sources it is built from are at https://github.com/chartjs/Chart.js/tree/v4.5.1/src.

Why are the file names so plain?

They are deliberately neutral: the tracking script is assets/js/scroll-depth.js and the public endpoint is /wp-json/ango/v1/depth, with no tracker/track in either. Those words are a common target for filter lists, and a blocked script or beacon loses data silently. Neither EasyList/EasyPrivacy nor the uBlock Origin and AdGuard filters matched these URLs (checked 2026-09-16 under the plugin’s previous name; the endpoint paths did not change in the rename), but the lists update daily — so do not rename them back “for clarity”.

What happens to my data when I uninstall the plugin?

Deleting the plugin removes everything it stored: the {prefix}_ango_visits table, the ango_db_version option and the throttle transients. Deactivating does not — the data survives a deactivate and reactivate cycle, so an upgrade or a temporary switch-off costs nothing. Clicking Delete on the Plugins screen shows a confirmation naming the statistics that will be lost. If you need the numbers after the plugin is gone, export them before deleting, or hold the cleanup back from a must-use plugin with add_filter( ‘ango_remove_data_on_uninstall’, ‘__return_false’ ).

Reseñas

No hay reseñas para este plugin.

Colaboradores & Desarrolladores

“AnGo Scroll Analytics” es software de código abierto. Las siguientes personas han contribuido a este plugin.

andrewgolubev

Traduce “AnGo Scroll Analytics” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código, echa un vistazo al repositorio SVN, o suscríbete al registro de desarrollo por RSS .

Historial de cambios

1.14.0

New: a Device filter (All devices / Mobile / Tablet / Desktop) in the dashboard’s filter bar. Every visit now carries a coarse device class — mobile, tablet or desktop, computed in the visitor’s browser from the pointer type and the viewport width; no user-agent string or anything more specific is collected. The filter narrows the whole dashboard — summary, percentiles, trend, article table — to one class, because a phone flick reaches 100% far cheaper than a desktop scroll. Visits recorded before this version appear under All devices only.

1.13.0

New: a row-number column (#) at the head of the By article table. The number is the row’s place in the current view: it renumbers when you sort or search, so the top of whatever you are looking at is always row 1. The column itself is not sortable — it always mirrors the active order.

1.12.0

New: a “Percentile mode” switch on the dashboard (Reach / Classical). Reach percentiles answer “how far did readers get” — at least X% of visitors reached this depth. Classical percentiles are the textbook statistical view, computed exactly like Excel’s PERCENTILE.INC — X% of visitors reached this depth or less. The switch changes the summary list, the table columns and their tooltips at once, needs no reload and is remembered per browser. Reach stays the default.

1.11.0

New: a “Search articles” box above the “By article” table. It filters the rows live as you type — case-insensitive title matching, no Apply click, no extra requests — composes with any active sort, and survives a re-render. When nothing matches, the table says so instead of showing a stale row set.

1.10.0

New: the “By article” table replaces the single “90% scrolled at least to” column with a full “Percentiles” group — seven sortable sub-columns (5/10/25/50/75/90/100) showing the depth each share of that article’s visitors reached. The separate Median column is gone; the 50% sub-column IS the median, computed the same way from the same rows. Wide screens scroll the table horizontally instead of squeezing it.

1.9.0

New: the tracker covers every public post type, not only posts and pages — WooCommerce products and any plugin’s custom post types are now measured and appear in the “By article” table. Media attachments stay untracked, and the new ango_trackable_post_types filter removes a type a site does not want counted.
New: the “By article” table names each row’s content type — a product reads “Product”, not “Post”.

1.8.1

New: article titles in the “By article” table are clickable links to the article itself, opening in a new tab. Posts that no longer exist stay plain text.
Fix: the sortable column headers no longer show their label twice (“ArticleArticle”). The 1.8.0 headers printed the column name both outside and inside the sort button; it now appears once.

1.8.0

New: the “By article” table is sortable. Click a column header to sort by it — first click ascending, second descending, with a direction arrow on the active column. Numbers sort numerically, titles and types alphabetically; finding the most visited or worst-median article no longer means eyeballing the rows.

1.7.0

New: a “Readability brief” widget on the admin Dashboard home screen. Visits, average scroll, median and the “90% scrolled at least to X%” line for the last 7 days, plus a link to the full report. Server-rendered — no extra scripts on the Dashboard — and counts visits exactly like the Readability page, load-and-die exclusion included.

1.6.0

New: the dashboard percentile list gains the low percentiles 5/10/25 alongside 50/75/90/100. On a bounce-heavy audience the classic lines read 0 and say nothing, while “25% of visitors scrolled at least to X%” stays informative.

1.5.0

New: logged-in visitors are not tracked — the site owner’s own views no longer pollute the percentiles. The tracking script is not loaded for logged-in users, and the endpoint refuses their beacons. Multi-author sites that want member visits counted can turn the exclusion off with the ango_track_logged_in filter.

1.4.0

Fix: the tracker no longer records 100% depth when the page layout is still unsettled at load time (scrollable height not yet known) — such loads were miscounted as full-depth reads.

1.3.0

New “Exclude load-and-die visits” filter (on by default): page loads whose only beacon fired at page load — mostly bots and link previews — are excluded from all dashboard statistics. The Visits card shows how many were excluded, and a checkbox in the filter bar turns it off.

1.2.1

Fix: the author is shown as Andrew Golubev, the Details link points to the WordPress.org page, and “Details” is translated in Russian.

1.2.0

Renamed to AnGo Scroll Analytics per the WordPress.org review; all code symbols, options and the REST namespace moved to the ango_ prefix.
Translation files no longer ship in the package — translations come from translate.wordpress.org.

1.1.8

Fix: cleared all Plugin Check errors (inline prepare() calls, %i identifier placeholder, sanitized REMOTE_ADDR).

1.1.7

Readme discloses the bundled Chart.js 4.5.1 build (MIT).

1.1.6

Uninstall cleanup: deleting the plugin removes its table, options and transients, with a warning on the Plugins screen naming what is lost.
Added the WordPress.org readme metadata block and plugin header fields.

1.1.5

Fix: rebuilt the Russian translation file with a parseable header (the previous build shipped a malformed one).

1.1.4

Fix: removed a doubled percent sign in the percentile lines (50%% -> 50%).

1.1.3

Plugin attributed to Adviko Inc.

1.1.2

Neutral asset and endpoint names (scroll-depth.js, /wp-json/…/depth) so ad-blocker filter lists don’t silently break tracking.

1.1.1

Fix: the Apply button sits on the controls’ line in the filter row.

1.1.0

The admin interface is translatable (English source, Russian catalogue).

1.0.1

Fix: Chart.js is bundled with the plugin instead of loaded from a CDN URL that returned 404.

1.0.0

Initial release: scroll-depth tracking on posts and pages, the Readability dashboard (visits, averages, percentiles, trend chart, per-item table), UTC storage with site-timezone day grouping.