This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Connect Matomo (WP-Matomo, WP-Piwik)


If you are not yet using Matomo On-Premise, Matomo Cloud or hosting your own instance of Matomo, please use the Matomo for WordPress plugin.

This plugin uses the Matomo API to show your Matomo statistics in your WordPress dashboard. It’s also able to add the Matomo tracking code to your blog and to do some modifications to the tracking code. Additionally, WP-Matomo supports WordPress networks and manages multiple sites and their tracking codes.

To use this plugin the Matomo web analytics application is required. If you do not already have a Matomo setup (e.g., provided by your web hosting service), you have two simple options: use either a self-hosted Matomo or a cloud-hosted Matomo by InnoCraft.

Requirements: PHP 7.0 (or higher), WordPress 5.0 (or higher), Matomo 4.0 (or higher)

Languages: English, Albanian, Chinese, Dutch, French, German, Greek, Hungarian, Italian, Polish, Portuguese (Brazil). Partially supported: Azerbaijani, Belarusian, Hindi, Lithuanian, Luxembourgish, Norwegian, Persian, Romanian, Russian, Spanish, Swedish, Turkish, Ukrainian

What is Matomo?

Learn more.

First steps


You can use following shortcodes if activated:

[wp-piwik module="overview" title="" period="day" date="yesterday"]

Shows overview table like WP-Matomo’s overview dashboard. See Matomo API documentation on VisitsSummary.get to get more information on period and day. Multiple data arrays will be cumulated. If you fill the title attribute, its content will be shown in the table’s title.

[wp-piwik module="opt-out" language="en" width="100%" height="200px"]

Shows the Matomo opt-out Iframe. You can change the Iframe’s language by the language attribute (e.g. de for German language) and its width and height using the corresponding attributes.

[wp-piwik module="post" range="last30" key="sum_daily_nb_uniq_visitors"]

Shows the chosen keys value related to the current post. You can define a range (format: lastN, previousN or YYYY-MM-DD,YYYY-MM-DD) and the desired value’s key (e.g., sum_daily_nb_uniq_visitors, nb_visits or nb_hits – for details see Matomo’s API method Actions.getPageUrl using a range).


is equal to [wp-piwik module=”overview” title=”” period=”day” date=”yesterday”].

Credits and Acknowledgements

  • Graphs powered by Chart.js (MIT License).
  • All translators at Transifex and WordPress.
  • Anyone who donates to the WP-Matomo project, including the Matomo team!
  • All users who send me mails containing criticism, commendation, feature requests and bug reports – you help me to make WP-Matomo much better!

Thank you all!


  • WP-Matomo settings.
  • WP-Matomo statistics page.
  • Closer look to a pie chart.
  • WordPress toolbar graph.
  • Matomo: Here you’ll find your auth token.


General Notes

  • First, you have to set up a running Matomo instance. You can get Matomo here and its documentation here.
  • If you want to update your Matomo instance, you should set your WordPress blog to maintenance while the update process is running.

Install WP-Matomo on a simple WordPress blog

  1. Upload the full wp-piwik directory into your wp-content/plugins directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
  3. Open the new ‘Settings/WP-Matomo (WP-Piwik) Settings’ menu and follow the instructions to configure your Matomo connection. Save settings.
  4. If you have view access to multiple site stats and did not enable “auto config”, choose your blog and save settings again.
  5. Look at ‘Dashboard/WP-Matomo (WP-Piwik)’ to see your site stats.

Install WP-Matomo on a WordPress blog network (WPMU/WP multisite)

There are two differents methods to use WP-Matomo in a multisite environment:

  • As a Site Specific Plugin it behaves like a plugin installed on a simple WordPress blog. Each user can enable, configure and use WP-Matomo on his own. Users can even use their own Matomo instances (and accordingly they have to).
  • Using WP-Matomo as a Network Plugin equates to a central approach. A single Matomo instance is used and the site admin configures the plugin completely. Users are just allowed to see their own statistics, site admins can see each blog’s stats.

Site Specific Plugin

