Works with your stack
Cookie consent for Matomo
consent through its own api
Matomo for WordPress adds no tracking until you pick a tracking mode. Then its tracker and the hits are served by your own site. Its cookie consent setting is off by default, and Matomo has no WP Consent API code: consent goes through Matomo’s own JavaScript API. Cookie Rocks Pro uses that API, and no Matomo cookie is written before the choice.
By Matomo · matomo.org · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Matomo
WordPress plugin
- Tested version
- 5.13.1
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 5.13.1 tested
- Active installs
- 100,000+
What Matomo adds to your visitors’ browser
No trackers In our test of Matomo 5.13.1 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with Matomo
Consent through Matomo’s own API
Cookie Rocks Pro tells the Matomo tracker to wait for consent from the start, and gives consent when the visitor accepts. Nothing is written in the browser before the choice.
Withdrawal without a stray cookie
Matomo writes a cookie each time consent is forgotten, even before any choice. Cookie Rocks Pro asks it to forget only a consent that was given on the page.
Shop orders sent from your server
With ecommerce tracking on, the default, Matomo for WordPress can send WooCommerce carts and orders from PHP, with no consent check. A choice made in the browser does not hold these hits. Review that option if your shop needs consent first.
Nothing until you choose a mode
Right after activation, Matomo for WordPress adds no tracking code at all. Consent only becomes a question once a tracking mode is on.
What our tests found on Matomo
Good to know · Matomo for WordPressWhat Matomo for WordPress stores in visitors' browsers
Matomo for WordPress: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.
Name Kept in Category What it is for matomo_has_jscookie Statistics Tells Matomo that the visitor's browser runs JavaScript, for visit statistics Read in its code, 2 November 2026, Matomo for WordPress.
Full detail
Matomo for WordPress can store these in a visitor's browser: matomo_has_js (cookie, statistics: Tells Matomo that the visitor's browser runs JavaScript, for visit statistics). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.
Good to know · TranslatePress, Weglot, Instagram Feed, WP Go Maps, MailPoet, MatomoTranslatePress, Weglot, MailPoet and others set nothing by default
by default: Default settings
With default settings and nothing set up, TranslatePress, Weglot, Instagram Feed, WP Go Maps, MailPoet and Matomo for WordPress set no cookie, use no storage and load no known third-party tool.
Seen in our tests, 17 October 2026, TranslatePress, Weglot, Instagram Feed, WP Go Maps, MailPoet, Matomo 3.3.8, 6.4.3, 6.14.0, 10.1.10, 5.42.0, 5.13.1. Source
Full detail
On a fresh WordPress home page with default settings (no account, key or content set up), TranslatePress, Weglot, Smash Balloon Instagram Feed, WP Go Maps, MailPoet and Matomo for WordPress set no cookie, keep nothing in the browser's storage and load no known third-party tool, after Accept all.
Set before the choice · MatomoMatomo writes a 30-year cookie when consent is forgotten, even before the choice
Cookie Rocks Pro now sends that command only when consent given on the page is withdrawn, so mtm_consent_removed is not written before the choice. Before 2.5.0 it sent it before any choice.
Seen in our tests, 16 October 2026, Matomo matomo.js 5.5.0.
Full detail
Matomo's tracker writes the cookie mtm_consent_removed (30 years) on the site's domain whenever forgetConsentGiven is called, even before any choice, with cookies disabled and with no hit sent. Cookie Rocks Pro pushes requireConsent at start, setConsentGiven on acceptance, and forgetConsentGiven only when a consent given on the page is withdrawn: no cookie is written before the choice. Before 2.5.0 it pushed forgetConsentGiven before any choice.
Depends on a setting · Matomo for WordPressMatomo for WordPress tracks nothing until set up; consent setting is None
setting “Cookie consent” · by default: None
After activation it adds no tracking code. Once a mode is chosen, the tracker is served by the site itself. Its Cookie consent setting defaults to None, and it has no WP Consent API code.
Read in its code, 16 October 2026, Matomo for WordPress 5.13.1.
Full detail
Matomo for WordPress adds no tracking code after activation (track_mode disabled by default). Once a mode is chosen, the tracker and hits are served by the site itself (app/matomo.js, app/matomo.php or /wp-json/matomo/v1/hit/), inline in the footer. Its Cookie consent setting defaults to None; the options push requireCookieConsent or requireConsent, and a consent plugin must then give consent through the _paq API. There is no WP Consent API code.
Sent from your server · Matomo for WordPressMatomo for WordPress sends WooCommerce carts and orders from the server
setting “Track ecommerce” · by default: on
With Track ecommerce on (default), carts and orders are sent from PHP in some cases, with no consent check. A browser-side consent signal does not hold these hits. The server tracker sets no cookie.
Read in its code, 16 October 2026, Matomo for WordPress 5.13.1.
Full detail
With Track ecommerce on (default), Matomo for WordPress sends WooCommerce carts and orders from PHP during AJAX or REST requests, in Tag Manager mode, or with MATOMO_TRACK_ECOMMERCE_SERVER_SIDE, with no consent check in that code; the PHP tracker sets no cookie but reads _pk_id. A browser-side consent signal does not hold these hits. Use server generated Visitor ID (off by default) starts the WooCommerce session for visitors without _pk_id.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Matomo 5.13.1, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: Matomo 5.13.1 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
Questions
Does Matomo read WP Consent API?
No. Matomo for WordPress has no WP Consent API code. A consent plugin has to give consent through Matomo’s JavaScript API.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Matomo users
Your own statistics, after the choice.
matomo waits
Every feature of the complete plugin for 30 days, no card. Matomo keeps counting from your own site.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.