First wordpress.org release. The Reports screen and the editor sidebar are\nfree, with no limits. Rewriting a heading or a paragraph now counts as a\nchange, so before\/after has something to compare against.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3697897,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3697897,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3697897,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3697897,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.5"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3697897,"resolution":"1","location":"assets","locale":"","width":1280,"height":600},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3697897,"resolution":"2","location":"assets","locale":"","width":1280,"height":740},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3697897,"resolution":"3","location":"assets","locale":"","width":1280,"height":530},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3697897,"resolution":"4","location":"assets","locale":"","width":1280,"height":1000},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3697897,"resolution":"5","location":"assets","locale":"","width":1280,"height":800}},"screenshots":{"1":"Reports \u2014 every measured page, worst drop-off first, with the block that\nlost the most readers named on each row.","2":"A single page, block by block in document order. The reach column is the\ncurve; the Change column marks the step where readers stopped.","3":"Settings. The coverage report says how many pages can be measured and\nnames the page builder found on the ones that cannot.","4":"The Manual, shipped in the plugin: what the numbers mean, when a block\ncounts as reached, and how far to trust the figures.","5":"The editor sidebar. Reach, dwell and clicks for the block you are editing,\nnext to the block itself."}},"plugin_section":[],"plugin_tags":[232,148857,307,63224,521],"plugin_category":[36],"plugin_contributors":[266175],"plugin_business_model":[],"class_list":["post-369226","plugin","type-plugin","status-publish","hentry","plugin_tags-analytics","plugin_tags-block-editor","plugin_tags-engagement","plugin_tags-scroll-depth","plugin_tags-statistics","plugin_category-analytics","plugin_contributors-onecraftne","plugin_committers-onecraftne"],"banners":{"banner":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/banner-772x250.png?rev=3697897","banner_2x":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/banner-1544x500.png?rev=3697897","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/icon-128x128.png?rev=3697897","icon_2x":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/icon-256x256.png?rev=3697897","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/screenshot-1.png?rev=3697897","caption":"Reports \u2014 every measured page, worst drop-off first, with the block that\nlost the most readers named on each row."},{"src":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/screenshot-2.png?rev=3697897","caption":"A single page, block by block in document order. The reach column is the\ncurve; the Change column marks the step where readers stopped."},{"src":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/screenshot-3.png?rev=3697897","caption":"Settings. The coverage report says how many pages can be measured and\nnames the page builder found on the ones that cannot."},{"src":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/screenshot-4.png?rev=3697897","caption":"The Manual, shipped in the plugin: what the numbers mean, when a block\ncounts as reached, and how far to trust the figures."},{"src":"https:\/\/ps.w.org\/onecraft-block-insights\/assets\/screenshot-5.png?rev=3697897","caption":"The editor sidebar. Reach, dwell and clicks for the block you are editing,\nnext to the block itself."}],"raw_content":"\n
OneCraft Block Insights measures pages built with the WordPress block editor, one\nblock at a time: how far down the page each reader gets, how long each block\nholds them, and where they click. It names the block your readers stop at.<\/p>\n\n
What it cannot measure. Read this first.<\/strong><\/p>\n\n Only content built with the block editor is measured. Pages built with a\npage builder \u2014 Elementor, Divi, WPBakery, Oxygen, Bricks, Beaver Builder \u2014\nstore their layout outside of blocks, so there is nothing for this plugin to\nattach to. Those pages produce no numbers at all. After activation the\nplugin scans your content and tells you exactly how many of your pages it\ncan and cannot measure, naming the builder it found.<\/p>\n\n This is also not a site-wide analytics plugin. There are no visitor totals,\nno sessions, no traffic sources, no unique visitors. It answers one\nquestion: within a page, which block do readers stop at.<\/p>\n\n It writes an identifier into your content.<\/strong><\/p>\n\n Telling one block apart from another, across edits, needs a name that\nsurvives the edit. So the first time you edit and save a page, the plugin\nadds a short ID to each block's comment delimiter in the post content.\nNothing visible changes, and the front end is unaffected.<\/p>\n\n Taking the plugin out takes them with it. Deleting the plugin restores post\ncontent to the exact bytes it had before the IDs were added, and\n wp block-insights strip does the same without uninstalling. Any post whose\ncontent would not survive that round trip is left completely untouched and\nreported to you, never rewritten.<\/p>\n\n A block counts as reached once enough of it is genuinely on screen: half the\nblock, or half the screen for a block taller than the screen. Dwell accrues\nonly while that holds, and stops when the reader switches tabs.<\/p>\n\n Measurement happens in the reader's browser, so the figures are directional\nrather than audited. Page views here will always be lower than your server\nlogs: content blockers, unusual browsers, crashed tabs and phones killing a\nbackground app all cost measurements. Use these numbers to compare sections\nwithin a page, not as a system of record.<\/p>\n\n Ratios survive this better than totals do. A block's reach and the page view\nit is divided by come from the same single beacon, so a lost visit removes\nboth at once and the percentage stays honest.<\/p>\n\n One more caution: reached is not read. A reader who scrolls past a block in\n200 milliseconds still counts as having reached it. That is what the dwell\nfigure is for.<\/p>\n\n Measurement is cookieless and first-party. No cookies are set, no browser\nstorage is used, no visitor identifier of any kind is created, and unique\nvisitors are not counted. No IP addresses, page URLs, referrers, user agents\nor personal data are stored.<\/p>\n\n What visitors do is written to your own WordPress database and read back\nfrom it. There is no analytics service, no third-party script, no remote\nAPI, no phone-home and no telemetry. Nothing about your readers leaves your\nserver.<\/p>\n\n Because no personal data is collected, no consent banner is required for\nthis plugin, and it adds nothing to personal data exports or erasure\nrequests.<\/p>\n\n Storage does not grow with traffic. One row covers one block, on one day, on\none device type, however many readers it had. Rows grow with pages times\nblocks times days.<\/p>\n\n Old data is never deleted. Once the daily table reaches its row budget, the\noldest days are folded into monthly totals, so disk usage stays predictable\nno matter how large the site is. Reports that reach back past that point\nprint the date day-level detail begins on, so a shrinking figure is never\nsilent.<\/p>\n\n By default only posts and pages are measured. Other public post types can be\nenabled in Settings.<\/p>\n\n Block Insights does not support WordPress Multisite.<\/p>\n\n The free version has no page limit, no page-view limit and no expiry.<\/p>\n\n Pro adds three things: the before-and-after comparison, which splits a\npage's numbers at the day you edited it; the client report, a printable\ndocument with your own letterhead; and a CSV export.<\/p>\n\n Your edits are recorded by the free version from the day you install it. If\nyou upgrade later, the comparison covers that whole history rather than\nbeginning on the day you paid.<\/p>\n\n The free version talks to no external service on its own. It ships the\nFreemius SDK, which powers licence activation and updates for Pro. On first\nactivation Freemius asks whether you want to share basic site data; the\nquestion is skippable, and if you skip it nothing is sent.<\/p>\n\n Data leaves your site in two cases: if you accept that opt-in, and if you\nactivate a Pro licence key. What is sent then is your site's homepage URL,\nthe plugin version and the SDK version \u2014 the minimum needed to enforce a\nper-site licence and deliver updates. The optional extras the SDK can send,\nyour list of installed plugins and themes and your WordPress\/PHP environment\nreport, are switched off by default in this plugin. No visitor data, and\nnothing from the statistics tables, is ever included.<\/p>\n\n Freemius terms: https:\/\/freemius.com\/terms\/\nFreemius privacy policy: https:\/\/freemius.com\/privacy\/<\/p>\n\n Deactivating the plugin stops measurement and changes nothing else.<\/p>\n\n Deleting the plugin runs a full cleanup, and this one modifies post content,\nso it is worth knowing in advance:<\/p>\n\n To remove the block IDs without uninstalling, run restores post content to its pre-assignment bytes. To verify that on your own\nsite:<\/p>\n\n Dump post content before stripping:<\/p>\n\n wp db export before.sql --tables=$(wp db prefix)posts<\/p><\/li>\n Run the strip (use --dry-run first to see what would change):<\/p>\n\n wp block-insights strip --yes<\/p><\/li>\n Dump again and compare:<\/p>\n\n wp db export after.sql --tables=$(wp db prefix)posts\ndiff before.sql after.sql<\/p><\/li>\n<\/ol>\n\n The only differences must be the removed WP-CLI commands: Filters: Set The editor scripts in npm install\n npm run build<\/p>\n\n The build uses @wordpress\/scripts (webpack). The front-end measurement\nscript, Step 3 is required, and it is the step people miss. Block identifiers are\nadded in the editor as you work; existing content is never rewritten in\nbulk, because that would touch every post on the site to solve a problem you\nmay not have. A post that has never been opened and saved in the editor\nsince activation is never measured. Opening it is not enough \u2014 the editor\nhas to consider the post edited. A space added and removed again counts.<\/p>\n\n Numbers then appear once someone has visited the published page. Your own\nvisits are not counted while you are logged in and able to edit that page.<\/p>\n\n\n No. Those builders store their layout outside of blocks, so there are no\nblocks to measure and those pages produce nothing. The coverage report in\nSettings names each builder it finds on your site and counts the pages\naffected. If most of your site is built that way, this plugin has little to\ntell you.<\/p><\/dd>\n Two things have to be true before a number exists. The page must have been\nopened in the block editor, actually changed, and saved since activation.\nThen someone other than an editor of that page must have visited it. Your\nown visits and previews are never counted.<\/p><\/dd>\nWhat it measures<\/h4>\n\n
\n
About the numbers<\/h4>\n\n
Privacy<\/h4>\n\n
Where to find it<\/h4>\n\n
\n
Storage<\/h4>\n\n
The Pro version<\/h4>\n\n
External services<\/h4>\n\n
Uninstalling<\/h3>\n\n
\n
wp block-insights strip<\/code>.<\/p>\n\nVerifying that strip restores your content exactly<\/h3>\n\n
wp block-insights strip removes every block ID this plugin has written and\n<\/code><\/pre>\n\n\n
\"biId\":\"...\"<\/code> entries in block\ncomment delimiters.<\/p>\n\nFor developers<\/h3>\n\n
wp block-insights audit<\/code>, render<\/code>, compact<\/code>, strip<\/code>.<\/p>\n\nblock_insights_post_types<\/code>, block_insights_reports_capability<\/code>,\n block_insights_exclude_viewer, block_insights_row_budget<\/code>,\n block_insights_trusted_proxies.<\/p>\n\nblock_insights_trusted_proxies<\/code> behind a CDN or reverse proxy, or rate\nlimiting treats every visitor as one address.<\/p>\n\nBuilding from source<\/h3>\n\n
build\/<\/code> are compiled from the uncompiled sources in\n src\/, which are included in this plugin. To rebuild them:<\/p>\n\nassets\/js\/bi.js<\/code>, is plain JavaScript with no build step and is\nshipped exactly as written.<\/p>\n\n\n\n
\n
Does it work with Elementor, Divi, WPBakery, Oxygen, Bricks or Beaver Builder?<\/h3><\/dt>\n
I activated it and the Reports screen is empty.<\/h3><\/dt>\n