• Resolved janaa

    (@janaa)


    Thanks for a wonderful plugin. I am very impressed with how comprehensive it is, and its ease of use. However, I am having some problems with Tag Manager. Please forgive me if any details below are incorrect or invalid. I am new to Matomo and am inexperienced in Tag Managers.

    Problem #1: It is necessary to create a Pageview tag when selecting Tag Manager as my tracking code (via Matomo Analytics > Settings > Tracking). Otherwise, page views are not tracked. This requirement is not documented. (I had to deduce this fact through trial and error).
    Recommendation: please document this.

    Problem #2: the trigger condition “Only trigger when (optional)” is supposed to be optional, but in my experience, it was essential for Pageview tracking (for tag type Matomo Analytics). Otherwise, the tag failed to fire.
    Recommendation: If this is a univeral problem, this needs to be documented. Ideally, it would help to have a video showing how to create a Pageview tag for tag type Matomo Analytics (and not just for tag type Google Analytics as provided here (if there are different requirements for types GA and MA).

    Problem details:-
    * When creating a Matomo Analytics type tag for Pageview with tracking type “Pageview” and trigger = “Pageview”, the tag fails to fire unless I add the supposedly optional “Only trigger when all of these conditions are met” with the following value:-
    “ Page URL matches the regular expression .* ”

    Problem #3: There is no documentation or video tutorial for creating an adjusted bounce rate, for example, based on a time-on-page of at least 30 seconds.

    Problem details:
    In practice, all my events (and not just my timer event) change the bounce rate to zero. Is this how it is supposed to work, so that any event including, for example, scroll-reach, changes the bounce rate to zero?

    Incidentally, I understand from this blog post that when setting up an adjusted bounce rate in Google Tag Manager, there is an optional field for “Non-interaction” which “needs to remain as (not set) to make sure the event actually affects your bounce rate percentages.” There is no such field in the Matomo Analytics tag settings, so there appears to be no way to specify whether a tag should affect the bounce rate. Personally, I’m OK with all events affecting my bounce rate in Matomo Tag Manager, but this needs to be documented.
    Recommendation: this needs to explained in some documentation and/or a video.

    Problem #4: AVG.TIME ON PAGE in the Pages report is based exclusively on my 30-second-timer event, but fails to include times-on-page for non-timer events which are less than 30 seconds, such as when the user scrolls to 50% scroll-reach.

    Problem details:
    When an event is tracked, such as scroll-reach-50% or timer-30-seconds, these details are correctly captured in the Visits Log. When I mouse over the page view action in the Visits Log, I can see the time-on-page. However, in the Behaviour > Pages report, those visits are shown with having a bounce rate of 0% and an incorrect average time on page of zero if the user did not trigger the 30-seconds-timer event.
    Recommendation: IMHO, the AVG.TIME ON PAGE should include all the times on page as displayed in the Visits Log mouseover details, and not just times as measured by timer events.

    • This topic was modified 4 years, 5 months ago by janaa.
    • This topic was modified 4 years, 5 months ago by janaa.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Thomas

    (@tsteur)

    Thanks for your valuable feedback @janaa . Very appreciated.

    Problem 1:
    I’ve documented this now in the app so it will be more clear in the future, thanks for this. It will be available in the next update.

    Problem 2:
    The trigger conditions are definitely optional and it should not be needed. Maybe some cached container version was being tested or there was some other issue. Maybe you could try to remove that optional condition again and release a new version? This should work. If there’s still an issue, feel free to send us a link to the page where we can reproduce this to [email protected] and we’ll be happy to investigate further.

    Problem 3:
    Unfortunately we don’t support non-interactive events so far. We have an open issue for this here: https://github.com/matomo-org/matomo/issues/9199

    Problem 4:
    Unfortunately, because we don’t have non-interactive events yet the average time on page might not be always correct when events are triggered on the page. It’s basically connected to problem 3. Additionally, the time spent on the last page view (if there is no event happening on that page) is currently always counted as 0s unfortunately. We have an issue for this in https://github.com/matomo-org/matomo/issues/9539

    We classified both these issues as major issues as they are quite important and I’m hoping that we can fix them in the next year.

    I hope this helps @janaa ?

    Thread Starter janaa

    (@janaa)

    Thanks so much for your thoughtful and thorough reply. I’m sorry I didn’t respond earlier to say thank you … I got diverted with several urgent projects. I will perhaps return here and respond in more detail in the coming months.

    Great support, much appreciated! ??

    Thank you both for these informations.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Tag Manager problems’ is closed to new replies.