Matomo for IT and development
IT is expected to run Matomo, secure it and keep it up to date, often alongside many other systems. I plan installation and architecture with your team, harden the instance, set up archiving and monitoring and hand everything over with documentation that lets your team take over operations. I have been part of the Matomo team since 2009.
Sound familiar?
- 01Archiving that doesn't finishReports are missing or out of date because archiving takes too long.
- 02The database keeps growingRaw data grows, queries get slow, backups take ages.
- 03SecurityA publicly reachable application with user accounts, plugins and API tokens.
- 04Updates and pluginsMatomo, PHP and the database should stay current without tracking going down.
- 05Login and permissionsAccounts should use the central login, permissions should follow roles.
- 06Tracking in codeEvents, data layer and single-page apps should be connected cleanly.
Architecture and installation
I plan with your team where Matomo runs and how it grows: one server or separate systems for tracking, archiving and reports, database, caching and backups. The installation is reproducible and fits your environment.
Archiving and performance
Archiving runs via cron job, with intervals and parallel processes that match the data volume. I tune the database and PHP so that reports stay fast even with large amounts of data.
Security and updates
I harden the application and server, set up roles following the principle of least privilege and connect the login via single sign-on. Updates to Matomo, plugins, PHP and the database can then be rolled out on schedule.
Tracking in code
For development teams I define which events and data an application delivers, what the data layer looks like and how single-page apps report pageviews. I review the implementation before it goes live.
Handed over with documentation
At the end there is documentation your team uses to run and update the instance and to know where to start when something goes wrong.
FAQ
Frequently asked questions
What infrastructure does Matomo need?
A web server with PHP and a MySQL or MariaDB database. How large depends on traffic and on how long raw data is kept. Beyond a certain size we spread tracking, archiving and reports across separate servers.
Does Matomo run in containers?
Yes. What matters is persistent data, archiving via cron job and a configuration that keeps several instances consistent.
How do we absorb traffic peaks?
With Queued Tracking: tracking requests first land in a queue in Redis or Valkey, and systemd services work through them continuously. Tracking stays fast even during campaigns, and the database gets an even load.
How do we connect a single-page app?
Through the tracking code or the tag manager, with a pageview on every view change and events from your code. I give your development team the requirements and review the implementation.
Do you also take on operations?
Operations with an SLA are offered by our sister brand feinwerk.io. Alternatively, I hand the instance over with documentation so that your team runs it itself.
Sounds like your project?
In an intro call we'll clarify where you stand and what comes first.
Your contactPeter Boehlke, Matomo consultant from Munich, 17 years in the Matomo team