Matomo Analytics: setup and help

Follow the steps in Quick start.

Open Configure from Module Manager. You need an existing self-hosted Matomo installation or Matomo Cloud site. Configure the site's ecommerce reporting in Matomo. The module does not install or host Matomo.

Use a base URL such as https://analytics.example.com/ or https://example.com/matomo/. The normalizer adds a trailing slash and removes a final matomo.php or piwik.php. It rejects credentials, query strings and fragments. The browser loads matomo.js; browser and server tracking use matomo.php under that base.

Set Matomo site currency even if you use browser-only purchases. Matomo uses its site's currency, so this integration holds monetary events when the order currency is missing or differs. It does not convert amounts. Configure a separate appropriate site for a different reporting currency rather than relabeling an amount.

The consent reader supports Cookies Revolution, Cookie Banner and the shared Cookiebot, OneTrust and TCF readers. Test your category and service mapping. Consent is checked when sending, and withdrawals are persisted through a private endpoint. An absent CMP decision is not treated as permission. A supported detected CMP still applies if the module's respect switch is off.

Each standard switch defaults to Yes. Turn off events you do not need.

The current cart event path records an event. It does not send an ecommerce cart-update total merely because an add button was clicked. Search terms that look like email addresses or long number sequences are filtered.

Track phone-link clicks, Track actual chat starts, Track confirmed contact forms and Track product engagement default to No. Form tracking requires a server-confirmed receipt. Chat tracking requires an actual supported start notification. The engagement tracker uses its shared defaults of 3 gallery interactions, 1 variant change, 1 detail interaction or 45 seconds, with once-per-product/session behavior when storage is allowed. This form has no threshold fields for those values.

Track custom events defaults to No. Custom event rules starts empty. Add rules before enabling the switch. Names accept 1 to 64 letters, digits, underscores or hyphens. You can configure up to 25 distinct names.

[
  {"event":"QuoteRequest","trigger":"click","selector":".request-quote","label":"Quote request"},
  {"event":"SalePageView","trigger":"url","url_contains":["/promotions","/sale"],"label":"Sale page"},
  {"event":"ContactPageView","trigger":"controller","controllers":["contact"],"modules":["contactform"],"label":"Contact page"},
  {"event":"ConfiguratorUsed","trigger":"event","dom_event":"mprmtmo:custom","label":"Configurator used"}
]

document.dispatchEvent(new CustomEvent('mprmtmo:custom'));

Use selector for a click rule, URL fragments for a URL rule and controllers for a controller rule. modules can accompany a controller rule. A DOM-event rule without a name uses mprmtmo:custom. once defaults to false for clicks and true for URL, controller and DOM-event rules.

The active builder maps custom rules to Matomo category Custom, the configured event as action, and the configured label as name. Arbitrary params and DOM-event details do not become Matomo properties. Use these configured rules instead of the old window.mprmtmoTrackEvent helper.

The module records the buyer's consent and staff status and queues eligible orders for the server. The worker checks enabled status, destination ownership, outbound policy, buyer consent, staff status and site currency again. If the buyer withdraws consent later, the queued purchase is not sent.

Each order is sent to a Matomo destination through one channel. When the server takes responsibility for sending a purchase, the browser does not send it; when the browser takes responsibility first, the purchase is not added to the server queue.

The purchase ID sent to Matomo is the numeric PrestaShop order ID, not the order reference. The payload includes products, tax-inclusive revenue and subtotal, tax, shipping and discount amounts. It sends only when the order currency matches Matomo site currency.

Ensure your shared MPR cron runner executes:

task: send_matomo_tracking_api
callable: mprmatomo::cronProcessMatomoTrackingAPIQueue
schedule: every:300
context: any
timeout: 30

The provider is matomo_tracking_http_api in the shared conversion queue. The worker runs in each enabled shop's context. The readiness panel shows pending, sending, sent and failed counts, plus held, terminal, suppressed and ambiguous states. A network ambiguity may require review rather than blind resending.

Check Matomo tracking readiness for Site ID, normalized URL, tracking, consent, custom rules, API queue and worker registration. Test in a customer browser with the relevant analytics/service permission.

Confirm the matomo.js request and tracker calls. Test page, product and category views, a successful cart change, wishlist, checkout, search and signup according to the enabled switches. Public HTML contains static configuration; the private endpoint supplies visitor policy and private checkout/signup context.

Place an order in your configured Matomo currency. Check its numeric order ID and amounts. If the server fallback is enabled, verify its queue admission and worker result, and confirm the browser channel did not duplicate it. Check refusal and withdrawal separately.

If nothing tracks, check the enabled switch, Site ID, URL, ownership, local dependencies, consent and staff policy. Remove another Matomo tracker that could bind to a different destination.

If purchases are missing, check Matomo site currency first. Then check Track purchases, buyer/cart/session ownership, the buyer's original consent and staff status, the channel reservation and worker status. A purchase whose consent state is unknown is held.

If a custom button does not track, update its selector and verify its rule. A successful standard cart event needs the shared commerce signal; a click alone is insufficient. The old helper and selector lists in earlier documentation do not define the current standard event detector.

Set Enable Matomo Analytics to No and save to pause this integration. Uninstall through Module Manager to remove its menu, cron registration and module configuration. The shared queue table is kept if another module uses the conversion package; otherwise its uninstall helper drops that table. The shared consent and channel tables are kept on uninstall; do not drop them manually. Manage your Matomo site and historical data in Matomo.

Use the setting names above when a reference screenshot differs from your installed version.