Alternatives to Chartbeat
Other Web analytics vendors we measure, sorted by how much they publish that Chartbeat does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Chartbeat on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Chartbeat has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Chartbeat does not” is the one that closes them.
| Vendor | Score | Publishes, and Chartbeat does not | Chartbeat publishes, and they do not | |
|---|---|---|---|---|
| Contentsquarecontentsquare.com | 61/100 | 7 Subprocessor list, Public pricing, Certifications named, +4 | 2 Data location stated, Named privacy contact | Compare |
| Mixpanelmixpanel.com | 85/100 | 6 Data processing agreement, Subprocessor list, Public pricing, +3 | nothing | Compare |
| PostHogposthog.com | 85/100 | 6 Data processing agreement, Subprocessor list, Public pricing, +3 | nothing | Compare |
| Amplitudeamplitude.com | 74/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | nothing | Compare |
| Fathom Analyticsusefathom.com | 65/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | 2 Status page with history, Named privacy contact | Compare |
| FullStoryfullstory.com | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Matomomatomo.org | 52/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 1 Status page with history | Compare |
| Plausibleplausible.io | 48/100 | 3 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change | 1 Status page with history | Compare |
| TelemetryDecktelemetrydeck.com | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Status page with history | Compare |
| Cabinwithcabin.com | 33/100 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | 2 Status page with history, Named privacy contact | Compare |
| Heapheap.io | 30/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Hotjarhotjar.com | 30/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.