Matomo audit

When numbers don't add up, teams stop trusting their data. The audit reviews your Matomo setup systematically and ends with a prioritised action plan rather than a long list of issues.

How I work

  1. 01Kick-off: clarify websites, goals and scope, set up access
  2. 02Review of tracking, data, configuration and server, without changing anything
  3. 03Report with current state, target state and action for every finding, ranked by priority
  4. 04Debrief with your team and a finished action plan

When a Matomo audit pays off

An audit is most valuable at turning points:

  • Before a relaunch or a migration So the tracking does not carry old mistakes into the new website
  • Before a major Matomo update To find outdated plugins and settings beforehand
  • When numbers do not match Matomo shows different values than the CRM, shop or campaign platform
  • When you take over an instance From another agency, a service provider or a team that has moved on
  • When data protection asks A new data protection officer wants to know what Matomo stores and for how long
  • When Matomo gets slow Reports load slowly, archiving fails, the database keeps growing

What unchecked numbers cost

  • Decisions on the wrong basis Matomo does not work with samples but with every single hit. A tracking code included twice, a missing goal or unfiltered bot traffic therefore flows straight into every report.
  • Privacy contradictions If IP shortening, retention or consent do not match the privacy policy, you store data you cannot justify.
  • Slow or missing reports Archiving in the browser, too many real-time segments or an overloaded database make the interface sluggish.
  • Security backlog An instance nobody looks after misses updates for Matomo, plugins, PHP and database.

Matomo Cloud or your own instance

The audit works with both. I review tracking, data, configuration, privacy and Tag Manager the same way everywhere. Your own instance adds server and archiving; with Matomo Cloud the provider takes care of those.

After the audit: set up monitoring

To keep the numbers clean, I can set up ongoing monitoring. Sentinel checks the tracking hourly and reports missing visits, drops, silent goals and bot spikes by email, Slack or Teams, before anyone stumbles over them in the monthly report.

Quick check or audit?

Website check Questionnaire Matomo audit
Cost free free on quote
What is checked what your website loads before consent your assessment of six questions tracking, data, configuration, privacy, Tag Manager and server
Access needed no no Matomo, and the server for your own instance
Result rating with notes in about 20 seconds assessment with focus areas report, action plan and debrief

You will find the website check and the questionnaire in the quick check. The audit is also available for Google Analytics 4 and Google Tag Manager, for example when both systems run in parallel.

Scope

What a Matomo audit reviews

Seven areas, adapted to your setup. The audit is read-only: I look at everything and change nothing.

  1. 01

    Tracking and measurement plan

    • Tracking code or Tag Manager container on all pages
    • Pageviews, events, goals and e-commerce compared with what should be measured
    • Site search, custom dimensions and campaign parameters
    • Gaps, double counting and events nobody needs any more
  2. 02

    Data quality

    • Duplicate pageviews and double-counted conversions
    • Bot and spam traffic, referrer spam
    • Internal visits from the office, VPN and development
    • Missing sections of the website, subdomains or apps
  3. 03

    Reports and configuration

    • Websites, time zones, currencies and excluded URL parameters
    • Goals, segments and dashboards
    • Reports that mislead and reports nobody opens
  4. 04

    Privacy settings

    • IP shortening, cookies, consent and feature detection
    • Retention and automatic deletion of raw data
    • Opt-out and the tools for access and erasure requests
    • Personal data in URLs, page titles or dimensions
  5. 05

    Tag Manager

    • Structure of containers, tags, triggers and variables
    • Versions, publishing and who may publish to live
    • Custom HTML and JavaScript in tags
    • Consistent naming
  6. 06

    Plugins, users and permissions

    • Installed plugins: current, unused or conflicting
    • Users and roles following the principle of least privilege
    • Old accounts and API tokens, for example from former service providers
  7. 07

    Server, archiving and operations

    own instance
    • Archiving via cron job, run times and errors
    • PHP and database settings, table sizes
    • Versions and updates of Matomo, PHP and database
    • Backups, trusted hostnames and enforced HTTPS
  8. +

    Your questions

    Do you have a specific question, for example about a campaign, one area of the website or a gap to the CRM? It gets its own focus in the audit.

After the audit

An action plan your team can work through.

Every finding gets a priority, an owner and a status. This is what the plan looks like, shown here as an example.

  • Summary for decision-makers, technical part for implementation
  • Current state, target state and action for every finding
  • Priority from P1 to P3 and a rough effort estimate
  • An owner for every action
  • Code examples wherever an action needs code
  • Debrief with your team and, if you like, the implementation
Action planExample
3 / 6 done
  1. P1Tracking code included twiceRemove the second snippet, otherwise page views count twiceWeb developmentdone
  2. P1Archiving runs in the browserSet up a cron job, switch off browser archivingIT operationsdone
  3. P1Internal visits not excludedExclude office and VPN IP rangesIT operationsdone
  4. P2Inconsistent campaign parametersAgree on a naming scheme and share it with the teamMarketingin progress
  5. P2Bot traffic in the reportsEnable bot detection, clean up old dataIT operationsopen
  6. P3Retention periods not documentedDefine and document retention for raw dataData protectionopen

FAQ

Frequently asked questions

What do I get at the end of the audit?

A report with a summary for decision-makers and a technical part. Every finding is listed with its current state, target state and action, plus a priority, a rough effort estimate and an owner such as web development, IT operations, marketing or data protection. In the debrief we go through everything together.

Does the audit change anything in our Matomo?

No. I look at configuration, tracking and reports but change nothing. Changes only come with the implementation, and only if you want them.

Do you need access to the server?

For tracking and configuration a Matomo account with admin rights is enough. For archiving, database and performance a look at the server helps, ideally together with your IT.

Does the audit work with Matomo Cloud?

Yes. I review tracking, data quality, configuration, privacy and Tag Manager on Matomo Cloud just as on your own instance. With Matomo Cloud the provider runs server and archiving, so those checks are left out.

How long does a Matomo audit take?

That depends on the number of websites, instances and Tag Manager containers. After the intro call you receive a quote with a clear scope and a date for the report.

Who carries out the audit?

I do it myself. I have been part of the Matomo team since 2009, I am a Matomo Implementation Partner and I know Matomo from the tracking code to the database.

Do you also implement the actions?

If you like, yes, fully or in part. Your team handles many items itself, and I help with the rest, for example Tag Manager, archiving or data clean-up.

Knowledge on this topic

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

Newsletter

Matomo know-how, once a month.

Practical tips on tracking, privacy settings and performance, plus notes on important Matomo updates. No spam, unsubscribe any time.