You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to ask for consent to use the analytics cookie. When you go to setup the analytics property, there's a prompt which talks about a few free cookie consent library options.
Alternatively, we could drop analytics entirely and then not worry about this. We have sometimes used the analytics data in the past, but not every year, and it's not essential.
We don't have many self-hosted Code4Lib services (the wiki?) and I think it would be challenging to run an analytics service, keep it up to date, pay for it somehow. If we're concerned about Google having our data, I lean towards not enabling analytics at all.
I'm not usually anti-Google on main, just personally, but I wouldn't be sad if we didn't do analytics. Or at least there's a conversation to be had about whether we enable analytics because we care about that data and use it to make code4lib/code4lib con better or because it's a reflex.
Activity
triplingual commentedon Aug 18, 2025
Any possibility of using an analytics tool like Matomo that stores data ~locally? (I am not the Matomo maven, just know of it.)
phette23 commentedon Aug 18, 2025
We don't have many self-hosted Code4Lib services (the wiki?) and I think it would be challenging to run an analytics service, keep it up to date, pay for it somehow. If we're concerned about Google having our data, I lean towards not enabling analytics at all.
triplingual commentedon Aug 27, 2025
I'm not usually anti-Google on main, just personally, but I wouldn't be sad if we didn't do analytics. Or at least there's a conversation to be had about whether we enable analytics because we care about that data and use it to make code4lib/code4lib con better or because it's a reflex.