Since the whole cookie consent thing becomes more and more an even more serious topic server side tracking becomes more interesting. I’m not an expert on the current law etc. so if somebody knows more please give your input.
We can do it after Neos resolves a node, but it has to work with the FullPageCache f.e…
Then we would already know that it’s a page and can retrieve title, etc.
A queue is a possibility, maybe make it available as an option as long as we don’t have a queue as core dependency.
my2c, without knowing matomo in-depth (we actually could do that for google analytics as well)
As soon as you store any personal data (i.e. IP Address), you need consent for that. Not absolutely clear what happens if we anonymize the IP Address (which we should do if we save it)
If you set a cookie (also using local storage or else) which is not technically necessary, you have to inform why and what you do with it.
Server side we mostly can track page views, so we would need to operate on document (url) level.
We could also track interaction (like pagination, forms, …) which would give some more reliable data with regards to conversions. (Could a tracking-API like “@tracking” in Fusion be helpful?)
If you also add tracking on webserver level, you can track downloads like pdfs as well (which might be one of the benefits of server side compared to client-side)
