AppsFlyer
Mobile attribution and marketing analytics platform that tracks app installs, in-app events, and revenue back to ad campaigns across all major networks with privacy-preserving SKAN support.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Multiple key types with different privilege levels creates confusion and risk of key misuse. No key rotation mechanism in UI — keys are long-lived. S2S devkey exposure would allow fraudulent install injection. EU data residency option available for GDPR compliance.
⚡ Reliability
Best When
A mobile app with significant paid UA spend needs to accurately attribute installs and revenue to campaigns across multiple ad networks.
Avoid When
Your app is organic-only with no paid UA, or you need real-time raw event data without the cost of an enterprise attribution platform.
Use Cases
- • Pull cohort-based ROAS data via the Pull API to automatically pause underperforming UA campaigns in connected ad networks
- • Forward server-to-server (S2S) in-app purchase events to AppsFlyer to attribute revenue to acquiring campaigns without SDK dependency
- • Use the Audiences API to build and sync high-value user segments to ad platforms for lookalike and retargeting campaigns
- • Automate fraud protection rule updates via the Protect360 API based on observed install quality thresholds
- • Query the Data Locker (raw data export) API to load attribution data into a data warehouse for custom BI reporting
Not For
- • Web-only analytics — AppsFlyer is purpose-built for mobile app attribution, not general web traffic analysis
- • Real-time in-app event processing at sub-second latency — attribution pipeline has inherent processing delays
- • Small apps with fewer than ~1,000 installs/month — attribution nuance and SKAN aggregation require volume for statistical significance
Interface
Authentication
API token (V1) and V2 tokens available; V2 tokens are app-scoped and preferred for multi-app accounts. S2S API uses the devkey (app-level key). Pull API uses account-level or app-level tokens. Different endpoints use different key types — mismatching causes confusing 403 errors.
Pricing
Pricing is not publicly listed for most plans. Enterprise contracts include SLA guarantees, dedicated support, and Data Locker raw data access. SKAN features available across all tiers.
Agent Metadata
Known Gotchas
- ⚠ Pull API V1 and V2 have different base URLs and token types — V1 uses account token, V2 uses app-level token; mixing them returns 403 without clear explanation
- ⚠ Data Locker reports are generated on a schedule (every ~2 hours) — agents polling for real-time data will get stale results
- ⚠ SKAN aggregated data has conversion value windows that must be configured in the AppsFlyer dashboard before iOS attribution data is meaningful
- ⚠ S2S event names must exactly match event names configured in the dashboard for revenue attribution to work; typos create orphan events silently
- ⚠ CSV Pull API responses include a BOM header that can corrupt JSON parsing if the response is not properly decoded as UTF-8-BOM
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for AppsFlyer.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.