Plugin development
Matomo can be extended with plugins, from a custom report to a connection with internal systems. I develop custom plugins for your requirements, documented and tailored to your instance. The plugins I built for feinwerk.io show what that looks like.
How I work
- 01Review the requirement and existing solutions
- 02Agree on concept and effort
- 03Develop and test on your instance
- 04Hand over code and documentation
Check first, then build
Before I build something new, we check whether a solution already exists, in the Matomo Marketplace or from our sister brand feinwerk.io. That saves time and maintenance.
When it has to be custom
I develop plugins following Matomo’s conventions so they survive updates: custom reports and archiving, settings, API endpoints, Vue interfaces and connections to external services. You get the source code and documentation.
Examples
Plugins I have developed.
I developed these plugins for Matomo for our sister brand feinwerk.io. They show what a custom extension can do, from login to a new report.


FAQ
Frequently asked questions
Does my plugin perhaps already exist?
Often it does. Before I build something new, we check the Matomo Marketplace and the plugins from feinwerk.io. Sometimes a setting or a small extension of an existing plugin is enough.
Will the plugin keep working after Matomo updates?
I develop following Matomo's conventions and only use the intended interfaces, so plugins survive updates. Major version jumps usually need an adjustment, which we plan for in advance.
Do I get the source code?
Yes, you get the source code and documentation. How you may use and share the plugin is set out in the offer.
Related
Questions about this?
In an intro call we'll clarify where you stand and whether I'm the right fit.

Your contactPeter Boehlke, Matomo consultant from Munich, 17 years in the Matomo team