Transparency alternatives to HockeyStack
Other Marketing attribution vendors we measure, sorted by how much we found at them and not at HockeyStack. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from HockeyStack on at least one criterion we measured for both. Public transparency score, not a product or security rating.
HockeyStack has 8 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at HockeyStack” is the one that closes them.
| Vendor | Score | Found there, not found at HockeyStack | Found at HockeyStack, not found there | |
|---|---|---|---|---|
| Supermetricssupermetrics.comSee also Transparency alternatives to Supermetrics | 65/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| AppsFlyerappsflyer.comSee also Transparency alternatives to AppsFlyer | 50/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Dubdub.coSee also Transparency alternatives to Dub | 52/100 | 4 Public pricing, Uptime SLA with a figure, security.txt (RFC 9116), +1 | 1 Data location stated | Compare |
| Improvadoimprovado.ioSee also Transparency alternatives to Improvado | 30/100 | 4 Public pricing, Certifications named, security.txt (RFC 9116), +1 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Cometlycometly.comSee also Transparency alternatives to Cometly | 65/100 | 3 Subprocessor list, Certifications named, Named privacy contact | nothing | Compare |
| Funnelfunnel.ioSee also Transparency alternatives to Funnel | 43/100 | 3 Status page with history, Public pricing, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Short.ioshort.ioSee also Transparency alternatives to Short.io | 43/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| ReportGardenreportgarden.comSee also Transparency alternatives to ReportGarden | 39/100 | 3 Subprocessor list, Public pricing, Named privacy contact | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Stapestape.ioSee also Transparency alternatives to Stape | 39/100 | 3 Public pricing, Uptime SLA with a figure, Named privacy contact | 2 Data location stated, Notice before subprocessors change | Compare |
| Tealiumtealium.comSee also Transparency alternatives to Tealium | 39/100 | 3 Subprocessor list, Certifications named, Named privacy contact | 2 Data processing agreement, Data location stated | Compare |
| Swydoswydo.comSee also Transparency alternatives to Swydo | 30/100 | 3 Public pricing, No third-party tracking before consent, Named privacy contact | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Addingwelladdingwell.comSee also Transparency alternatives to Addingwell | 26/100 | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 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.