For subscription apps on RevenueCat
RevenueCat creator attribution: which creators brought subscribers?
RevenueCat shows every trial and subscription. It can't tell you which creator's TikTok or Reel sent each one. WhichPost reads your RevenueCat data read-only and credits each creator with the paying users their posts brought, each with a likely range.
The short answer
Create a RevenueCat secret API key, version 2, with read-only access to customer information, and paste it with your project ID and links to your creator posts. WhichPost lines up each post's hourly views with your installs, trials and purchases, and gives every creator a call: rebook, test again or pause.
The problem
Subscribers arrive. Their source doesn't.
Subscription apps paying creators run into the same gaps again and again.
-
The trail breaks at the App Store
A viewer sees a post, opens the App Store and searches for your app. No link was tapped, so the install looks organic and the creator gets no credit.
-
Offer codes don't scale
Apple limits how many offer codes can run at once, and most viewers never redeem one. A code per creator gets hard to run across dozens of creators.
-
Subscriptions aren't attribution
RevenueCat records who subscribed and when. By its own documentation it isn't an attribution tool: it forwards events to the attribution tools you connect, which rely on tracked clicks and ads.
How WhichPost answers it
Installs, trials and payments, credited post by post
No SDK and no app update. Your RevenueCat data and your posts' public views are all it needs.
Connect RevenueCat read-only
Create a secret API key, version 2, with Customer information set to read only, and paste it with your project ID. Revoke it in RevenueCat at any time.
Add your creator posts
Paste links to the TikTok, Instagram or YouTube Shorts posts you paid for. WhichPost checks their public views every hour.
Get a call on every creator
Each creator's paying users and cost per paying user, each with its range, so you rebook the creators whose viewers subscribe.
What you need
Two things to connect. Nothing to install.
No SDK, no tracking links and no changes to your app, checkout or captions.
Stripe or RevenueCat
A restricted, read-only Stripe key for a web product, or a read-only RevenueCat key for a mobile app. Connect both if you sell in both places.
The posts you paid for
Links to the TikTok, Instagram or YouTube Shorts posts, from a clipping platform, an agency's sheet or direct creator deals.
Enough daily volume
About 20 new sign-ups or installs a day or more, and at least a week of history before the campaign started. A free data check tells you whether your data is enough before you pay.
Questions
Questions, answered.
What does WhichPost read from RevenueCat?
Customers, subscriptions, purchases and their transactions: when someone first opened the app, started a trial, paid, renewed or got a refund, and their country. The key only reads. It can't change your products, prices or customers.
Are creators ranked on installs or on paying users?
On paying users. WhichPost reads installs, trials, first payments, renewals and refunds, and ranks creators by the paying users their posts brought, so a creator whose trials rarely convert doesn't look better than one whose trials do.
Do I need an attribution SDK?
No. Nothing changes in your app. If you already run an attribution SDK, keep it for paid ads. WhichPost covers the creator posts that reach people without a tracked click.
We also sell on the web through Stripe. Can we connect both?
Yes. Connect RevenueCat for the app and Stripe for web checkouts, and the report counts paying users from both.
More guides
Other questions teams ask
See which of your creators paid
Connect in about two minutes, or look through a sample report first. Every result comes with its range.