Counters Block – showcase your stats with animated numbers
Turn your numbers into social proof – animated counters that showcase your stats, milestones, and live store data the moment visitors scroll into view. Counters Block | Pricing | Support | Demos Why Counters Block? Numbers convince, but static numbers get ignored. Counters Block is a Gutenberg tool for displaying statistics, milestones, and achievements with professional animated number counters – ideal for business landing pages, portfolios, and high-converting dashboards where social proof and key metrics need to capture attention and build trust. Choose from 16 modern counter layouts (including a Circular Progress Counter), pick from a wide range of animation styles and triggers, and fine-tune everything responsively for desktop, tablet, and mobile – complete creative freedom without touching a single line of code. With Premium’s Dynamic Data Integration, you can stop updating numbers manually: the block automatically fetches live WooCommerce stats (sales, orders, products, customers) and WordPress core stats (posts, pages, comments, users) straight from your site. Free Features Unlimited Static Counters: Add as many counters as you need, anywhere. 3 Professional Themes: Ready-made counter designs with one-click switching. Responsive Grid Layout: Separate controls for desktop, tablet, and mobile, plus column and row gap control. Classic Animations: Smooth counting animations with visibility triggers. Icon Support: Use custom icons from Font Awesome, Bootstrap, and Lucide. Number Formatting: Custom prefix and suffix, thousands separators (comma and space), and decimal support. Typography Controls: Style numbers, labels, and sub-labels responsively. Pro Version Upgrade to Counters Block Premium for live data and advanced design options. Premium features include: Live Dynamic Data: Display WooCommerce Total Sales, Orders, Products, and Customers, plus WordPress Posts, Pages, Comments, and Users – auto-synced, no manual updates. Smart Customer Counting: Includes both registered users and guest checkouts. HPOS Ready: Fully compatible with WooCommerce High-Performance Order Storage. 13 Premium Themes: Including the SVG-based Circular Progress Counter with ring size, thickness, and color controls. Advanced Animations: Rolling, Bounce, Fade, Slide (Up/Down/Left/Right), Pulse, Flip, and Typewriter. Animation Triggers: On Visible, On Page Load, On Click, On Hover, or a Custom CSS Selector, with global and per-counter duration, delay, and stagger controls. Smart Sales Formatting: Automatically handles refunds and prevents negative values. Per-Counter Styling: Backgrounds, borders, shadows, and hover effects. Priority Support: Direct help from the development team. How to Use Install and activate the Counters Block plugin. Open any page or post in the Gutenberg editor. Add Counters Block from the block inserter. (Optional) Select a Data Source – Static, WP Core, or WooCommerce. Customize themes, colors, and animations from the settings panel. Publish and watch your stats come to life! Use Cases E-commerce: Live sales counters and happy customer stats. Agency/Business: Project milestones and team achievements. Blogs/Portfolios: Published post/page counts and subscriber stats. SaaS/Dashboards: Real-time KPI tracking and performance metrics. Found a bug or have a feature request? Send feedback or post on the support forum. Check out the Parent Plugin of this plugin- B Blocks – A blocks collection and page building tool for Gutenberg. Check out our other WordPress Plugins- Html5 Video Player – Display videos as single and playlist in multiple skins. PDF Poster – Display/Embed PDF files with different styles. Html5 Audio Player – Listen audios with awesome visuals. StreamCast – Customizable radio player with different skins. 3D Viewer – Embed 3D models and 3D products with interaction. Advanced Post Block – Show posts and custom posts in different layouts.
Top keywords
- counters11×1.98%
- block9×1.62%
- counters block6×1.08%
- stats6×1.08%
- data5×0.90%
- live5×0.90%
- numbers5×0.90%
- support5×0.90%
- animations4×0.72%
- controls4×0.72%
- counter4×0.72%
- custom4×0.72%
WP-PostViews
WP-PostViews counts how many times each post, page or custom post type has been read and gives you somewhere to show the number. The count is kept as post meta, so it sorts, queries and exports like anything else WordPress stores about a post. Features A view count on any post, page or custom post type, printed by a template tag or by the [views] shortcode. Two templates you edit yourself, with tokens for the count, the title, the date, the excerpt, the thumbnail, the author and more. Choose who is counted — everyone, guests only or logged in users only — and leave known robots out. Template tags and a widget for the most and least viewed posts, optionally within a category or a tag. A sortable Views column on the post and page list tables. The count on the REST API as a views field, and an AJAX counting path for sites behind a page cache. A section on the WP-Stats page when that plugin is installed. Donations I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations. Usage The simplest way, and the only one that works in a block theme without editing template files, is the shortcode. Put it in the post or page whose count you want shown: [views] shows the count for the post it appears in. [views id="1"] shows the count for post 1, wherever you put it. To show the count on every post automatically, a classic theme calls the template tag from index.php, archive.php, single.php or page.php, anywhere inside the loop: The settings live at WP-Admin -> Settings -> WP-PostViews, on two tabs. Settings is where you choose who gets counted and whether WP-Stats is offered a Views section; Templates is where you edit the markup a count is rendered with. Where the count appears is decided by where your theme calls the_views() or where you put the shortcode. To hide it somewhere in particular, answer the wp_postviews_should_display filter: add_filter( 'wp_postviews_should_display', function ( $show ) { return ! is_archive() && ! is_search(); } ); Showing The View Count In A Block One block is available in the editor, under Widgets: Post Views — the view count, rendered with the template from the Templates tab. Leave Post ID at zero to show the count of the post the block is in, which is what an empty [views] does, or set it to another post’s ID to show that post’s count instead. It renders on the server, so the block preview in the editor is the real number rather than an approximation, and the count keeps rising in every post showing it without anything being re-saved. Previewing the block in the editor does not count a view. The shortcode still works and is not going anywhere. [views] and [views id="1"] behave exactly as they always have, and a post already containing one needs no change. The block calls the same code the shortcode calls, so the two render identically — use whichever suits the post. WP-CLI wp postviews list wp postviews list --limit=50 --format=json wp postviews get 42 The command reads and never writes. No screen in this plugin edits a view count, so the command does not offer one either — wp post meta update views is still there for whoever genuinely needs it, and says plainly that it is reaching past the plugin. REST API POST /wp-json/postviews/v1/post/ /view Reading a count needs no route of its own. The count is already published as a read-only views field on the core post resource, so /wp-json/wp/v2/posts/ answers with the post and its count together, and a list of posts carries every count in one response. What the core field cannot do is write, which is what this route is for: it counts a view, and it exists for sites serving cached pages, where the view has to be reported after the page is delivered. It takes the same wp_postviews_nonce the counting script is given, as a nonce parameter. It is refused unless the site defers counting — that is, unless it has a page cache and has turned the AJAX counting path on. Otherwise the view has already been counted while the page rendered, and counting again here would record every view twice. A refusal answers 403 — a bad nonce, or a site that counts views while the page renders. A post that does not exist is 404. This route is an addition. The admin-ajax.php wp_postviews action is unchanged and still supported.