Publishing plugins on Marketplace
Thanks Mikanoshi, your second plugin is now also live!
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
Thanks Mikanoshi, your second plugin is now also live!
In Matomo, you can track qualified leads by setting up goals for meaningful actions, such as form submissions, demo requests, or completed contact forms. Use the Pages report alongside goal conversions to see which landing pages contribute to those actions, and consider adding custom dimensions or campaign tracking if you need more detail. One useful tip is to define what counts as a qualified lead in your CRM and compare those records with Matomo’s conversion data, since a form submission…
Hi there — this error and the inability to create tokens are usually connected, so fixing one often fixes the other. A few things worth checking: Create personal API tokens from the user menu (top-right avatar) under Personal → Security → “Create new token”. If that page itself errors, the account you are logged in with may lack the required role. A Matomo Super User can verify your access rights under Administration. If you are using the Matomo for WordPress plugin: make sure you are logged in…
That’s completely normal. Page views count every page loaded, while unique visitors count people, so one visitor reading three pages gives you three page views and one visitor. A big gap usually just means people are browsing more than one page, which is a good sign. For SEO, I check the Entry pages report most, since it shows which pages people land on from search, and you can sort it by bounce rate to find pages that aren’t holding attention. The Channel Type and Search Engines reports are…
There doesn’t seem to be a way at the moment. However, altering the code might help but of course if the code is updated then the change will be reverted. (not tested) File: core/Plugin/Controller.php Method: showWhatIsNew() $view->whatisnewShow = false; if (isset($view->hideWhatIsNew) && $view->hideWhatIsNew) { return; } Setting $view->hideWhatIsNew = true prevents the modal from appearing for that view. I have created an issue here: Add a configuration option to disable the “What’s New” modal…
That brute force table lockout is what is blocking you now. Every failed login adds an entry, and once enough pile up Matomo blocks your IP, which also explains the password reset error you are seeing. If you have database access, clearing the brute_force_log table (or asking your host to do it) usually unlocks the account right away. For the missing reset emails, Matomo uses plain PHP mail or your server’s SMTP settings, so it can fail silently even when your domain mail works fine elsewhere.…
Is there a way to disable the “What is new” modal that is shown after a Matomo update? I don’t want my users to see these news records, as the text is not translated and the links don’t work if modules mentioned in the news records are disabled. They are also way too technical for my users. As a workaround I used this to silence the modal until the next update: update piwik_user set idchange_last_viewed=17, ts_changes_shown='1970-01-01 00:00:00' where idchange_last_viewed IS NULL; Not sure why…
Frankie: Once these changes are made, please increment the version in plugin.json, create a matching new Git tag, and let us know. We will then review the new tagged release. Done. Used Http::sendHttpRequest() and manual location following up to 5 redirects.
Frankie: do not enable CURLOPT_FOLLOWLOCATION; This is the only reason I used CURL directly and not Http::sendHttpRequest(). Libravatar does 302 redirect to Gravatar proxy, so I need to always follow location to get a resulting HTTP code. This part in Matomo code is not actually true, CURLOPT_FOLLOWLOCATION can be set with open_basedir. There are some redirection protocols shenanigans, but it works just fine. github.com/matomo-org/matomo core/Http.php edb949cf5 // curl.options + redirect…
Hi Mikanoshi, Marketplace display names are not controlled by a general CamelCase-splitting rule in plugin.json. Some names have explicit Marketplace formatting—for example, McpServer is displayed as “MCP Server”—while other acronyms are not split consistently. The plugin’s technical name is also its Marketplace identity, directory name, and namespace, so please do not rename DDBotTracker or add spaces to the technical name. “DD Bot Tracker” would require a Marketplace-side display-name…
How Marketplace plugin titles are generated? By splitting CamelCase? Some plugins with multiple consecutive capital letters are split (MCP Server), some are not (DDBotTracker, KPIWidgets). It’s better to split mine like “DD Bot Tracker” to fit the majority. Frankie: So the parentheses are invalid sorry. Is new tag or new plugin.json version required to update screenshots? I also forgot to make cover
Hi Mikanoshi, Yes, Marketplace only accepts screenshot filenames matching: ^[a-zA-Z0-9_-]+\.(png|jpg|jpeg)$ So the parentheses are invalid sorry. I reviewed UltimateProfileAvatar and found a small set of changes needed before publication. The main issue is in VisitorDetails.php. The plugin inserts the visitor User ID directly into HTML returned for the Visits Log. As User IDs can originate from tracking data, please HTML-escape the displayed User ID before rendering it. Please also escape the…
Thanks. Is there a problem with parentheses in thumbnail titles? Matomo.org Supported bot categories - DDBotTracker Matomo excludes any detected bots from tracked visits using their DeviceDetector library. | Separate tracking of parsers, crawlers, scrapers and any other bots supported by Matomo's built-in DeviceDetector. Also my other plugin UltimateProfileAvatar is somewhere in limbo

