I’ve tried to add in </head>  <script type="text/discourse-plugin" version="0.2"> // Track page views api.onPageChange((url, title) => { if (_paq) { try { var currentUser = PreloadStore.get('currentUser'); _paq.push…

You should use this Script to enable Matomo analytics on Discourse

Thanks you, that should solve my current problem… But shouldn’t it be possible to inject custom js in those sections anyhow ?

I’ve installed the component and activated it for “Default” theme … and doesn’t seem to work any better :-/

Did you check your browser logs? Have you added your Matomo script host to the CSP setting list?

You got it right… I was not aware of a CSP setting…

That is something the browser logs will always warn about, so always check those.

Hi @Falco I think I’ve got the same problem with Matomo not working with Discourse. It is what the support team of Matomo told me when I opened a ticket on their github : Matomo support : “I checked your website and the configured CSP is preventing to load our tracker. You’ll want to have a look a…

I see the Matomo script loading correctly on hec.fm, so you’re not having a CSP issue. Maybe it’s something else on the Matomo side? Also the rows below https://stats.hec.fm/Matomo in your screenshot above are unnecessary.

Oublié de modifier CSP lors de l'ajout du code de suivi via un composant personnalisé

Assistance produit

Antony Janvier 2, 2021, 4:37 3

Merci, cela devrait résoudre mon problème actuel…

Mais ne devrait-il pas être possible d’injecter du JS personnalisé dans ces sections de toute façon ?

Sujet		Réponses	Vues
Matomo Analytics Theme component official , matomo-analytics	52	19086	Janvier 13, 2025
Matomo analytics is not working after recent update Product Support	13	2891	Octobre 23, 2018
How can I embed tracking JS into Discourse Data & reporting	2	898	Juin 25, 2021
Mitigate XSS Attacks with Content Security Policy Site Management how-to , content-security-policy	30	25749	Juin 13, 2023
Javascript not working in customised areas Product Support	8	1189	Mai 14, 2019

Oublié de modifier CSP lors de l'ajout du code de suivi via un composant personnalisé

Sujets connexes