• Extensions
  • FriendsOfFlarum Analytics - tracking user visits

Anonymous43 which provider?

For Google Analytics, visit the Google Analytics dashboard on google's domain.

For Matomo, visit your Matomo instance. Optionally Matomo can be shown inside an iframe in the admin panel as described in the settings.

So, it has absolutely nothing to do with flarum admin panel. In theory I can just view the stats from google without this extension.

    Anonymous43 yes, that's how it's intended to be used.

    The role of this extension is to perform the collection of the data. It's used instead the tracking code you usually paste in the header/footer. The code added by this extension tracks navigation inside of the single page app, which is not done if you just paste the code Google gives you.

    2 months later

    I can't see google analytics Tracking Code ID starting with " UA-XXXX" ...... I can only found the Tracking Code ID Like " G-XXXX " .

      2 months later

      Is it compatible with Flarum 1.2?
      Extiverse helper tells it is not 🙁

        almalino that was a temporary bug. The helper should now report things differently. Sorry for the confusion.

        7 days later
        9 days later

        matomo:
        Refused to display 'https://www.*****.com:9000/' in a frame because it set 'X-Frame-Options' to 'deny'.

        [General]
        enable_framed_pages=1

        无效

        3 months later

        r4nchy I have not studied the changes yet. Do you know whether it requires modifications to the javascript we embed in the extension?

        17 days later

        Hello, I would like to report a bug. I have disabled all extension and discovered that this extension is causing errors in my website:

        Console:

        45
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        6
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        15
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        7
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        12
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        7
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        12
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        32
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18
        3
        sw:57 Uncaught ReferenceError: fetchEvent is not defined
            at sw:57:18

          girefko that code is not in this extension, nor it is in Flarum core. The sw: reference means it comes from a service worker I believe. This extension doesn't use service workers.

          Wasn't it a PWA extension issue? You might need to clear your browser cache and storage after removing that extension because a service worker won't uninstall itself automatically.

            clarkwinkelmann You are right.. I was using Chrome all along and no matter what I did - the error would not go away. I then switched to Firefox and the error disappeared.

            a month later

            luceos So you are saying I should be the sacrificial lamb 😆

            I can possibly try tomorrow morning at the start of the new month....

            @luceos after some investigation it looks liek its close but not fully there. The Javascritp Google Analytics 4 gives is

            <script async src="https://www.googletagmanager.com/gtag/js?id=G-personalCodeGoesHere"></script>
            <script>
              window.dataLayer = window.dataLayer || [];
              function gtag(){dataLayer.push(arguments);}
              gtag('js', new Date());
            
              gtag('config', 'G-personalCodeGoesHere');
            </script>

            Looking at my own page source it looks like using this in the current state it is just missign this line:

            gtag('config', 'G-personalCodeGoesHere');

            No idea how much that one line matters... but may need to be added for this extension to work with the new Google Analytics 4.