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