1
0 Comments

Why We Built Attribr

We run 25+ apps across the MRVL portfolio. Every single one needs attribution. And every existing MMP caused the same problems:

The Problems:

  • Rejection risk — AppsFlyer, Adjust, Branch all require IDFA + NSUserTrackingUsageDescription. Apple reviews every submission. We've seen apps rejected over tracking wording alone.

  • TestFlight blindness — You can't track attribution in TestFlight with any major MMP. So you launch to beta, watch your conversion metrics flatline, and have zero idea why. You wait weeks for App Store approval just to see your data.

  • Referral gap — We wanted to know which friend drove which subscriber. Not just "TikTok drove 100 installs." None of them do this.

  • Bloat & cost — AppsFlyer is 1.5MB. Adjust's SDK is 350KB. They're enterprise tools charging $1K+/month. We're bootstrapped indie devs.

The Solution: We realized everything we needed was already in iOS and Android natively: SKAdNetwork and Play Install Referrer API. No third-party SDK. No permissions. Zero rejections.

3 lines of code. Done.

We've been running Attribr on all 25 MRVL apps for 6+ months. Zero rejections. Full TestFlight attribution. Referral tracking that no other platform has.

For indie devs: You shouldn't need a $10K/year subscription to track installs. You shouldn't hold your breath waiting for App Store approval because you don't know if your attribution will break. You shouldn't lose visibility into your metrics between TestFlight and launch.

Attribr is what we wished existed when we started building.

posted toAvatar for product Attribr
Attribr