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