Integrations

Matomo in Shopware 6: plugins, Tag Manager and orders from the server

Matomo itself offers nothing for Shopware 6, but the Shopware Store has several third-party plugins. Here is how they differ, how to measure e-commerce data via Matomo Tag Manager, why orders should also come from the server and what to watch out for with Shopware's cookie consent.

Shopware 6 allows your own code in the storefront, so a tracking code is quickly built in. It gets difficult with the data only the shop knows: which product is viewed, what is in the cart and what was ordered. For this, there are plugins that pass this data to Matomo or to Matomo Tag Manager, and one that reports everything from the server.

The plugins in the Shopware Store

Plugin Vendor Way E-commerce Notes
Matomo Tracking and Ecommerce Martin Eisenführer tracking code product, cart, order with revenue, tax, shipping and discount since 2020, no Tag Manager, consent from Shopware or via its own cookie name
Matomo Tracking and Ecommerce Campit tracking code product, cart, order connects to several consent tools, also Shopware Cloud
Matomo Tag Manager Campit Tag Manager e-commerce data layer for your own tags container plus data layer, also Shopware Cloud
Server-side Matomo tracking Konpio server full e-commerce data since version 3 without cookies, compatibility stated up to Shopware 6.7.8

All four are subscriptions with a free trial month. There is also a free plugin by Alexander Müller outside the store that only outputs the tracking code, without e-commerce and without consent. Matomo’s list of integrations names Campit and Alexander Müller.

A plugin is only as good as its maintenance. Check the supported Shopware versions, the date of the last change in the changelog and which e-commerce data it actually reports.

E-commerce via the Tag Manager

If you already work with Matomo Tag Manager, what you need from the plugin above all is a data layer: product, category, cart and order as data that triggers and tags can access. The tracking itself then runs in the Tag Manager and can be changed in Matomo without touching the plugin. Campit offers a separate plugin for this. How containers, triggers and variables work together is covered in Matomo Tag Manager.

Two ways from the shop to Matomo: in the browser, a data layer delivers products and cart to the Tag Manager; from the server, orders go directly to Matomo's Tracking API.

Orders from the server

In the browser, orders get lost: through ad blockers, thank-you pages that do not load or missing consent to cookies. Matomo therefore describes a hybrid approach: page views keep coming from the browser, while the shop reports cart and orders from the server to the Tracking API. For this, the shop stores Matomo’s visitor ID and the source with each order so the order lands with the right visit, and flags reported orders so none is counted twice. According to its own guide, Matomo does not yet fully support refunds and partial refunds in this setup.

In the Shopware Store, Konpio’s plugin reports everything from the server, without cookies. How orders go from Matomo on to ad platforms is covered in Conversions API.

Shopware comes with its own cookie consent. Matomo belongs in the Statistics and Tracking group there, and the plugins register their cookies in this place. Since version 6.7.3, a rule applies that surprises many:

  • Shopware stores a hash of the whole cookie configuration, with names, descriptions and lifetimes.
  • Every change counts: if a plugin adds, changes or removes a cookie, the value changes.
  • Then everything starts over: Shopware deletes all non-essential cookies, including Matomo’s, and asks for consent again.

For Matomo, this means: after a plugin update, recognition can be reset at a stroke, and until consent is given again, Matomo measures without cookies or not at all, depending on the plugin. Plan such updates and read the numbers afterwards with this in mind.

What makes Shopware tracking reliable

  • A maintained pluginMatching Shopware version, current changelog, clear e-commerce scope.
  • A data layer for the Tag ManagerMaintain tracking in Matomo, not in the plugin.
  • Orders from the serverAd blockers and pages that do not load swallow no revenue.

Typical pitfalls

  • A plugin for Shopware 5Several older plugins only run there.
  • Two ways for the same orderBrowser and server count twice if nothing is flagged.
  • Updates without looking at cookiesShopware asks everyone again, recognition starts over.

Sources

As of 12 November 2026

FAQ

Frequently asked questions

Is there an official Matomo plugin for Shopware?

No. Matomo itself offers nothing for Shopware. Matomo's list of integrations points to third-party plugins, and the Shopware Store has several, all as subscriptions with a free trial month.

Why does my shop suddenly ask all visitors for consent again?

Since Shopware 6.7.3, the browser stores a hash of the cookie configuration. If a plugin adds or changes a cookie, the value differs: Shopware then deletes all non-essential cookies, including Matomo's, and asks again.

Does Matomo Tag Manager work with Shopware?

Yes. A plugin or the theme includes the container. For e-commerce, the Tag Manager needs a data layer with products, cart and order; Campit offers a separate plugin for this.

Where does Matomo belong in Shopware's cookie consent?

In the Statistics and Tracking group. The plugins register their cookies there, and Matomo only measures after consent or, depending on the plugin, without cookies until then.

Questions about your setup?

In an intro call we'll look at your situation together.

Book an intro call

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.