What Three-line integration actually does

The problem with 'just integrate'

Most attribution SDKs treat integration like a tax. They want dependencies. They want network calls at startup. They want permission dialogs. They want you to read documentation that assumes you've read their other documentation first. By the time you've finished integrating, you've already made three architectural decisions that will haunt you for the next two years.

Attribr does the opposite. Three lines in Swift. Three lines in Kotlin. Then you're done. No third-party dependencies. No extra frameworks to maintain. No launch-time network calls blocking your app startup. We hit sub-50ms overhead on a real device because we decided early that indie developers shouldn't have to choose between knowing where their installs come from and keeping their app snappy.

The three questions it actually answers

Here's what those three lines unlock. First: where did this install actually come from? Not a guess. Not a probabilistic fingerprint based on 200 data points. A real answer built on deterministic matching when it's possible, probabilistic matching when it isn't, and the honesty to tell you which is which. It works on iOS 14.5 and later without ATT permission because we built it to work in the world we actually live in, not the world we wish existed.

Second question: is anyone still playing? Day 7 retention. Day 14. Day 30. We track cohorts, not just install volume. A studio we spoke to last year was paying for installs from a channel that looked great on day one, then dropped off a cliff by day 14. Nobody caught it for three months because they were looking at install numbers, not retention numbers. Attribr shows you both, split by source.

Third: which Rippl promoter actually drove this install? If you're running community-driven performance marketing through Rippl, Attribr is the only attribution SDK with a direct bridge between your Rippl account and your install data. You see the promoter name next to the install. You don't have to guess who's sending quality users and who's flooding you with zombies.

Why SDK size matters when you're indie

50 kilobytes. That's Attribr. Your app bundle grows by 50KB. An average indie game on the App Store is 200 to 500 megabytes. Attribution shouldn't be 0.01% of your user's download. It should be invisible.

The other vendors pack their SDKs with features you'll never touch. Session tracking you don't need. Event logging you can do yourself in half the code. Deep-linking infrastructure that costs you megabytes and milliseconds. Attribr asks a single question: what does an indie developer actually need to know on day one? Install source. Retention. Rippl promoters. Everything else is noise.

We made that choice early and stuck to it. No feature creep. No "wouldn't it be nice if we added..." That's how you end up with a 2MB SDK doing the work of a 50KB one.

The free tier actually means something

1,000 installs a month costs you nothing. That's not a trial. That's not a three-week demo. That's a real, permanent free tier for solo developers and hobby projects. We get it. Your first app might never reach 2,000 installs. Why should attribution cost anything?

At Growth (£29 a month), you get 25,000 installs. Pro (£99 a month) covers 100,000. If you hit Business scale, you talk to us. You're not charged based on what some algorithm decided your company is worth. You're charged based on what you actually use. A studio with one game at 80,000 monthly installs pays the same as a solo dev with one app at 80,000 monthly installs. The scale doesn't change the logic.

What happens after day one

Integration is step one. Understanding what the numbers mean is step two. We built a dashboard that shows install sources as a rolling chart. Retention cohorts so you can spot which channels send people who actually play. Funnel views that let you trace users from install through their first session. Pro users get fraud signals and ad-network roll-up so you can see patterns in fake traffic before it costs you real money.

None of this is hidden behind API calls or export workflows. It's there, refreshing in real time, the moment someone installs your app.

Who this is and isn't for

Attribr is built for you if you're an indie iOS or Android developer, or part of a small studio, and you've been avoiding attribution because the enterprise options felt bloated and expensive. We're not a competitor to Adjust or AppsFlyer at scale. If you're a 500-person company with a dedicated analytics team and unlimited budget, they're built for you. We're built for everyone else.

We're also built for developers who use Rippl for promoter marketing and want to know which community members are actually driving installs that matter. That connection doesn't exist anywhere else.