Transparency alternatives to Supermetrics
Other Marketing attribution vendors we measure, sorted by how much we found at them and not at Supermetrics. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Supermetrics on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Supermetrics has 4 gaps in what we could measure: Data processing agreement, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Supermetrics” is the one that closes them.
| Vendor | Score | Found there, not found at Supermetrics | Found at Supermetrics, not found there | |
|---|---|---|---|---|
| Dubdub.coSee also Transparency alternatives to Dub | 52/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 4 Subprocessor list, Data location stated, Status page with history, +1 | Compare |
| Cometlycometly.comSee also Transparency alternatives to Cometly | 65/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Analyzifyanalyzify.comSee also Transparency alternatives to Analyzify | 57/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Factors.aifactors.aiSee also Transparency alternatives to Factors.ai | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 5 Subprocessor list, Data location stated, Status page with history, +2 | Compare |
| HockeyStackhockeystack.comSee also Transparency alternatives to HockeyStack | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 6 Subprocessor list, Status page with history, Public pricing, +3 | Compare |
| Stapestape.ioSee also Transparency alternatives to Stape | 39/100 | 2 Data processing agreement, Uptime SLA with a figure | 5 Subprocessor list, Data location stated, Status page with history, +2 | Compare |
| AppsFlyerappsflyer.comSee also Transparency alternatives to AppsFlyer | 50/100 | 1 Uptime SLA with a figure | 2 Data location stated, Certifications named | Compare |
| Clarisightsclarisights.comSee also Transparency alternatives to Clarisights | 43/100 | 1 Data processing agreement | 4 Subprocessor list, Status page with history, Public pricing, +1 | Compare |
| Northbeamnorthbeam.ioSee also Transparency alternatives to Northbeam | 43/100 | 1 Notice before subprocessors change | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| Tealiumtealium.comSee also Transparency alternatives to Tealium | 39/100 | 1 Notice before subprocessors change | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Whatagraphwhatagraph.comSee also Transparency alternatives to Whatagraph | 39/100 | 1 Data processing agreement | 5 Subprocessor list, Status page with history, Certifications named, +2 | Compare |
| DashThisdashthis.comSee also Transparency alternatives to DashThis | 30/100 | 1 Data processing agreement | 6 Subprocessor list, Data location stated, Status page with history, +3 | 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.