Hi Mikanoshi, I saw your new 1.0.1 tag, and it imported successfully. I have now published DDBotTracker in the Matomo Marketplace. Thanks again for your patience, and for contributing to the Matomo Marketplace.
Hi Mikanoshi, You were correct about the access check: Archive::createDataTableFromArchive() already calls Piwik::checkUserHasViewAccess($idSite), so the commented-out checks in your two API methods are not needed. One small update is still required before publication: your plugin declares PHP >=7.2.5, but it uses PHP 8 syntax (such as union types and match). Please update plugin.json to require PHP 8.0 or later: "php": ">=8.0.0" Thanks for pointing that out.
Scott Aerators team appreciates how useful accurate tracking can be when analyzing website performance. When overriding page titles in Matomo Tag Manager, it’s worth checking when the title variable is updated and making sure the tag fires after the correct value is available. Testing the setup with Matomo’s preview and debugging tools can help confirm whether the updated title is being captured as expected.
Welcome to Matomo. This is completely normal, not a tracking problem. Why the numbers differ: a unique visitor is counted once per period, no matter how many pages they open. Page views count every page load. So if one person visits five pages, that is 1 unique visitor and 5 page views. A big gap usually just means your visitors browse several pages per visit, which is a good sign of engagement. On your other questions: For SEO insights, check the Referrers menu, especially Search Engines and…
Frankie: These checks are currently commented out and are needed to ensure users can access data only for sites they are permitted to view. But Archive::createDataTableFromArchive() has that check as the first line, at least in Matomo 5.14.
I am also interested in learning more about Matomo for SEO analysis. Understanding visitor behavior, bounce rates, and the difference between page views and unique visitors can really help us make better decisions. Looking forward to learning from the community’s experience!
Hi Mikanoshi, Thanks for reporting this, and sorry for the frustrating experience. We investigated and confirmed that your latest archive is valid: the PHP files, including ReportHelpers.php, pass syntax checks. The repeated error was caused by a Marketplace import issue: a broken file from the first failed import was retained under the same plugin version and was still being linted on later tag submissions. This was on our side, not GitHub caching your old repository contents. You do not need…
Yes, this is expected behavior, and it comes down to how Matomo applies the two scopes. The visit-scope condition (user_group = Group A) selects whole visits, and once a visit is selected, the action-scope condition does not filter the other actions out of that visit. So Action 2 (Project B) rides along inside every visit that matches the visit condition, exactly as you are seeing. If user_group is effectively constant for the whole visit, the cleanest workaround is to record it as an…
Submitted first plugin 9 days ago, got an email confirming review, no news ever since. Tried to submit second one today: → We have detected PHP syntax errors in your plugin: PHP Fatal error: Namespace declaration statement has to be the very first statement or after any declare call in the script in /ReportHelpers.php on line 3. Please fix your plugin code so it does not trigger errors. ← I fixed it, created new tag - still got email with the same error. So I deleted the entire git repo,…
I’m running PHP 8.6.0RC3 with Matomo version 6.0.0-b5 and get a WARNING message in the web interface: WARNING: /core/Session/SaveHandler/DbTable.php(25): Warning - Class Piwik\Session\SaveHandler\DbTable implementing SessionHandlerInterface is missing the create_sid() method which will be required in PHP 9.0 - Matomo 6.0.0-b5 - Please report this message in the Matomo forums: https://forum.matomo.org (please do a search first as it might have been reported already) (Module: CoreAdminHome,…
Adding one practical note to the answers above: after updating Matomo to 5.2.0 or newer, make sure to publish a new version of your Tag Manager container. The tag template list in an existing container can look stale until you publish, and it is easy to assume the update did not work when the container simply was not republished. If the tags still do not appear after publishing, clear the Matomo tmp cache and reload the container editor.
I would start by testing the site on Android Chrome with JavaScript errors and network requests visible through remote debugging. Temporarily disable plugins one by one, especially optimization or caching plugins, and check whether the issue disappears. If it works on a desktop but fails across multiple Android devices, JavaScript compatibility or a mobile-specific resource loading issue would be worth investigating first.
Yes, the line was thicker from 4->5. We reviewed the code and instead doubled the native size of the image request and forced the tag width the same. The @2x pixel density fixed the issue. I saw this: public const DEFAULT_WIDTH = 200; public const DEFAULT_HEIGHT = 50; public const LINE_THICKNESS = 4; public const POINT_SIZE = 6; ... $sparkline->setLineThickness(self::LINE_THICKNESS);
Hi AlleB, happy to walk you through the variable approach Jason mentioned. Here is a beginner friendly sequence that works well: In Matomo, open Tag Manager from the top menu and select your container (work in the draft version). Go to Variables on the left and click Create new variable. Choose the JavaScript Function type and name it something like Custom Page Title. In the function box, write logic that returns the title you want. Keep it simple to start. A common pattern is: if the page URL…
Hallo melbao, das klingt tatsächlich frustrierend, besonders wenn die betroffenen Seiten früher gut gerankt haben und seit Jahren auf deiner Website existieren. Ein Punkt wäre für mich allerdings besonders interessant: Dass die Übersichtsseite weiterhin indexiert wird, während die verlinkten Einzelseiten bei bestimmten Suchanfragen kaum oder gar nicht erscheinen, bedeutet nicht unbedingt, dass Google diese Seiten gezielt blockiert. Es könnte auch daran liegen, wie Google die einzelnen URLs…
I’d test the site with Chrome DevTools using Android device emulation and check the console for JavaScript errors. Also try temporarily disabling optimization/minification plugins, since broken or delayed JS is a common cause when menus and buttons fail only on mobile.
Hi there, There isn’t a way via a parameter to set the line width for spark lines. In the code the thickness is set to 1 pixel. The relevant file is: core/Visualization/Sparkline.php In the sparkline initialization code, around lines 109–112: $sparkline->setWidth($this->getWidth()); $sparkline->setHeight($this->getHeight()); $sparkline->setLineThickness(1); <------- this one $sparkline->setPadding('5'); But altering that may not make a difference. Did you find going from Matomo 4 to 5 that the…