To somewhat close my own loop - I think we've identified the issue and are working on a solution.
By default, Matomo shows 500 rows in reports. Any page usage that's the 501st row or beyond is lumped together into a single "other" row. The pages I was looking for were all very low usage, so weren't appearing in the top 500 rows in reports with large date ranges: https://matomo.org/faq/how-to/faq_54/ We can change the 500 row default, and are figuring out how many rows we can ask our local resources to regularly process. We have some monthly general usage reports in Google Analytics with over 200,000 rows, so it may be a challenge. I'm glad to see interest in Matomo more broadly, and would still love to chat with anybody who's been using it for a while at scale. -Chad --- Chad Haefele he/him/his Head of User Experience UNC University Libraries chaef...@email.unc.edu -----Original Message----- From: Haefele, Chad Mark Sent: Thursday, November 17, 2022 9:41 AM To: Code for Libraries <CODE4LIB@LISTS.CLIR.ORG> Subject: Matomo With the July 2023 Google Analytics transition looming, we've been evaluating Matomo as a possible replacement. Has anyone been robustly using Matomo who'd be willing to chat about it? I'm interested in general best practices, but also some specific troubleshooting: Matomo was looking promising until I noticed a concerning reporting issue on low-use pages: -If I look for usage of those pages on a single specific day, Matomo reports correctly. -If I run the same report for a date range that includes that same day, Matomo reports no usage. We've reprocessed the data from raw logs as Matomo suggests, without improvement. Thank you, Chad --- Chad Haefele he/him/his Head of User Experience UNC University Libraries chaef...@email.unc.edu
