Hello Matomo Community,
We are integrating Matomo Analytics (on-premise build) to track user interaction events across dynamic multi-step form submissions on our web portal (hdclaims.co.uk).
Issue Description:
Standard pageview tracking via _paq.push(['trackPageView']) executes cleanly. However, when triggering custom Form Analytics events (_paq.push(['FormAnalytics::scanForForms'])) after dynamic DOM node updates, the analytics collector endpoint drops incoming tracking requests with an HTTP 400 Bad Request error.
Technical Setup:
-
Matomo Version: Matomo On-Premise 5-x
-
Tracking Method: JavaScript Tracker (
matomo.js) + Tag Manager -
Target Domain:
(hdclaims.co.uk) -
Browsers Affected: Google Chrome 125, Mozilla Firefox 126
Steps Taken:
-
Configured custom dimensions to capture form field focus states.
-
Verified that
setCookieDomainandsetDomainsmatch the root domain configuration. -
Inspected browser network tab; payload parameters fail parsing when dynamic form steps push state via History API (
pushState).
Is there a specific JavaScript tracker configuration or execution delay required when calling scanForForms on dynamic .co.uk web applications with single-page step routing?
Any technical insights from analytics engineers would be greatly appreciated!