3 ms·

There are also "tiny" solutions for analytics. I'm working on Plausible Analytics which is only 1.4 KB right now and provides a modern dashboard. It also doesn

There are also "tiny" solutions for analytics. I'm working on Plausible Analytics which is only 1.4 KB right now and provides a modern dashboard. It also doesn't use cookies and doesn't collect personal data so you're not required to show the cookie/GDPR prompts which would make tiny websites much less tiny. See https://plausible.io/ https://plausible.io/ There's an issue on our Github which will help us perhaps reduce it to under 1 KB too. We're working on that https://github.com/plausible-insights/plausible/issues https://github.com/plausible-insights/plausible/issues

webspaceadam 6y ago
this looks amazing! I might consider using this for my sideproject and some a/b testing.
nicbou 6y ago
If you don't need detailed information about visitors, you can also consider server log analytics.
def_true_false 6y ago
You claim that using your analytics doesn't require user consent: > "Plausible does not use cookies and does not collect any personal data. This makes us compliant with the different cookie laws and privacy regulations. It means that you are not required to annoy your visitors with a cookie notice if you’re using Plausible analytics." [1] > "Compliant with privacy regulations: Google Analytics places cookies and collects a lot of data from your visitors. You’re required to have a privacy policy, to show a cookie banner and to obtain consent for GDPR. Plausible Analytics doesn’t use cookies and doesn’t track personal data so you don’t need to annoy your visitors or worry about those prompts." [2] It would seem you are collecting PII and processing it server side (?), e.g. calculate_fingerprint here [3]. Care to explain how that doesn't require user consent? [1] https://plausible.io/data-policy#plausible-is-compliant-with-the-cookie-law-gdpr-ccpa-and-pecr-out-of-the-box https://plausible.io/data-policy#plausible-is-compliant-with... [2] https://plausible.io/blog/blog-post-changed-my-startup#new-plausible-analytics-individual-product-pages https://plausible.io/blog/blog-post-changed-my-startup#new-p... [3] https://github.com/plausible-insights/plausible/blob/master/lib/plausible_web/controllers/api/external_controller.ex#L85 https://github.com/plausible-insights/plausible/blob/master/...
- markosaric 6y ago
  This is what we do: Instead of setting a cookie with a unique user ID, we simply count the number of unique IP addresses that accessed your website to determine the visitor count. To enhance the visitor privacy, we don’t actually store the raw visitor IP address in our database or logs. We run it through a one-way hash function to scramble the raw IP addresses and make them impossible to recover. To further enhance visitor privacy, we add the website domain to their IP hash. This means that the same user will never have the same IP hash on two different websites. If we didn’t do this, the hash would effectively act like a third-party (cross-domain) cookie. Network Address Translation allows many unique users to share the same public IP address. For this reason we also add the User-Agent string to the hash, although we don’t store the actual User-Agent string.

webspaceadam 6y ago

this looks amazing! I might consider using this for my sideproject and some a/b testing.

nicbou 6y ago

If you don't need detailed information about visitors, you can also consider server log analytics.

def_true_false 6y ago

You claim that using your analytics doesn't require user consent: > "Plausible does not use cookies and does not collect any personal data. This makes us compliant with the different cookie laws and privacy regulations. It means that you are not required to annoy your visitors with a cookie notice if you’re using Plausible analytics." [1] > "Compliant with privacy regulations: Google Analytics places cookies and collects a lot of data from your visitors. You’re required to have a privacy policy, to show a cookie banner and to obtain consent for GDPR. Plausible Analytics doesn’t use cookies and doesn’t track personal data so you don’t need to annoy your visitors or worry about those prompts." [2] It would seem you are collecting PII and processing it server side (?), e.g. calculate_fingerprint here [3]. Care to explain how that doesn't require user consent? [1] https://plausible.io/data-policy#plausible-is-compliant-with-the-cookie-law-gdpr-ccpa-and-pecr-out-of-the-box https://plausible.io/data-policy#plausible-is-compliant-with... [2] https://plausible.io/blog/blog-post-changed-my-startup#new-plausible-analytics-individual-product-pages https://plausible.io/blog/blog-post-changed-my-startup#new-p... [3] https://github.com/plausible-insights/plausible/blob/master/lib/plausible_web/controllers/api/external_controller.ex#L85 https://github.com/plausible-insights/plausible/blob/master/...

markosaric 6y ago
This is what we do: Instead of setting a cookie with a unique user ID, we simply count the number of unique IP addresses that accessed your website to determine the visitor count. To enhance the visitor privacy, we don’t actually store the raw visitor IP address in our database or logs. We run it through a one-way hash function to scramble the raw IP addresses and make them impossible to recover. To further enhance visitor privacy, we add the website domain to their IP hash. This means that the same user will never have the same IP hash on two different websites. If we didn’t do this, the hash would effectively act like a third-party (cross-domain) cookie. Network Address Translation allows many unique users to share the same public IP address. For this reason we also add the User-Agent string to the hash, although we don’t store the actual User-Agent string.