Just add WP-Matomo to your /wp-content/plugins folder and enable the Plugins page for individual site administrators. Each user has to enable and configure WP-Matomo on his own if he want to use the plugin.

Network Plugin

The Network Plugin support is still experimental. Please test it on your own (e.g. using a local copy of your WP multisite) before you use it in an user context.

Add WP-Matomo to your /wp-content/plugins folder and enable it as Network Plugin. Users can access their own statistics, site admins can access each blog’s statistics and the plugin’s configuration.


Where can I find the Matomo URL and the Matomo auth token?

To use this plugin you will need your own Matomo instance. If you do not already have a Matomo setup, you have two simple options: use either a self-hosted Matomo or cloud-hosted Matomo by InnoCraft.

As soon as Matomo works, you’ll be able to configure WP-Matomo: The Matomo URL is the same URL you use to access your Matomo, e.g. for the demo site: The auth token is some kind of a secret password, which allows WP-Matomo to get the necessary data from Matomo. To get your auth token, log in to Matomo, click at the preferences gear icon (top right) and click at “API” (left sidebar menu, near the bottom).

You can get a more detailed description here:

I get this message: “WP-Matomo (WP-Piwik) was not able to connect to Matomo (Piwik) using our configuration”. How to proceed?

First, please make sure your configuration is valid, e.g., if you are using the right Matomo URL (see description above). Then, go to the “Support” tab and run the test script. This test script will try to get some information from Matomo and shows the full response. Usually, the response output gives a clear hint what’s wrong:

The response output contains…
bool(false) and HTTP/1.1 403 Forbidden: WP-Matomo is not allowed to connect to Matomo. Please check your Matomo server’s configuration. Maybe you are using a password protection via .htaccess or you are blocking requests from localhost/ If you aren’t sure about this, please contact your web hoster for support.
bool(false) and HTTP/1.1 404 Not Found: The Matomo URL is wrong. Try to copy & paste the URL you use to access Matomo itself via browser.
bool(false) and no further HTTP response code: The Matomo server does not respond. Very often, this is caused by firewall or mod_security settings. Check your server logfiles to get further information. If you aren’t sure about this, please contact your web hoster for support.

If this does not help as well, feel free to open a topic in the support forum. Please share all available information including the test script result, if possible.

PHP Compatibility Checker reports PHP7 compatbility issues with WP-Matomo.

The Compatibility Checker shows two false positives. WP-Matomo is 100% PHP7 compatible, you can ignore the report.

Overview shortcode shows no unique visitors using a yearly range.

See Matomo FAQ.

WP-Matomo only shows the first 100 sites of my multisite network. How can I get all other sites?

The Matomo API is limited to 100 sites by default. Add the following line to the section [General] of Matomo’s config/config.ini.php file:

API_datatable_default_limit = 1000

Tracking does not work on HostGator!

Try to enable the “avoid mod_security” option (WP-Matomo settings, Tracking tab) or create a mod_security whitelist.

Can I contribute to WP-Matomo as a translator?

You like to contribute to WP-Matomo translations? Please use the Transifex translation community.

Of course, I will add missing languages if requested, and I will also upload the existing language files of older WP-Matomo releases.

If you can’t (or don not want to) use transifex, you can also translate languages/wp-piwik.pot delivered with WP-Matomo.

Thank you very much! 🙂


13. märts 2024
Good plugin. Nonetheless, considering it is better to be in the safe side a consent banner is a must. It would be great if the tool also adds the function to incorporate the code in the header to support popular consent banners with matomo. Matomo already has made available the code for the most common popular consent banners. Plugins to add code in the headers have the drawback that one cannot really choose the location in the header, and the location seems to make a difference. That the only reason preventing me using Matomo and that is the reason to set 2 stars to the plugin
22. sept. 2023 3 replies
Impossible to connect the sites with the latest version of Matomo, unusable!
1. dets. 2022
This plugin does what it claims very easily. But also gives a lot of options if you want to customize your tracking.
7. sept. 2022
Once you understand how the plugin works in connection to an “on premise” Matomo, it’s the ideal plugin for Analytics outside GA. Am migrating most of the blogs I manage (8 so far) with good data. Thx!
3. juuli 2022
Lots of issues. Main issue is no data showing in wordpress. Also zero support even if you buy their packages. We spend close to $2000 and no replies. Based on many posts, this appears to be a bug in plugin.
20. aug. 2021
Just great ! So easy to use with Wordpress, compared to the never eending problem I had with Analytics!
Read all 92 reviews

