Setting up AppsFlyer takes five stages: add the app to your AppsFlyer account, integrate the SDK in the Android and iOS builds, define your in-app events, test the whole flow with a real device, and connect the partners who will run traffic. Do all five before spending anything — fixing tracking after launch means paying for traffic you cannot measure.
Stage 1: Add the app
- Sign in to AppsFlyer (or create an account).
- Choose Add app and select the platform.
- Android: enter the package name (for example
com.company.app). For apps not yet in Google Play, choose the option for apps pending approval or out-of-store apps. - iOS: enter the App Store ID (the number after
idin the App Store URL). Pre-release apps can be added before they are public. - Set the app's time zone and currency — they affect every report, so choose carefully.
- Copy the dev key from the app's integration settings. Treat it like a password and keep it out of public code repositories.
Stage 2: Integrate the SDK
Your developers integrate the AppsFlyer SDK following the official developer docs at dev.appsflyer.com:
- Android: add the SDK dependency, add the Google Play Install Referrer library, set required permissions, then initialise the SDK with your dev key in the
Applicationclass and callstart. - iOS: add the SDK through Swift Package Manager or CocoaPods, initialise it with the dev key and the Apple app ID, and start it when the app becomes active.
- iOS privacy: if you request App Tracking Transparency consent, configure the SDK to wait for the user's choice before sending the first launch (AppsFlyer documents a timeout setting for this). Add the SKAdNetwork and AdAttributionKit settings your partners need.
- Cross-platform apps (React Native, Flutter, Unity): use AppsFlyer's official plugins.
- Consent: in regions such as the EEA and UK, pass users' consent choices to the SDK as required by AppsFlyer and your legal setup.
Stage 3: Define your in-app events
Agree an event plan before developers code it:
| Event | Suggested AppsFlyer name | Key parameters |
|---|---|---|
| Registration | af_complete_registration | af_registration_method |
| Login | af_login | — |
| Tutorial complete | af_tutorial_completion | — |
| Purchase / deposit | af_purchase | af_revenue, af_currency, af_content_id |
| Subscription start | af_subscribe | af_revenue, af_currency |
Use AppsFlyer's predefined event names where they fit — partners understand them without mapping. Send revenue only on real money events, and never send test purchases in production. The full detail is in how to track purchase events in AppsFlyer.
Stage 4: Test before launch
- Register a test device in AppsFlyer (by advertising ID or other supported ID).
- Use the dashboard's SDK integration test to check that installs and events arrive.
- Test a non-organic install: click a test attribution link on the device, then install and open the app — it should appear attributed to that link's media source.
- Trigger every in-app event and confirm names, values and currency in the dashboard or raw data.
- Test on both Android and iOS, and on a fresh install each time (uninstall, clear data, reinstall).
Stage 5: Connect your partners
- Go to the partner marketplace / integrations section and search for each ad network or DSP.
- Activate the integration, enter the partner's IDs if required, and choose which in-app events to send as postbacks — map your event names to the partner's events.
- Set attribution windows per partner if they differ from your defaults, and match what is in your contract.
- Copy the partner's attribution link (or let the partner pull it) — see AppsFlyer links and OneLink.
- For self-reporting networks (Google, Meta, TikTok and others), connect them through their dedicated integrations.
- If an agency runs campaigns for you, add it and grant permissions — see AppsFlyer for agencies and advertisers.
Before you launch: a final checklist
- Dev key secured, SDK initialised on both platforms.
- Test install attributed correctly from a test link.
- All money events tested with correct revenue and currency.
- Partner integrations active with the right events mapped.
- Attribution windows match your partner agreements.
- Fraud protection reviewed (Protect360 if on your plan).
- Cost data and ad revenue integrations planned if you want ROI and ROAS.
FAQ
How long does AppsFlyer setup take?
The dashboard setup takes an hour or two. SDK integration and testing usually take developers one to several days, depending on the app and the number of events.
Where do I find my AppsFlyer dev key?
In the app's settings in the AppsFlyer dashboard, under the SDK integration section. Only account users with the right permissions can see it.
Can I set up AppsFlyer before my app is published?
Yes. AppsFlyer supports pending and pre-release apps so you can test before the store listing is live.
How do I test AppsFlyer attribution?
Register a test device, click a test attribution link on it, install the app fresh and open it. The install should appear attributed to that link's media source in the dashboard.
Sources
Published 25 October 2026 by the ClickSpero Editorial Team. Platform features, fees and policies change often — check the provider’s current terms before you rely on a number. Third-party names are trademarks of their owners; no endorsement is implied.