On Sat, 2 Nov 2024, Bob Weinand wrote: > On 1.11.2024 22:41:29, Larry Garfield wrote: > > In a similar vein to approving the use of software, Roman Pronskiy > > asked for my help putting together an RFC on collecting analytics > > for PHP.net. > > > > https://wiki.php.net/rfc/phpnet-analytics
[snip] > Let's see what the RFC names: > > Time-on-page > Whether they read the whole page or just a part > Whether they even saw comments > > Yes, these need a client side tracker. But I doubt the usefulness of > the signal. You don't know who reads that. Is it someone who is > already familiar with PHP and searches a detail? He'll quickly just > find one part. Is it someone who is new to PHP and tries to understand > PHP. He may well read the whole page. But you don't know that. The Matomo JS tracker also does not collect all this data, it only improves the "time spent on each page": https://developer.matomo.org/guides/tracking-javascript-guide#accurately-measure-the-time-spent-on-each-page I make no comments about how useful this is. > How much are users using the search function? Is it finding what they > want, or is it just a crutch? > > How much is probably greppable from the server logs as well. The PHP client tracker that was mentioned in this thread, has a specific feature for this: https://github.com/matomo-org/matomo-php-tracker/blob/master/MatomoTracker.php#L910 The JS version can't track our internal search systems, and I am not sure it use the HTTP referrer to see whether the entry came through a Google (or other third party) search. > And yeah, server logs are more locked down. But that's something you > can fix. I hope that the raw analytics data is just as locked down as > the server logs... The raw server logs will definitely not be opened up, and neither will any other raw data. cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/support mastodon: @derickr@phpc.social @xdebug@phpc.social
