Optional revenue matching
RevenueCat is optional. It adds subscription context to first-party customer votes so you can prioritise requests using revenue as well as vote counts. It does not identify App Store reviewers or weight imported reviews. See App Store reviews.
Use the same stable app-user ID in your app's RevenueCat integration and Upweight integration. SDK matching uses that identity, not the customer's email address. An unmatched identity is not proof of a paying subscriber, and the app-supplied identity is not independently verified by Upweight.
When identity linkage is unavailable, Upweight can fall back to matching a verified public-board customer's email within the same workspace, provided that customer is not already linked to a RevenueCat customer. This lets public-board votes receive revenue context. Unverified SDK email is not used for this fallback.
Connect RevenueCat
In the RevenueCat setup screen, enter a v2 secret API key, not a public SDK key or a v1 key. Give it read-only access to customers, products, subscriptions, purchases, and transactions. Map each app to the RevenueCat project ID containing its customers, not an app ID; at least one project mapping is required.
Choose Test connection, then Save Changes, then Sync now. The connection test checks customers only; success does not verify all permissions needed for a full sync. Never ship the secret key in your app or put it in public feedback.
Configure the webhook
After saving, copy the private webhook URL shown in Upweight into RevenueCat's Integrations → Webhooks → Add new configuration. This is an illustrative URL only: https://upweight.dev/api/webhooks/revenuecat/TOKEN. Use the actual URL from your setup screen, not the placeholder.
Set the Authorization header to Bearer, followed by one space and the same v2 secret API key saved in Upweight. Never put the key in the URL. Keep the URL and authorisation value private.
Sync and backfill
Sync now queues a full sync. Queued and Running are not completion messages: wait for the updated customer count and timestamp, or inspect a failed state. Webhooks keep subscription changes current, and a nightly sync refreshes the full data set. Failed connections can leave rankings stale.
Backfill recalculates classifications and vote aggregates from data already stored in Upweight; it is not a fresh fetch from RevenueCat and cannot invent missing purchase metadata or unknown prices. A queued sync is not a completed backfill. If classifications remain unexpected, check the app-to-project mapping and stable app-user ID, then the completed sync state.
Read revenue classifications
The voter labels are Paying, Free, Free (trial), and Cancelled. Trials count as free. Paid access can remain active with auto-renew turned off, during grace, or during billing retry; a cancellation event alone does not end access. Cancelled describes previously paid customers whose access has ended, not merely customers who turned off renewal.
A paid, owned lifetime purchase counts as Paying with zero monthly revenue only when product metadata proves it is a non-consumable purchase. Missing metadata must not be treated as proof of lifetime access. Unknown recurring prices stay unknown rather than being guessed.
The UI labels monthly revenue; API monetary values use integer USD cents. Recurring prices are normalised to monthly amounts using supported billing periods. Estimates are not guaranteed future renewal prices or lifetime spend. Cancelled customers have zero current monthly revenue, while a last known monthly amount can be retained for cancellation analysis.
Privacy
Revenue and classifications are never shown publicly on the board or in SDK responses. They are available to authorised owners and admins, including through authorised MCP access. Do not copy customer revenue into public requests or comments. Learn the boundaries in Security and privacy and the meaning of votes in Core concepts.
For in-app feedback, see the SDK overview, Swift SDK guide, and HTTP API reference.