Matomo Tag Manager
Matomo Tag Manager is built into Matomo and keeps tracking, tags and data in one instance, without an additional service. I set up containers, take over existing setups from Google Tag Manager and build the structure so that your team understands it and can maintain it. This website also measures through Matomo Tag Manager.
How I work
- 01Review the existing setup and measurement plan
- 02Create the container with tags, triggers and variables
- 03Set up consent, test environment and publishing
- 04Handover with documentation and training
What Matomo Tag Manager can do
Tags, triggers and variables as in Google Tag Manager, plus preview and debug mode, versions and environments. Because it is part of Matomo, there is no second account and no further provider. Your own Matomo instance delivers the container file.
Moving from Google Tag Manager
I take over tags, triggers and variables from the existing container, tidy up along the way and name things consistently. What was only needed for Google services is dropped or gets its own solution. Both containers can run in parallel for a while until the numbers match.
Data layer and e-commerce
For shops and applications I define a data layer from which the container reads products, cart and orders. That keeps tracking stable even when the page layout changes.
Consent and privacy
Tags only fire once your consent tool reports consent. Matomo itself can be configured to measure without cookies. Whether that is enough without consent is for your data protection advisers to decide.
Publishing and maintenance
Who may make changes, who publishes? I set up permissions, environments and a naming convention and document the container so that your team still understands it two years from now.
FAQ
Frequently asked questions
Can Matomo Tag Manager replace Google Tag Manager?
For most websites, yes. It has tags, triggers and variables, a preview and debug mode, versions and environments. Many services have ready-made templates, everything else can be added with custom HTML.
Where does consent come in?
Through triggers and variables: tags only fire once your consent tool reports consent. Whether Matomo itself may measure without cookies before that is for your data protection advisers to decide.
How do we test changes before they go live?
In preview and debug mode and in separate environments, for example for staging. A version only goes live after approval, and earlier versions can be restored.
Where is the container hosted?
On your Matomo instance. Your own server delivers the container file, not an external service.
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