• Resolved alain2

    (@alain2)


    Hi

    While I fully understand to be very privacy compliant (the reason I use statify), it would be nice to have aggregated nr of resolution/browser.

    For example a sum for every month. For 99% of uses it’s enough to have an idea of the type of technology used in the last months. It would take only a little bit DB space and given the big aggregation no privacy risk.

    Alain

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Stefan Kalscheuer

    (@stklcode)

    Note that Statify does not aggregate on every hit. Each visit is stored in a single DB row and aggregated for visualization when accessing the dashboard.

    With UserAgent (full string) and exact resolution one might recognize at least some visitors.

    Second point: How to aggregate?
    There are thousands of Browsers out there, think of all Chromium-based derivates… Major 10 + “others”, always last part of the String, …? Versions?
    Even worse for resolution. width classes, height classes, pixel-count classes, what about DPI?

    I’m not sure if that kind of statistics really fits the scope of Statify. Could be an idea for a possible Extension Plugin though.

    Thread Starter alain2

    (@alain2)

    Well I know that statify doesn’t aggregate on every hit. But registration of resolution and/or browser and/or OS on evry hit is a privacy problem.

    If only those are aggregated monthly from the start (in a separate table) the privacy will be far better preserved.

    An extension seems difficult because the javascript call has to be changed and also the logging part. Those seem to be rather specific for statify itself.

    Plugin Support Stefan Kalscheuer

    (@stklcode)

    That’s not, how Statify works. Different tracking call, different aggregation technique, different data model… Just not the same Plugin anymore.

    Also several hooks might have to be adjusted when different data is processed.

    For difficulty:
    Browser can be easily tracked without adjusting the JS. On the other hand resolution with non-JS tracking is obviously a bit of a challenge.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘aggregated info about resolution/browser’ is closed to new replies.