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