1. It is trivial to have a metric about how many requests were made for a link on a site, say a/
2. It is legally very much non-trivial to have a metric about how many requests were made to a/ followed by requests to b/
One way to solve 2. would be to change links based on earlier interaction server-side. So instead of [a/, b/], the requests would be [a/, a.b/] IMO, this should be legal, but might not under strict interpretation of the law.
User sessions were created with a URL query parameter, like `?sessionid=`, and every page would pick up the sessionid and include it in every link on the page.
> the Working Party considers that first party analytics cookies are not likely to create a privacy risk when they are strictly limited to first party aggregated statistical purposes and when they are used by websites that already provide clear information about these cookies in their privacy policy as well as adequate privacy safeguards.
[0] Section 4.3 of https://ec.europa.eu/justice/article-29/documentation/opinio...