roadmap
roadmap copied to clipboard
Upgrade Google services
I received a notice from Google today that they are sun-setting 'Universal Analytics'.
We will need to upgrade to Google Analytics 4. The EOL for v3 is July of 2023.
This is a major upgrade for GA and involves completely different data points. Here is a useful article on the differences related to the metrics collected by each version.
We need to see if we can continue to support client tracker codes.
We will only have access to historical v3 metrics for an additional 6 months after EOL. The good news though is that v3 and v4 can be run in parallel, so the sooner we upgrade the better as v4 will be like starting from scratch with no historical context.
We should also consider upgrading to reCaptcha3 which provides a seamless user interface (the user doesn't see anything)
This is starting to be a problem for our users, and it seems that Google no longer provides a mechanism to generate a UA tracker code. We should discuss how many partners are utilizing this feature and what needs to be implemented to continue supporting this integration.
@mariapraetzellis FYI C. Nancarrow is in the Google Analytics working group. If you haven't already, we should check if this feature is on their radar with the UA upgrade.
I've seen some recent conversations about an alternative to GA on the Code4Lib listserv. It's called Matomo which has fairly reasonable pricing and free if the site has relatively low traffic and hosted on premise.
Might be an option for some and a benefit I guess is that you control your analytics data.
Whenever we get around to this issue we should also address #3298 and #3259
Is DMPTool using GA4 yet or is it still on Universal Analytics? https://support.google.com/analytics/answer/9539598?hl=en
From: Brian Riley @.> Sent: Thursday, March 9, 2023 7:30 AM To: DMPRoadmap/roadmap @.> Cc: Marisa Strong @.>; Comment @.> Subject: Re: [DMPRoadmap/roadmap] Upgrade Google services (Issue #3160)
CAUTION: EXTERNAL EMAIL
Whenever we get around to this issue we should also address #3298https://github.com/DMPRoadmap/roadmap/issues/3298 and #3259https://github.com/DMPRoadmap/roadmap/issues/3259
— Reply to this email directly, view it on GitHubhttps://github.com/DMPRoadmap/roadmap/issues/3160#issuecomment-1462254952, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGF4L24DNEJN5GQBMPALX3W3HZPXANCNFSM5TZLWVOQ. You are receiving this because you commented.Message ID: @.***>
DMPRoadmap and DMPTool is still on universal
I've just looked at this topic.
We use an on-premise matomo instance.
For now, I've just hardcoded the javascript matomo code in application.html.erb but would be cool if we could have an integration for such case. Like:
+++ <% if Rails.configuration.x.matomo_onprem_analytics.present? %>
+++ <%= javascript_include_tag "matomo" %>
+++ <% end %>
<%= javascript_include_tag "application", "data-turbo-track": "reload", defer: true %>
<%= stylesheet_link_tag "application", "data-turbo-track": "reload" %>
</head>
what do you think?
would you accept a PR therefore?
@StCyr, apologies for the delay in getting back, I've been on leave, this is my first week back. Has this been resolved?