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