Consent-Free Tracking with Matomo

matomo must be configured so that it does not require user consent via a consent management platform (cmp) this allows for analytics tracking to occur without interruption or user opt in, assuming it complies with applicable legal and regulatory standards (e g gdpr, eprivacy) how consent free tracking works matomo can be configured for consent free operation in two primary ways server side configuration client side configuration both approaches ensure matomo does not trigger consent requirements when loading but differ in implementation scope and control server side configuration (used by purple analytics) at sprylab, the purple analytics service implements server side configuration for matomo this setup ensures that matomo is executed without requiring cmp interaction no client side scripts need to manage or gate tracking behavior the tracking remains active regardless of the cmp state on the page this is the preferred method for ensuring reliable, consent free analytics client side configuration although matomo supports client side consent free setups, sprylab has not implemented any client side consent free solutions these would typically involve manipulating the matomo tracking script directly in the browser to bypass or avoid cmp triggers mobile apps and cmp interaction for mobile applications , sprylab has not implemented a consent free matomo configuration as a result matomo can still be blocked by cmps within the app environment tracking availability depends on how the client configures their cmp if matomo is excluded from the cmp and no vendor id is provided , tracking works without consent otherwise, matomo remains subject to the consent rules defined in the cmp summary platform consent free configured? method notes web (purple analytics) ✅ yes server side fully consent free without cmp involvement mobile apps ❌ no n/a subject to cmp behavior unless excluded by the client