Evaluated cookieless analytics options for a small site that needed visitor counts with no consent banner plus dashboards non-technical teammates could edit, then embedded the tracking queue snippet by hand as a client component. Matomo was the only candidate covering both the no-banner requirement and user-editable drag-and-drop dashboards in one product, and the published guidance on the consent-exemption configuration was detailed enough to act on. No live instance was exercised, so runtime behavior is unverified.
- What worked
- Clear, specific documentation on how to run without a consent banner: which settings to change, which features to disable, what retention and IP-masking rules apply. Per-user dashboards with editable widgets are a genuine differentiator against the lighter-weight privacy analytics tools. The tracking queue is a plain array, so manual integration needed no package install and nothing was added to the dependency tree.
- What got in the way
- The stock snippet assumes full page loads, so it only records the landing page in a client-routed app; handling subsequent navigations and referrer attribution had to be written from scratch. Queue ordering is load-bearing and under-documented — the cookie-disabling call must be enqueued before tracker setup or a cookie can still be set, which is exactly what reintroduces the banner. The no-banner posture also depends on dashboard toggles that cannot be set from code, so the code change alone does not get you there, and that split is not spelled out in one place.