Contributors & Developers

“Connect Matomo (WP-Matomo, WP-Piwik)” is open source software. The following people have contributed to this plugin.


“Connect Matomo (WP-Matomo, WP-Piwik)” has been translated into 12 locales. Thank you to the translators for their contributions.

Translate “Connect Matomo (WP-Matomo, WP-Piwik)” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Fix settings behavior
  • Fix auto configuration in PHP API mode
  • Fix Opt-Out shortcode language attribute
  • Remove deprecated dynamic property (PHP 8.2)


  • Rename plugin to “Connect Matomo”
  • Fix a XSS vulnerability


  • Encode plugin display name
  • Option to set requireConsent or requireCookieConsent
  • Avoid notice on empty ecommerce data
  • Improve search tracking performance (thanks to theodejager, details)
  • Fix multisite sub-site tracking (thanks to ulkoalex, details)
  • Remove excess form closing tag (thanks to ulkoalex, details)


  • Fix a CSRF vulnerability
  • Fix JavaScript typos on settings page which broke some interface functionality
  • Fix proxy path on multisite networks (thanks to caveman99, details)
  • Fix array key warnings (thanks to goaround, details)
  • Fixed a bug in proxy config.php to avoid adding the protocol twice to the Matomo URL
  • Proxy script will run proxy/config.local.php before proxy/config.php to set an individual WordPress root directory via $wpRootDir


  • Fix feed tracking via proxy script (thanks to nicobilliotte, details)
  • Add piwik.php proxy script wrapper to make sure proxy tracking codes continue working if piwik.php is used
  • Fix for stalled blog options on network activation (thanks to ulkoalex, details)
  • Fix wrong title on city statistics (thanks to ulkoalex, details)
  • Fix “call to undefined method” error on network admin
  • Do not allow to set empty WP-Matomo display name
  • Rename Piwik link on dashboard widget to Matomo


  • Replace jqplot and jquery.sparklines with Chart.js
  • Allow to show overview stats for last 60 and 90 days
  • Allow to select the per post stats range from today to last 90 days
  • Optionally remove Matomo’s script tag’s type attribute, see
  • Fix/update proxy script (thanks to nicobilliotte and Rasp8e,
  • Make plugin working if deployed in a custom folder (thanks to utolosa002,


  • Hotfix to avoid deprecated in jqPlot (
  • Enabling metaboxes on particular Custom Post Types (thanks to goaround,


  • Handle tracking codes containing matomo.js/.php instead of piwik.js/.php
  • Fixed target=”_BLANK” property (thanks to tsteur)


  • Bugfix: Innocraft cloud URL * will work
  • Option to configure filter_limit parameter (see expert settings)
  • Replaced piwik.php proxy script by matomo.php proxy script


  • Bugfix: Get HTTP mode working again


  • Support for new Innocraft cloud URL (*
  • Changed naming from Piwik to Matomo
  • Added City, Type and Model views
  • Bugfix: Avoid warnings on empty results


  • Security fix: Escape request var
  • Language updates


  • support: Use different site IDs for different languages
  • Ecommerce widgets


  • Header issue solved which caused incompatibilities with other plugins like Yoast SEO
  • Update of InnoCraft cloud links (InnoCraft is the team behind Matomo)
  • Bugfix: Avoid a broken page if Matomo is misconfigured and WordPress debugging enabled


  • Added InnoCraft Cloud support (the new service created by the people behind Matomo). is still usable via HTTP mode, the configuration will be updated automatically.
  • Added search functionality to site browser
  • Added preload DNS option, see
  • Added option to set link and download classes (expert settings)
  • Added option to choose which post types should be considered for annotations
  • Bugfix: Opening Matomo stats of a specific network site does not lead to the sitebrowser anymore
  • Bugfix: Avoid unnecessary notices
  • Bugfix: Avoid a warning in proxy script
  • Bugfix: NoScript code is working again
  • Replaced deprecated wp_get_sites


  • Allow to modify the tracked user ID using the filter “wp-piwik_tracking_user_id”
  • Bugfix: Output of “post” shortcode was incorrectly placed, see
  • Bugfix: Usage of WP_PROXY_BYPASS_HOSTS, see
  • Bugfix: Proxy script did not work with cURL, see
  • Bugfix: RSS feed tracking did not use proxy URL


  • Action “wp-piwik_site_created” was extended by a site ID parameter, so it will deliver the Matomo site ID of the created site
  • Bugfix: Fixed an issue with Matomo site creation
  • Bugfix: Allow changes of a manually defined tracking code on networks, see


  • Language updates
  • Readme typo fixes (thx to ujdhesa)
  • Perform your own code after site creation by using the action “wp-piwik_site_created”
  • Improved caching ID to avoid interferences, see


  • Removed notices and warnings
  • Allow to modify the tracking code using the filter “wp-piwik_tracking_code”
  • Network: Don’t show plugin overview settings link on individual sites


  • Security improvements
  • Removed some division by zero warnings
  • Option to disable SSL host verification (additional to peer verification)
  • Overview widget: Do not show unique visitors row if value is not available
  • Bugfix: Post shortcode is fixed and will work again


  • Security fix


  • Language updates
  • Bugfix: Deprecated get_currentuserinfo() replace. Thx to the infinity, see
  • Bugfix: Overview widget will show proper values even if a period > 1 day is selected, see


  • Feature: Show “per post stats” and the “custom variable meta box” also on page and custom post edit
  • Bugfix: Fixed user tracking (moved the user tracking changes from general modifications to runtime modifications)
  • Bugfix: Fixed namespace error. Thx to thelfensdrfer, see
  • Bugfix: Warning on blog name change, see


  • Feature: User ID Tracking. Thx to Danw33, see
  • Feature: Site ID parameter added to opt-out shortcode. Thx to christianhennen, see
  • Feature: Allow a local config file to affect the proxy script, see
  • Bugfix: No script tag is not auto-inserted if the tracking code is manually defined.


  • Language updates
  • Encoding & gettext fixes
  • Better error messages. Thx to mcguffin, see


  • Several language updates.
  • Important security fix: XSS vulnerability


  • Several language updates.
  • Feature: Offer setDownloadExtensions option (see expert settings).
  • Feature: Consider configured HTTP connection method in proxy script.
  • Widget: Visitor country added.
  • Bugfix: Annotations on scheduled posts will work.
  • Bugfix: Donation button will work again.


  • Several language updates.
  • Switch to JSON renderer (Matomo 3 compatibility preparation)
  • Workaround: PHP API will work with Matomo 2.14+, see for further information.
  • Feature: Heartbeat timer support
  • Feature: Expanded token & URL/path input fields
  • Bugfix: Site duplication fix.
  • Bugfix: Avoid notice on empty overview response.
  • Bugfix: Return request error responses.
  • Bugfix: Opt-out URL fixed.
  • Bugfix: Capabilities: “Do not track”-filter and “show stats”-limit will work on multisites as expected again.


  • Several language updates.
  • Feature: Disable update notifications (expert settings).
  • Feature: Choose between cURL and fopen if both are available (expert settings).
  • Feature: Choose between POST and GET (expert settings).
  • Widget: System details added.
  • Widget: SEO widget re-enabled.
  • Update: Replaced deprecated Matomo API calls.
  • Bugfix: Settings link (toolbar, network mode) fixed.
  • Bugfix: Encode blog titles in PHP mode.
  • Bugfix: Pie charts won’t show to long legends if more than 10 items are available.


  • Several language updates, amongst others Portuges (Brazil) finished. See for further information.
  • Bugfix: If WP-Matomo is not configured properly or the connection to Matomo could not be established, the toolbar graph won’t cause a JavaScript error anymore.


  • Feature: Expand “other” values on click
  • Bugfix: Avoid notices on invalid file path (PHP API)
  • Bugfix: Cookie lifetime input boxes are in some cases shown or hidden by mistake
  • Network (multisite): Updated plugin to use wp_get_sites if possible
  • Test script: Settings dump added

  • Bugfix: Fixed memory & timeout issue on multisites

  • Add clear cache function.
  • Add clear settings (reset) function.

  • Bugfix: Sitebrowser link (settings page, support) fixed
  • Bugfix: Use new settings directly after saving (reloading is not necessary anymore)
  • Optimized caching behaviour
  • Language update (German, French)

  • Bugfix: Opt-out shortcode output fix
  • Bugfix: Opt-out shortcode will also work in “pro” and “php” mode
  • Bugfix: Test script link (settings page, support) fixed
  • Bugfix: Removed test script errors and notices
  • Bugfix: Keep sure the revision ID is stored and avoid re-installing the plugin again and again
  • Bugfix: http/pro – after configuration the settings page had to be reloaded once to start working
  • Typo fixes

  • Bugfix: Option storage bug if WP-Matomo is used as single site plugin on blog networks
  • Bugfix: WP-Matomo will work without Matomo superuser access, again
  • Bugfix: Choosing the site without auto config works again

  • Bugfix: In some cases the update message did not disappear -> fixed
  • Important change: If you want to upgrade from 0.8.x to 0.10.x, please install first:

  • Bugfix: Settings link in admin notices fixed
  • Bugfix: Shortcode result will appear where expected
  • Bugfix: settings will be kept (if WP-Matomo was not reconfigured after updating to, yet)
  • Feature: If Matomo returns an error instead of a tracking code, this error will be visible

  • Public beta of WP-Matomo 1.0
  • Full refactored code
  • Feature: Limit referral cookie lifetime
  • Feature: Enable content tracking

  • Improvement: Define additional file extensions for tracking downloads
  • Improvement: Added a POT file to support translators (Note: 1.0 will change a lot, so please don’t spend too much time in translating the current version, e.g., by creating an all new translation. With 1.0 I will also offer a translation platform to support your work.)
  • Improvement: If necessary, you can force Matomo to use HTTP or HTTPS now (e.g., to avoid redirections from http to https)
  • Avoided a naming collision with Woo Theme

  • Improvement: Updated the Matomo proxy script and added cURL support if url_fopen is not available
  • Bugfix: Setup bug, see
  • Bugfix: CDN URL notice, see
  • Bugfix: Fixed zlib compression notice, see
  • Bugfix: Proxy script label links to proxy script checkbox
  • Fixed a typo in German language file

  • Bugfix: PHP API causes plain text output issue (see
  • Bugfix: Shortcode output translated

  • Bugfix: One more commit error
  • Bugfix: Adding up problem related to the overview widget
  • Bugfix: Fixes missing brackets on ob_start
  • Hotfix: Adds / to js/index.php to force a reload
  • Bugifx: Replaced broken support link
  • Added a bitcoin donation link

  • Bugfix: Commit errors in

  • Improvement: Only activate/ load admin components if an admin page is actually loaded. Thanks to Michael!
  • Bugfix: Proxy tracking will work again. Matomo 2.7 or higher is recommended.
  • Bugfix: Avoid a PHP notice in dashboard
  • NOTE: If you update Matomo and use the “add tracking code” feature, please also update your WP-Matomo tracking code: Just open the WP-Matomo tracking code settings and save them again.

  • Bugfix: Avoid forced relogin on site change (WP network)
  • Bugfix: Avoid multiple annotations on post updates
  • Bugfix: Use mergeSubdomains instead of mergeAliasURLs
  • Feature: Added mergeAliasURLs as additional feature

  • Bugfix: PHP API causes plain text output issue, see
  • Bugfix: PHP API causes WordPress multisite login issue, see
  • Bugfix: Removed PHP warning if annotations are enabled and annotations will work again, see
  • Feature: “Track visitors across all subdomains” script changes are done by Matomo now, see
  • Update: Flattr API update

  • Bugfix: Multisite login issue, see
  • Bugfix: wpMandrill compatibility, see
  • Feature: Show page views (actions) in “visitors last 30”

  • Update: PHP API will use namespaces (Matomo 2.x compatibility)
  • Update: Matomo URL isn’t necessary to use PHP API anymore.
  • Feature: Limit cookie lifetime
  • Feature: Track visitors across all subdomains
  • Feature: Disable custom var box if necessary
  • Feature: Choose if you like to add the tracking code to your site’s footer or header
  • Feature: New shortcode (post)
  • Feature: Add data-cfasync=false to script tag if necessary.
  • Feature: Add annotations on new posts, see
  • Bugfix: Do not load sparklines plugin if toolbar not shown
  • Bugfix: PHP API will work again (urlencoding removed)
  • jqPlot and jquery.sparkline updated
  • Partly refactored code

  • Feature: Per post stats (shown at the edit post page)
  • Feature: Track RSS views using a measurement pixel

  • Bugfix: Error messages won’t by cached anymore
  • Bugfix: Custom vars will now be added properly
  • Bugfix: Missing slash in proxy mode added
  • Feature: Track users on admin pages

  • Bugfix: Proxy script will work again
  • Option: Enable/disable one week caching
  • Load config file using full path to avoid side effects

  • Fatal error on statistics settings page fixed

  • Use Transients API (one week caching)
  • Option: Track visitors without JavaScript, see

  • Sparkline script update (IE 10 compatibility)
  • Syntax error fixes

  • Bugfix regarding tracking code changes in proxy mode, see
  • Feature: Change text “WP-Matomo” in menu items and dashboard widgets
  • Code cleanup (“new” first step)
  • Debugging: Logger added
  • Avoid double slash (//) in tracking code

  • CDN support: http and https separated, see
  • Made code optional. Move code to site footer.

  • Matomo 1.11 compatibility fixes (Matomo 1.11 required now!)
  • Depending on Matomo 1.11 WP-Matomo will use async tracking now
  • CDN support added, see

  • Warning on empty data removed (overview table)
  • Removed a possible deadlock
  • Bugfix: Apply tracking code settings everytime the tracking code is updated
  • Reset/uninstall script bugfix regarding network mode


  • WordPress 3.5 compatibility fix: (Thanks Christian Foellmann!)
  • Advanced Search Result Analytics, see
  • Site Search stats added
  • Use js/index.php: Replaces piwik.js and piwik.php by js/ (instead of piwik.js only)
  • Connection timeout setting added
  • Full reset option added
  • Uninstall script added
  • Stats metaboxes: Date formatted
  • Use proxy settings defined in wp-config.php
  • Matomo.php proxy script added (see
  • Bugfix: After upgrade, Matomo automatically places cookies again (


  • Shortcodes added
  • WP-Matomo will rename sites in Matomo if site name changes in WordPress
  • Bugfix: Tracking code changes should stay active after WP-Matomo updates

  • Matomo 1.9+ compatibility fix (Matomo 1.9 required!)
  • Browser version details added

  • Toolbar graph bugfix


  • Option: Disable SSL peer verification (REST API)
  • Option: Use own user agent
  • Test script displays additional information (e.g. response headers)
  • Using WordPress metabox concept properly
  • Bugfix: Sparkline script only loaded if required
  • Stats site supports up to 3 columns
  • Network admin stats: Choose site using a paged table (instead of a select box).
  • Feature: Custom variables, using custom post meta boxes.
  • Some minor bugfixes


  • WordPress 3.4 compatible (workaround)


  • Requires at least Matomo 1.8.2!
  • Choose between HTTP API or PHP API
  • Show graph on WordPress Toolbar
  • Add option to disable cookies – Thanks to Mathias T.!
  • Update bugfix: Upgrading from WP-Matomo 0.8.7 or less will work again
  • Some minor bugfixes


  • Bugfix: Adding a new site will work again.


  • Uses $wpdb->blogs instead of $wpdb->prefix.’blogs’ to keep it compatible to different database plugins
  • Bugfix: SEO dashboard widget will work even if “last 30” is selected
  • Bugfix: New created blogs won’t show “Please specify a value for ’idSite’.” anymore.
  • Bugfix: New network sites without title will be created
  • Bugfix: Upgrading from old versions will work again
  • Tabbed settings
  • Debug tools added (testscript, site configuration overview and WP-Matomo reset)
  • Support forum RSS feed
  • Language updates
  • Optionally use of set_time_limit(0) on stats page time out


  • Bugfix: Usage as “Site Specific Plugin” mixed up the different sites settings (network mode)
  • Hotfix: Avoid “Unknown site/blog” message without giving a chance to choose an existing site. Thank you, Taimon!


  • Auto-configuration
  • No code change required to enable WPMU mode anymore (Still experimental. Please create a backup before trying 0.9.0!)
  • All features in WPMU available
  • Bugfix: Removed unnecessary API calls done with each site request – Thank you, Martin B.!
  • Bugfix: No stats on dashboard (sometimes this issue still occured, should be fixed now)
  • Code cleanup (still not finished)
  • Minor UI fixes
  • Minor language/gettext improvements
  • Security improvements
  • Show SEO rank stats (very slow, caching will be added in 0.9.1)
  • WordPress dashboard SEO rank widget (very slow, caching will be added in 0.9.1)
  • New option: use js/index.php
  • New option: avoid mod_security
  • Multisite: Order blog list alphabetically (Network Admin stats site)
  • Settings: Order site list alphabetically (site list shown if order conf is disabled)



  • WP 3.2 compatible, metabox support


  • Bugfix: Will also work with index.php in Matomo path
  • Bugfix: last30 dashboard widget – show correct bounce rate


  • New language files (Azerbaijani, Greek, Russian)
  • Fixed hardcoded database prefix (WPMU-Matomo)
  • Minor bugfixes: avoid some PHP warnings


  • Added an optional visitor chart to the WordPress dashboard
  • WPMU/multisite bug fixed
  • Minor bugfixes


  • Select default date (today or yesterday) shown on statistics page
  • Bugfix: Shortcut links are shown again
  • German language file update
  • Minor optical fixes (text length)


  • New stats in overview box
  • WP 3.x compability fixes (capability and deprecated function warnings)
  • Some minor bugfixes
  • New config handling
  • Code clean up (not finished)


  • Matomo 1.1+ compatibility fix



  • Use load_plugin_textdomain instead of load_textdomain
  • Fixed js/css links if symbolic links are used
  • Changed experimental WPMU support to experimental WP multisite support
  • Try curl() before fopen() to avoid an OpenSSL bug
  • Added Norwegian language file by Gormer
  • Don’t worry – new features will follow soon 😉


  • Using jqPlot instead of Google Chart API
  • Some facelifting
  • Some minor bugfixes


  • Track 404-pages in an own category
  • Get some page (and article) details
  • Language updates


  • Bugfix: Percent calculation fixed
  • Bugfix: Visitor chart: No label overlapping if < 50 visitory/day
  • Visitor chart: Added a red unique visitor average line
  • Visitor table: Added a TOTAL stats line
  • Pie charts: Show top 9 + “others”, new color range
  • Option: Show Matomo shortcut in overview box
  • Some performance optimization


  • Unnecessary debug output removed
  • German language file update
  • WordPress dashboard widget: last 30 days view added


  • Click at a visitor stats day-row to load its details
  • Add stats overview to your WordPress dashboard


  • Added experimental WPMU support
  • Switch to disable Google Chart API
  • Added Albanian [sq] language file
  • Added Belorussian [be_BY] language file


  • Display statistics to selected user roles
  • Some HTML fixes (settings page)


  • Tracking filter added
  • Resolution stats
  • Operating System stats
  • Plugin stats


  • If allow_url_fopen is disabled in php.ini, WP-Matomo tries to use CURL instead of file_get_contents


  • WordPress 2.8 compatible
  • Bugfix: Warnings on WP 2.8 plugins site
  • Dashboard revised
  • Partly optimized code


  • WP-Matomo dashboard widgetized
  • Stats-boxes sortable and closeable
  • German language file added
  • Browser stats and bounced visitors


  • First public version