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