
Table of Contents
ToggleIf you run a subscription app, you have probably asked whether RevenueCat or Amplitude should be your source of truth for revenue. The short answer is that they do different jobs, and most subscription apps get the best results from using both with clear rules about who owns what.
This RevenueCat vs Amplitude guide explains what each tool is built for, where they overlap, how to connect them without breaking your numbers, and how to add attribution on top. The setup details below were checked against RevenueCat and Amplitude documentation in October 2026.
RevenueCat sits between your app and the stores. You integrate one SDK, and RevenueCat handles purchase processing, entitlements and subscription status for iOS and Android. It also records subscription lifecycle events such as trial starts, renewals, cancellations and billing issues, and it can send those events to other tools.
That matters because subscription state is hard to rebuild yourself. Trials, grace periods, billing retries, upgrades and refunds all change what “an active subscriber” means. RevenueCat keeps that logic on its servers so your client code does not have to guess.
According to RevenueCat’s account management documentation, RevenueCat stays free until you reach $2.5k in Monthly Tracked Revenue (MTR). Above that, Pro plan customers pay 1% of MTR, calculated before store commission and taxes. Check the current terms before you budget, because pricing pages change.
Amplitude tracks events your app sends and turns them into funnels, retention charts, cohorts and user journeys. It is the place to ask behavioral questions: which onboarding path leads to more trial starts, where users leave before the paywall, and which features your longest-retained subscribers use.
Amplitude’s pricing page lists a free plan with no time limit and a volume limit of 2M events per month, and a Plus plan that starts at $0 for the first 2M events. Older articles quote a 10M event free tier, which no longer matches the current page. The free plan includes A/B/n Web Experimentation, while Feature Experimentation A/B/n testing is listed on the Growth and Enterprise plans.
| Question | RevenueCat | Amplitude |
|---|---|---|
| Main job | Subscription and purchase management | Product and behavior analytics |
| Manages entitlements across iOS and Android | Yes | No |
| Subscription lifecycle events | Built in | Only if you send them yourself or import them from RevenueCat |
| Funnels, retention and cohorts | Not its focus | Core feature |
| Tests | Experiments on offerings, such as price and trial length (Pro and Enterprise plans) | Experimentation features, with plan limits |
| Free tier | Free until $2.5k MTR | Free plan with 2M events per month |
RevenueCat’s Experiments documentation says tests are built on Offerings, so you can test more than price, including trial length, subscription length and product grouping. Neither tool replaces the other. One records the subscription, the other explains behavior around it.
RevenueCat can send subscription events to Amplitude, so revenue and behavior live in one place. The steps below follow RevenueCat’s Amplitude integration guide.
Configure the Amplitude SDK with the same App User ID that RevenueCat uses, either at initialization or with setUserId. This is what lets both tools describe one person. On RevenueCat’s side, identifying customers works through logIn. Note how it behaves: if the current ID is anonymous and the new ID is unused, the two are merged and purchases carry over. If the ID you pass already has an anonymous alias, or the current ID is not anonymous, the user is switched and no purchases are transferred.
// iOS: set the same ID in both SDKs after login
let userId = "user_12345"
Purchases.shared.logIn(userId) { customerInfo, created, error in
// handle result
}
amplitude.setUserId(userId: userId)
// Android: set the same ID in both SDKs after login
val userId = "user_12345"
Purchases.sharedInstance.logInWith(userId, ::showError) { customerInfo, created ->
// handle result
}
amplitude.setUserId(userId)The Swift snippet uses the Amplitude object from Amplitude’s Swift SDK, and the Android one uses the Android-Kotlin SDK. Amplitude’s documentation also points to a Unified SDK if you want Analytics, Experiment and Session Replay together, so pick one path before you start. If your RevenueCat ID and Amplitude ID are different by design, RevenueCat supports two optional customer attributes, $amplitudeDeviceId and $amplitudeUserId, which tell it which Amplitude identity to use.
In the RevenueCat dashboard, open your project, go to Integrations and choose Amplitude. Add your Amplitude API key, confirm the event names, choose how revenue is reported, and if your Amplitude project is on EU servers, set the region to EU.
By default RevenueCat sends events with names like these, and you can rename them in the integration settings:
rc_initial_purchase_eventrc_trial_started_eventrc_trial_converted_eventrc_trial_cancelled_eventrc_renewal_eventrc_cancellation_eventrc_billing_issue_eventrc_expiration_eventrc_product_change_eventThere are more, including uncancellation, non-subscription purchase and subscription paused events. The names are easy to get wrong from memory, and older posts show shortened versions that do not match the current defaults, so copy them from the integration screen.
You decide whether RevenueCat reports gross revenue, before store commission, or a net figure after commission and estimated taxes. Pick one and write it down, because mixing the two across tools is a common reason finance and marketing numbers disagree. RevenueCat also states that revenue in this integration is always reported in USD, with the original currency kept in a currency field.
Run a sandbox purchase, then look for the event names above in Amplitude. Check that the user ID matches the one your app sets, and that revenue and currency look right. Two things can look like bugs but are not: without Platform Server Notifications, RevenueCat says expiration events can be delayed by about an hour, and some events are store specific, for example the paused event applies only to Google Play.
Once events flow, you can build the views that justify the integration. A basic path for a trial-based app is: onboarding completed, paywall viewed, trial started, trial converted. Use your own app events for the first two steps and the RevenueCat events for the last two. For churn, compare behavior in the days before a cancellation event with behavior from users who renewed. If a funnel shows a gap between paywall views and trial starts, that is a product question for Amplitude, while a gap between trial starts and conversions is where RevenueCat’s subscription data and your trial design matter.
If you buy installs, you also need to know which campaign produced each paying subscriber. A mobile measurement partner does that part, and the three tools split the work:
RevenueCat documents an AppsFlyer integration. Its main requirement is the $appsflyerId attribute, which you set in the app. RevenueCat also recommends device identifiers such as the IDFA and IDFV on iOS and the Google Advertising ID on Android, and its page warns that some events may not be delivered if the AppsFlyer ID is missing. It also says to remove any client-side purchase tracking, or revenue may be double counted in AppsFlyer. For the AppsFlyer side, see the AppsFlyer setup guide, and for tool trade-offs, AppsFlyer vs Adjust.
rc_trial_cancelled_event so you can study why users leave before paying.The honest answer to the RevenueCat vs Amplitude question depends on your stage. For a small subscription app with no paid acquisition, start with RevenueCat alone. It gives you subscription state and revenue metrics with little code, and you can add analytics later. Add Amplitude when you have enough traffic to ask behavioral questions. Add an MMP when you start paying for installs. If you outgrow free limits, compare costs using the current pricing pages, since both vendors change them.
They do different jobs. RevenueCat manages purchases and subscription status and reports subscription revenue. Amplitude analyzes user behavior. For subscription revenue, RevenueCat is the better source, and most subscription apps benefit from using both.
You can log purchase events in Amplitude, but you would still need your own way to validate purchases, manage entitlements and handle subscription states such as trials and billing retries. RevenueCat handles that work, and it can send its events to Amplitude.
Use the same App User ID in both SDKs, then open Integrations in the RevenueCat dashboard, choose Amplitude, add your Amplitude API key, confirm the event names and choose gross or net revenue reporting. Test with a sandbox purchase and look for the events in Amplitude.
Yes. RevenueCat documents an AppsFlyer integration. You set the AppsFlyer ID as a customer attribute, enable the integration in the dashboard and choose event names. RevenueCat recommends removing client-side purchase tracking to avoid double counted revenue.
RevenueCat’s documentation says it stays free until you reach $2.5k in Monthly Tracked Revenue. Above that, Pro plan customers pay 1% of MTR, calculated before store commission and taxes. Check the current pricing page before you plan a budget.
Amplitude lists a free plan with no time limit and a limit of 2M events per month. Paid plans are priced by events and are listed as custom for the Growth and Enterprise tiers, so check the pricing page for current details.
The usual causes are different user IDs, a mix of gross and net revenue settings, revenue being counted in two places, and Amplitude reporting revenue in USD after conversion. Pick one source of truth for revenue and run a sandbox test after any change.
If you want help connecting RevenueCat, Amplitude and attribution without double counting, send your platform and a short description to contact@alfahadhridoy.com and I will reply by email.