• Extensions

  • FriendsOfFlarum Analytics - tracking user visits

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.

                  Gatsu I think this extension needs to be updated. I added what I believe needs to be changed in my previous comment.

                  Just need someone from the FOF team to take a look and update.

                    14 days later

                    Tobi mine looks like it's reporting. But I do believe updates are needed

                      a month later

                      1.1.0

                      This extension should have supported GA4 out of the box, since none of the syntax used by this extension differs between UA and GA4.

                      If you have issues with page view reporting, make sure that your web data stream has Enhanced measurement enabled, and that Page views are configured with the Page changes based on browser history events option enabled.

                      Changes

                      • Explicitly address GA4 compatibility
                        • Using GA4 will not manually report page views to Google Analytics, like was done for UA
                        • Please note, this means that instead of a page_path property on your page_view events, the full URL will be contained in the page_location property
                      • Pass user IDs to Google Analytics for user-based tracking between devices, sessions and accounts

                      Updating

                      composer require fof/analytics:"*"
php flarum cache:clear

                      Checking configuration

                      If you use GA4, you can check everything is running smoothly by checking the DevTools network tab. This should show pings to collect?v=2&.... Clicking on one of these, then checking the Payload tab should show...

                      • tid matching your G-... tracking ID
                      • dl matching the page you visited
                      • dr matching the page you just moved from
                      • uid matching your Flarum user ID
                      • ...and various other tracking properties