Transparency alternatives to Whatagraph
Other Marketing attribution vendors we measure, sorted by how much they publish that Whatagraph does not. 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 7 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Whatagraph does not” is the one that closes them.
| Vendor | Score | Publishes, and Whatagraph does not | Whatagraph publishes, and they do not | |
|---|---|---|---|---|
| Supermetricssupermetrics.com | 65/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 1 Data processing agreement | Compare |
| Tealiumtealium.com | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Cometlycometly.com | 65/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 1 Public pricing | Compare |
| Dubdub.co | 52/100 | 3 Uptime SLA with a figure, security.txt (RFC 9116), Notice before subprocessors change | 1 Data location stated | Compare |
| AppsFlyerappsflyer.com | 50/100 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 2 Data processing agreement, Data location stated | Compare |
| Analyzifyanalyzify.com | 57/100 | 2 security.txt (RFC 9116), Notice before subprocessors change | 1 Named privacy contact | Compare |
| Northbeamnorthbeam.io | 52/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Data processing agreement, Named privacy contact | Compare |
| Short.ioshort.io | 35/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Treasure Datatreasuredata.com | 35/100 | 2 Status page with history, Certifications named | 3 Data processing agreement, Public pricing, Named privacy contact | Compare |
| Improvadoimprovado.io | 30/100 | 2 Certifications named, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Addingwelladdingwell.com | 26/100 | 2 Status page with history, Uptime SLA with a figure | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| BlueConicblueconic.com | 26/100 | 2 Status page with history, Certifications named | 3 Data processing agreement, Data location stated, 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.