Integrations · Purchase data
RevenueCat + Proofline
Most subscription apps already send their purchase events to RevenueCat. Proofline listens to the same events through a RevenueCat webhook, so you don’t point Apple or Google anywhere new.
Setup
Four steps, about ten minutes.
- 01
Add your app in Proofline
Choose RevenueCat as the purchase source. Proofline shows a webhook URL for your app and generates an authorization value.
- 02
Create the webhook in RevenueCat
In your RevenueCat project, add a webhook integration. Paste the URL and set the Authorization header to the value from Proofline. Proofline checks it in constant time and rejects anything else.
https://app.proofline.link/api/ingest/revenuecat/<appId>
- 03
Install the SDK and sync attributes
The SDK writes the creator into RevenueCat subscriber attributes, so every later webhook carries it and the creator shows up in RevenueCat Charts.
proofline_end_user_id · proofline_creator_id · proofline_creator_handle proofline_program_id · proofline_tier · proofline_code
- 04
Send a test event
Use RevenueCat’s test webhook, then make a sandbox purchase. A sandbox receipt appears in Proofline; sandbox purchases never earn commission.
What syncs
What Proofline reads.
- Initial purchases, trials, renewals, product changes, cancellations and refunds
- The offer code used for a purchase (RevenueCat’s offer_code field), recorded as a store-verified signal
- Store commission and tax percentages, so commissions are paid on net proceeds
- Environment (production or sandbox) and family-sharing ownership
- Proofline subscriber attributes written by the SDK
Limits
- Events from before you connect are not backfilled automatically. Nightly reconciliation checks RevenueCat for users with signals in the last 90 days.
- Proofline acknowledges each webhook within two seconds and processes it in a background job; duplicates are ignored by event ID.
- Sandbox and family-shared purchases are recorded but excluded from commission by default.