Alternatives to Addingwell
Other Marketing attribution vendors we measure, sorted by how much they publish that Addingwell does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Addingwell on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Addingwell has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Certifications named, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Addingwell does not” is the one that closes them.
| Vendor | Score | Publishes, and Addingwell does not | Addingwell publishes, and they do not | |
|---|---|---|---|---|
| Cometlycometly.com | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 2 Status page with history, Uptime SLA with a figure | Compare |
| Analyzifyanalyzify.com | 57/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| Factors.aifactors.ai | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Status page with history, Uptime SLA with a figure | Compare |
| Northbeamnorthbeam.io | 52/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| HockeyStackhockeystack.com | 48/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 Status page with history, Uptime SLA with a figure | Compare |
| Tealiumtealium.com | 48/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| DashThisdashthis.com | 43/100 | 3 Data processing agreement, Data location stated, Public pricing | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| Elevargetelevar.com | 39/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| Dreamdatadreamdata.io | 35/100 | 3 Data location stated, Public pricing, Certifications named | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | Compare |
| Improvadoimprovado.io | 30/100 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | 2 Status page with history, Uptime SLA with a figure | Compare |
| Funnelfunnel.io | 43/100 | 2 Data location stated, Public pricing | 1 Uptime SLA with a figure | Compare |
| BlueConicblueconic.com | 39/100 | 2 Data location stated, Certifications named | 1 Uptime SLA with a figure | 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.