WinWinKit vs Dub Partners
A side-by-side look at which platform fits your mobile app.
The Key Difference
Dub is a link attribution platform, and Dub Partners is the affiliate program built on top of it. That lineage shows in the best way: short links, click analytics, first-party cookies that ad blockers don’t strip, and conversion events posted from your own server. Partners get real-time analytics, you pay hundreds of them in one click, and the Stripe integration is native rather than a bolted-on sync.
The model starts with a link and ends with a conversion event your backend sends. Both ends are harder on mobile. A link click happens in the browser, the install happens in the App Store, and the dub_id doesn’t cross that boundary on its own. And because Apple and Google record the subscription, there’s no Stripe charge to convert - you’d be writing the code that carries the referral into the app and reports the purchase back yourself.
WinWinKit does that part for you. The user claims a code inside the app, which fixes attribution without a cookie or an install referrer, and subscription revenue is read from App Store Connect and Google Play directly, or through RevenueCat.
WinWinKit
| Dub Partners | |
|---|---|---|
| Built for | Mobile apps - iOS, Android, desktop - including web checkout when the app onboards on the web | Web products tracking referrals through links and server-side conversion events |
| Attribution | Code-based, entered in-app; deterministic and privacy-safe | Short links with a dub_id parameter stored as a first-party cookie, converted by events from your server |
| Growth channels | Affiliates, referrals, and promo codes in one dashboard | Partner programs |
| Reward types | Two-sided - cash commissions for affiliates, in-app and app store rewards for users. In a referral both sides can be rewarded - the referrer and the friend | Cash commissions to the partner - percentage or fixed, one-time or recurring |
| Integrations | RevenueCat, Stripe, App Store Connect, Google Play | Stripe and Shopify |
| SDKs | Swift, Kotlin, Dart, and TypeScript, plus a REST API | TypeScript, Python, Go, PHP, and Ruby, plus an analytics script and a REST API |
| Payouts | Stripe Connect, PayPal, and Wise, in one click | Stripe Connect, PayPal and Stablecoin |
| Pricing | Starter - $30/mo Essential - $75/mo Scale - $150/mo | Business - $90/mo Advanced - $300/mo Enterprise - custom |
| Metered on | Monthly attributed revenue, from $3K on Starter | Links, tracked events, partners, and partner payout volume - $2.5K/mo of payouts on Business |
| Beyond the basics | Real-time analytics, affiliate groups, a resource hub of assets and FAQs, public application forms, plus content tracking and community channels | A full link management suite - short links, click analytics, and partner group reporting |
| Best for | Subscription apps that monetize through the app stores | Web products that already run their growth on links |
When to Choose WinWinKit
- Your users subscribe through the app stores. Apple and Google record the purchase, so there’s no Stripe charge to convert and no server-side event unless you write it. WinWinKit reads the store transaction itself.
- You want commissions off real revenue. WinWinKit reads subscription revenue directly from App Store Connect and Google Play, or through RevenueCat if that’s your setup - either way commissions follow what you actually earned, not an estimated conversion.
- You don’t want to build the mobile half. Carrying a referral across the install boundary, into the app, and back out as a purchase event is the part you’d be writing yourself. In WinWinKit it’s the product.
- You want mobile-native rewards. A special paywall via a RevenueCat Offering, a free month via an Entitlement, or a discounted subscription via an App Store Offer Code or Google Play Promo Code - rewards that only exist in the app ecosystem.
- You need more than affiliates. Affiliate campaigns, referral programs, and promo code campaigns share one attribution system and one revenue view.
- You build in Swift, Kotlin, Flutter, or React Native. WinWinKit ships an SDK for each; Dub’s SDKs are server-side.
When to Choose Dub Partners
- Your product lives in the browser. Dub assumes a web funnel: a short link, a first-party cookie, and a conversion your server or Stripe reports. If your customers buy on your site, that model works and WinWinKit’s in-app codes buy you nothing.
- You want link management as well as a partner program. Short links, click analytics, and campaign reporting are Dub’s core product, not an add-on. WinWinKit has landing pages, but nothing of that depth.
- You sell on Shopify. Dub integrates with it natively; WinWinKit doesn’t.