In order to comply with the European laws, users must have the possibility to reject piwikās cookie. Piwik offers a really simple solution for this, by including an IFrame.
Unfortunately, Discourse doesnāt allow iframe tags in postsā¦
Does anyone see a way to include this piwik iframe in Discourse TOS ?
Thanks.
This doesnāt appear to be working for me at the moment? I can add the component, and add the correct URL and siteid, but it doesnāt render anything:
I added the comments around the code to find it quicker in the page:
So I have the JS loaded into the theme customizations, and the external ātheme JavaScript fileā* is linked in my test browser, just under where I inserted it like in the screenshot in a few posts earlier ⦠BUT the requests arenāt coming through to the Matomo tracking web server.
(Tracking works fine for other non-Discourse sites, FWIW.)
Has anyone else seen that happen?
* e.g. https://discourse-cdn.example.com/standard11/theme-javascripts/{numeric_string}.js?__ws=my-discourse-forum.example.org
Iām confused why the tracking code is sending a custom variable called Anonymous. Isnāt that custom for your particular Matomo setup? It doesnāt seem like it should be there for everyone.
You have to whitelist your Matomo-URL inside the Content-Security-Policy-Header. Search for the admin setting content_security_policy_script_src and add your domain (with https:://) there
Iām having trouble making this work on my installation. Iāve installed the component, and added it to my theme, but Matomo is saying thereās no data for the site. Iād think I have the settings correct:
But Iām seeing this error in my browser console:
ā¦and when I look at the site in Matomo, I get this:
What am I missing?
Edit: Further investigation reveals that the error in the Javascript console only appears in Firefox, not in Chrome (with the latest versions of each on a Mac). And I am now seeing some results in Matomo, though Firefox is conspicuously absentāall but one of the visitors are using Chrome; the one exception is using Safari.
suggests that it could be Firefoxās ādo not trackā settings, but even when I disable them for my site, Iām getting the same error in the web console with Firefox. And Firefox doesnāt seem to be viewing this as a tracker in any event: