Payments
Know which posts bring RevenueCat customers
In-app purchases and renewals of your mobile app, sent by RevenueCat as they happen.
Available to connect- Access
- Read-only
- Connection
- Secret API key
- History
- Live, from the day you connect
Which post brought paying users to your mobile app?
For iOS and Android makers who sell subscriptions and in-app purchases through RevenueCat. App stores rarely say which post made someone install and pay; upTake ties purchases and renewals to the visit to your site or landing page that came before.
For example: you post a short demo on X and a launch on Product Hunt, each pointing to your landing page with its own tag. RevenueCat sends the purchases as they happen, and the report shows which launch brought paying users rather than downloads.
From a post to a RevenueCat payment
- 1. The postReddit · r/SideProjectShared with indiepdf.com/?ut=reddit
- 2. Visits and signups1,204 visits · 88 signupsRecorded by the upTake script
- 3. Payments in RevenueCat9 customers · $431Matched to the visit before the payment
What upTake reads from RevenueCat
upTake reads your paid orders and subscription payments from RevenueCat: the amount, the currency, the date, and the identifiers of the payment and of the customer. RevenueCat sends each payment to upTake as it happens, from the moment you connect: there is no history to import, and a payment sent twice is counted once. Each payment is then matched to the visit that led to it: exactly when your checkout passes upTake's visitor identifier, otherwise by time, and a payment matched by time is always shown as estimated.
How to connect RevenueCat
- You need an upTake project first; creating one takes 5 minutes.
- Click Connect on the Integrations page; a small window asks for what RevenueCat needs.
- Secret API key: In RevenueCat: your project → API keys → create a secret key (v2) with read access.
- Webhook authorization header: Any long random value: the same one you set as “Authorization header value” in step 1.
- Count sandbox purchases (optional): Type yes to also count SANDBOX test purchases.
- upTake checks it with RevenueCat before saving it.
- To receive payments as they happen, in RevenueCat: your project → Integrations → Webhooks → Add. Paste this address and set “Authorization header value” to a long random value of your choice.
On the RevenueCat side, see RevenueCat's documentation on webhooks.
What you see afterwards
Your revenue appears on the overview, split by the source that brought each customer: the post, the link or the release behind it. The weekly report tells you which actions paid and which only brought attention. Revenue is always shown apart from visits, and anything upTake had to estimate is marked as estimated.
Privacy and access
- upTake never reads or stores card numbers. It never moves money, issues a refund or changes anything in your RevenueCat account.
- Your visitors' IP addresses are never stored.
- Keys and accesses are stored encrypted and never sent back to your browser. Your data is hosted in the European Union.
- Disconnect RevenueCat at any time: upTake stops at once, and what was imported stays until you delete it.
Questions about RevenueCat
Does upTake need write access to my RevenueCat account?
No. upTake only reads payments. It never moves money, issues a refund or changes anything in your RevenueCat account.
How far back does upTake import RevenueCat payments?
RevenueCat sends each payment as it happens, from the day you connect. There is no history to import.
What happens when a payment cannot be tied to a visit?
It still counts in your revenue, shown as not traced to a source. A payment matched by time instead of by identifier is always marked as estimated.
Are test purchases counted?
No. Purchases from the SANDBOX environment are ignored, unless you choose to count them in the connection window, which is useful while testing.
Use RevenueCat in your own project
Free plan · No card · 5-minute setup
Connect RevenueCatSee Home in the demo