RevenueCat-reviewed OAuth access
RevenueCat manually reviewed and approved Lily's OAuth client application. You sign in and grant explicit read scopes on RevenueCat's authorization flow; Lily then selects the accessible project and joins its revenue metrics with Apple Ads acquisition data.
Authorization
Reviewed and approved by RevenueCat
Scopes
Projects, apps, charts: read
Credential
Encrypted OAuth tokens
This approval authorizes Lily to offer RevenueCat's OAuth flow. The authorization request uses read scopes for projects, apps, and charts, so you grant access on RevenueCat without pasting a secret API key into Lily.
Lily exchanges the authorization code using PKCE, encrypts the resulting tokens, lists the accessible projects, and records the selected project and last successful test.
Compare spend with purchases, subscriptions, paying users, and revenue by campaign, keyword, and country. Cohort windows make the payback period explicit instead of treating every install as equal.
How it works
Paste the app link so Lily can scope every source to the same product.
Review the requested read scopes and approve the registered Lily OAuth client.
Join spend and campaign dimensions to the selected revenue source.
Questions
RevenueCat manually reviewed and approved Lily's OAuth client application. This authorizes Lily to offer direct RevenueCat OAuth access to users who grant permission. The approval validates the integration path; it does not by itself designate Lily as a RevenueCat-endorsed product or formal commercial partner.
No. RevenueCat supplies customer and revenue outcomes. Apple Ads supplies campaign cost and acquisition dimensions. Lily joins the available signals for analysis.
Time zones, attribution windows, refunds, proceeds versus gross revenue, delayed events, and identity matching can all create differences. Use a documented comparison window.
Yes. Lily can analyze Apple Ads delivery and cost metrics first. Add RevenueCat when you want subscription and paying-user context.