The Rippl bridge: seeing which promoter drove each install

The gap that shouldn't exist

If you're a solo developer or run a team under ten people, you live in a specific world. You can't afford Branch or AppsFlyer. You certainly can't pay £500 a month for Adjust. But you also can't run blind. You need to know: did that install come from your Reddit post, your TikTok creator friend, or a paid campaign?

Rippl solved half that problem. It's a performance-marketing platform where community members - micro influencers, streamers, dedicated fans - can promote your app and earn money per install. No gatekeeping. No middleman rates. But the moment an install landed in your app, the connection went dark. Your attribution SDK (if you had one) would tell you the traffic source was organic or direct. Rippl would tell you how many installs they sent. Neither would say: this specific install came from this specific promoter.

That gap bothered us because it meant indie developers were flying half-blind. They had growth, but no granularity. They couldn't reward the promoters who actually converted. They couldn't double down on what worked. They were guessing.

Why we built it into Attribr

We started building Attribr for indie developers who needed install attribution without enterprise pricing. The SDK is 50KB, integrates in three lines of Swift or Kotlin, and runs with zero third-party dependencies. Launch overhead under 50ms. It answers the three questions that matter: where did each install come from, is that user still active at day 7, 14, and 30, and (now) which Rippl promoter drove the install.

The Rippl bridge works because Rippl gives us a promoter identifier in the click. We match that click to the install using the same logic that powers our core attribution: deterministic matching when the signal is strong, probabilistic matching when it isn't. On iOS 14.5 and above, we do this without needing ATT permission. The result is a direct line from promoter to install in your Attribr dashboard.

Why does this matter? Because if you're paying for performance marketing through Rippl, you need to know what you're paying for. Not in aggregate. Install by install. You need to see which promoter's audience actually converts, which ones drive retention, which ones are noise. That's not a luxury. That's basic operating data.

The bridge in practice

Let's say you launch a puzzle game on iOS. You recruit five promoters through Rippl. Each one runs a different TikTok angle: speedrun clips, satisfying level wins, frustrating failures. You set a 50p CPI rate and let them loose.

In your Attribr dashboard, you see the cohort breakdown. Promoter A sent 200 installs this month. Of those, 140 are still active on day 7. Promoter B sent 180 installs, but only 80 are active on day 7. Promoter C's installs are cheap, but nobody comes back. Promoter D's users stick around and spend time in-app.

Now you have actual business intelligence. You can message Promoter D and ask if they want to run a second campaign. You can ask Promoter C what their audience demographic is, because the retention gap suggests a mismatch. You can adjust your CPI rate for each promoter based on their actual impact, not their traffic volume.

The bridge isn't complicated. Attribr receives the Rippl promoter ID with each click, attributes the install deterministically or probabilistically, and labels it in your dashboard. You see it in your retention cohorts, your funnel charts, your install breakdown. No separate system. No manual CSV matching. One platform. One source of truth.

Why this only works at indie scale

You won't find the Rippl bridge in Adjust or AppsFlyer. Not because they can't build it, but because their customers don't need it. Enterprise clients run campaigns through programmatic networks, direct deals with ad partners, and internal teams. A direct line to a community promoter platform doesn't fit their playbook.

But indie developers live in a different ecosystem. Rippl is purpose-built for that world: low friction, community-driven, transparent payouts. And once you've sent your first 100 or 1,000 installs through Rippl, you want to see what happened. Not next week. Not in a custom report. In your dashboard, right now.

That's why we built it into Attribr. Not as a feature. As a bridge. A deliberate connection between where indie developers get their growth and where they measure it.

The numbers that surprised us

When we launched the Rippl bridge, we expected indie developers to use it. What we didn't expect was the retention variance.

Early users told us their Rippl promoters showed day-7 retention rates between 35 and 65 percent. Wide spread. Some promoters' audiences were genuinely better matched to the game. Others had brought in volume at the expense of quality. But here's the thing: without the bridge, they would never have known. They would have written off Rippl as either working or not working, in aggregate, with no way to optimize.

One developer told us the bridge helped them cut their CPI by 30 percent by focusing exclusively on the two promoters whose users actually engaged with the game. That wasn't a bigger campaign. That was precision. Knowing which promoter's audience fit, and doubling down there instead of spreading budget across five mediocre channels.