Matomo Site Kit

2.3.1

Release date: 2026-05-10

Fixed:

• Tag Manager dataLayer (_mtm) is now preserved for users whose role is in the tracking exclusion list. The _mtm array is still initialized and the config / page-context pushes are still emitted, so site code that relies on _mtm.push(…) keeps working and the dataLayer stays inspectable from devtools. Only the actual tracker payloads (MTM container script, classic matomo.js, server-side PHP tracker, noscript pixel) are suppressed for excluded roles

Security:

• Resolved all open Dependabot advisories (1 critical, 29 high, 13 moderate, 11 low) by upgrading @wordpress/scripts from ^27.0.0 to ^32.1.0 and pinning patched transitive versions via overrides: @babel/runtime ^7.29.2, serialize-javascript ^7.0.5, webpack-dev-server ^5.2.3, markdownlint-cli ^0.48.0
• Patches affect axios, lodash, node-forge, fast-uri, basic-ftp, cross-spawn, tar-fs, ws, path-to-regexp, picomatch, brace-expansion, follow-redirects, @babel/runtime, serialize-javascript, and others. All affected packages are build-time / dev dependencies except @babel/runtime, which is bundled into the admin UI
• Admin UI bundle rebuilt against the upgraded toolchain

2.3.0

Release date: 2026-04-16

New Features:

• Page context dataLayer – New optional toggle “Push page context to dataLayer” that enriches _mtm with ready-to-use variables for Tag Manager triggers and variables
• Pushed variables include: page_type (home, blog, search, error_404, author, <post_type>, archive_<post_type>, archive_<taxonomy>, archive_date, archive), post_type (singular human-readable label), post_id on singular pages, taxonomies (category, tag, any custom taxonomy slug with term names), author on author archives, locale, and user_login_status
• user_id (SHA256) and user_role are now pushed in the page context when User ID tracking is enabled (previously in the Matomo config object)

Improvements:

• Renamed the Tag Manager “Push context to dataLayer” toggle to “Push config context to dataLayer” to clearly distinguish it from the new page context toggle
• Enabling the config context toggle now pre-checks the page context toggle
• Config context push now only carries matomo.* and wordpress.environment – keeps the initial payload minimal
• matomo.site_id is now pushed as an integer (was a string)
• Removed recMode from the dataLayer push (kept on the actual tracker requests where it is needed)
• Matomo Host is now trimmed and stripped of any trailing slash on save and in the dataLayer payload
• Custom taxonomies registered with publicly_queryable or show_ui (but not public) are now included

Technical:

• New helpers: omsk_get_page_context(), omsk_get_post_type_label(), omsk_get_current_user_role()
• REST settings add enableMtmPageContext flag (omsk-matomo-enable-mtm-page-context-field option)

2.2.0

Release date: 2026-03-06

New Features:

• AI Bot Tracking – Track visits from AI assistants (ChatGPT, Perplexity, Claude, Gemini, etc.) separately in Matomo using the bot tracking API (recMode). Requires Matomo 5.7.0+
• Server-Side PHP Tracking – Track page views server-side for ad-blocker resistance and enhanced privacy
• WooCommerce Ecommerce Tracking – Complete ecommerce analytics for all three tracking methods
• Site Search Tracking – Automatically track WordPress searches with keyword, category, and result count
• Automatic Annotations – Create Matomo annotations when posts are published
• Customizable annotation format with variables ({post_type}, {title}, {url}, {author})
• Privacy settings page with robots.txt and .well-known/ai-plugin.json management

Improvements:

• Restructured Settings page with intuitive tracking method cards
• Each tracking method now clearly shows its required fields
• Separated feature cards for better organization (GDPR, Heartbeat, User ID, Ecommerce, Search, AI Bot Tracking)
• Renamed Dashboard tab to Features tab for clarity
• Intelligent bot detection for server-side tracking with AI assistant categorization
• Server-side AI bot detection sends recMode=1 (bot-only) requests with source label
• Classic JS and Tag Manager use recMode=2 (auto mode) for automatic AI bot classification
• Noscript image tracker includes recMode=2 for pixel-based bot detection
• Privacy opt-out shortcode now uses modern script-based approach
• Full WordPress Coding Standards compliance
• Enhanced security with proper escaping and sanitization throughout
• Added REST API nonce for improved security
• Performance optimizations with DNS prefetch and script preloading

Technical:

• Complete code audit for security and best practices
• Improved internationalization (i18n) support
• PHP 8.2+ compatibility
• WordPress 6.0+ required
• Matomo 5.7.0+ required for AI Bot Tracking feature

2.1.1

Release date: 2025-11-24

• Tested on WordPress 6.9

2.1.0

Release date: 2025-11-24

• Refactored Settings page with tabbed interface
• Added Dashboard tab for API configuration
• Added User ID tracking feature (SHA256 hashed email)
• Added Heartbeat Timer option for classic tracking
• Improved Tag Manager dataLayer with wordpress.user_id
• Removed setup wizard in favor of streamlined settings
• Various UI/UX improvements
• Added noscript image tracker fallback

2.0.0

Release date: 2025-11-20

• Complete refactor using React and WordPress components
• New modern dashboard interface
• WordPress Dashboard widget
• Post/Page analytics metabox

1.1.2

Release date: 2024-09-25

• Fix missing function get_value()

1.1.0

Release date: 2023-06-29

• Add dataLayer sync
• Add Matomo details in dataLayer
• Fix Matomo Cloud instances support

1.0.2

Release date: 2023-06-27

• Support Matomo Cloud CDN in tracking codes

1.0.0

Release date: 2023-05-17

• Initial plugin release