Alternatives to Parse.ly
Other Web analytics vendors we measure, sorted by how much they publish that Parse.ly does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Parse.ly on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Parse.ly has 8 gaps in what we could measure: Data processing agreement, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Parse.ly does not” is the one that closes them.
| Vendor | Score | Publishes, and Parse.ly does not | Parse.ly publishes, and they do not | |
|---|---|---|---|---|
| Amplitudeamplitude.com | 74/100 | 6 Data processing agreement, Status page with history, Public pricing, +3 | 1 Subprocessor list | Compare |
| Contentsquarecontentsquare.com | 61/100 | 6 Status page with history, Public pricing, Certifications named, +3 | 2 Data location stated, Named privacy contact | Compare |
| Mixpanelmixpanel.com | 85/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | nothing | Compare |
| PostHogposthog.com | 85/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | nothing | Compare |
| Fathom Analyticsusefathom.com | 65/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 2 Subprocessor list, Named privacy contact | Compare |
| FullStoryfullstory.com | 57/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Matomomatomo.org | 52/100 | 3 Data processing agreement, Public pricing, Certifications named | 1 Subprocessor list | Compare |
| Plausibleplausible.io | 48/100 | 3 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Cabinwithcabin.com | 33/100 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | 2 Subprocessor list, Named privacy contact | Compare |
| Heapheap.io | 30/100 | 3 Status page with history, Public pricing, Certifications named | 3 Subprocessor list, Data location stated, Named privacy contact | Compare |
| Hotjarhotjar.com | 30/100 | 3 Status page with history, Public pricing, Certifications named | 3 Subprocessor list, Data location stated, Named privacy contact | Compare |
| LogRocketlogrocket.com | 30/100 | 3 Status page with history, Public pricing, Certifications named | 3 Subprocessor list, 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.