Use a reporting token—not an OAuth login.
The current Lily connection expects an AppsFlyer API V2 token that can list the relevant app and read Raw Data Pull reports. This is intentionally described differently from RevenueCat's OAuth flow.
AppsFlyer reporting API
AppsFlyer uses a different connection path from RevenueCat: you provide an API V2 token with access to the app list and Raw Data Pull reports for installs and in-app events. Lily validates the app, encrypts the token, and uses it only for reporting.
Connection
AppsFlyer API V2 token
Access
Raw Data Pull reports
Use
Read-only attribution
The current Lily connection expects an AppsFlyer API V2 token that can list the relevant app and read Raw Data Pull reports. This is intentionally described differently from RevenueCat's OAuth flow.
Lily encrypts the API token, tests whether it can reach the selected AppsFlyer app, and stores the last-tested app, platform, currency, and time zone for the reporting connection.
Lily syncs AppsFlyer reporting snapshots and joins the available acquisition dimensions with Apple Ads spend. Attribution windows, privacy thresholds, event configuration, and time zones remain visible caveats.
How it works
Add the App Store app that connects the acquisition and outcome data.
Use a token with access to the app list and the required installs and in-app event reports.
Validate date range and attribution assumptions before acting on ROAS.
Questions
Not in the current Lily flow. AppsFlyer connects with an API V2 token, which Lily encrypts and uses only to read reporting data for the selected app.
No. AppsFlyer is read as an outcome source for the selected app. Apple Ads campaign operations remain separately scoped and controlled.
Use events that represent the business outcome you optimize for, such as trial, purchase, subscription, or revenue. Confirm event quality before automating decisions.
Yes, when the connected sources expose compatible country and campaign dimensions for the selected reporting window.