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