RevenueCat · revenue attributionApp subscriptions, attributed to the posts that caused them.
If you sell app subscriptions, RevenueCat already knows your revenue to the cent, and your social accounts already do the marketing. What is missing is the line between them: which post made someone install and subscribe.
planpo.st draws that line. Connect RevenueCat, post with tracked links to your store page or landing page, and subscription events match back to the posts that started them. For indie app developers this is the difference between posting into the void and posting with a scoreboard.
Connecting RevenueCat takes three steps
1
Create a read API key in RevenueCat
Subscriptions: Read permission is enough. planpo.st uses it to pull revenue metrics, nothing else.
2
Add the webhook
Point a RevenueCat webhook at your planpo.st revenue endpoint, shown in the connect screen. Subscription events start arriving as they happen.
3
Post with tracked links
Links to your App Store page, your site or your paywall become tracked redirects, and events match against the clicks.
Under the hood
The life of a RevenueCat payment, from post to number
Subscription events match to tracked clicks directly or through the 30-day last-click window, same as every source. App funnels are longer than web funnels, someone clicks Tuesday, installs Wednesday, subscribes after the trial, so expect the window matching to do more of the work here, marked medium confidence and shown as such.
- 1
A post publishes with a tracked store link
The link to your App Store page, landing page or paywall runs through a redirect that records the post and platform behind the click before handing off.
- 2
RevenueCat fires a subscription event
Trial starts, conversions and renewals arrive at the webhook you pointed at planpo.st during setup, carrying the subscription's details.
- 3
The matcher bridges the funnel
App funnels stretch over days, so the 30-day window earns its keep here: the event matches to the recorded click that started the journey, labeled by confidence.
- 4
The post shows its subscribers
Attributed subscription revenue lands next to the post, and the demo clip that keeps converting reveals itself over the following weeks.
What counts
Which RevenueCat money shows up, and how
Trial conversions
The moment a trial becomes a paying subscription is the event that attributes: it matches back to the click that started the funnel, however many days earlier.
Renewals and subscription events
Ongoing subscription events arrive from RevenueCat as they happen, and aggregate revenue metrics are read with the Subscriptions: Read permission, in dollars as RevenueCat reports them.
Both stores, one stream
RevenueCat abstracts the App Store and Play Store, so iOS and Android subscriptions attribute identically with no per-store setup.
Who runs this
Three ways this pairing gets used
Indie iOS and Android developers
AppsThe demo-clip-to-subscription path finally gets measured, which settles where scarce posting time should go: the network that produces subscribers.
Subscription apps testing content angles
AppsFeature demos versus lifestyle content versus founder story: each angle's tracked links accumulate their own conversions, and the calendar tilts toward what converts.
App marketing agencies
AgencyClient reports move from installs-adjacent vanity to subscription revenue per post, read from the client's own RevenueCat.
The alternative
Compared to the UTM spreadsheet you were about to build
Manual attribution for apps usually means store-listing analytics plus RevenueCat's charts plus a spreadsheet guessing which spike belonged to which post. The store's own attribution is notoriously coarse, and none of it connects to individual posts.
Matching store-page clicks to later subscription events across a multi-day funnel is exactly the work the tracked redirect and the 30-day window automate, with confidence labels standing in for the false certainty a spreadsheet would fake.
Where manual still wins
If you post twice a month and check numbers quarterly, a spreadsheet is genuinely fine. Automated attribution earns its keep at the posting volume where the spreadsheet quietly stops being maintained.
What it looks like in practice
You post a demo clip of your app on X and Threads with a tracked link to the store page. Over the week, clicks accumulate and a few trials convert.
Converted subscriptions attribute to the posts that drove the clicks, and the revenue view shows the demo clip earned its slot. Your agent can pull the same numbers over MCP and draft next week accordingly.
Questions people ask
- Does this replace RevenueCat's own analytics?
- No, it adds the social dimension RevenueCat does not have. RevenueCat tells you revenue by product and platform; planpo.st tells you which social posts started those subscriptions.
- App store pages break link tracking, don't they?
- The tracked redirect records the click before handing off to the store, so the social side of the trail survives. The install-to-subscription step happens inside RevenueCat's events, which is why the webhook matters.
- iOS and Android both?
- Yes. RevenueCat abstracts the stores, and planpo.st consumes RevenueCat events, so both platforms' subscriptions attribute the same way.
- How accurate is attribution for app funnels?
- Honest answer: app funnels lean on the 30-day window more than web funnels, because the click and the payment are further apart. Matches are labeled by confidence so you can see which kind of evidence each number rests on.
- What does it cost?
- Revenue attribution including RevenueCat is a Pro feature, $39.99 a month, 7-day free trial.
Keep going
The rest of the loop