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