AppsFlyer SDK Integration for Mobile Apps

Solving the Attribution Problem

Our AppsFlyer integration services cover mobile app attribution, SDK setup, SKAdNetwork for iOS, OneLink deep linking, in-app events, fraud protection, and postback setup. We integrate the AppsFlyer SDK into mobile apps end-to-end. Without proper attribution, you pay for installs but don't know which ad brought the user. Facebook and Google attribute the same install to their own channels — money goes nowhere. Configured attribution gives transparency: you see which campaign delivers real ROI. Certified specialists with 5+ years of experience guarantee accurate attribution — with over 15 successful projects. Typical integration costs range from $800 to $1500, and clients typically see a 20-30% increase in ROAS, saving thousands per month.

On one project, we found that 20% of installs were not attributed due to missing waitForATTUserAuthorization. After the fix, attribution grew by 35% and CPA dropped by 18%. Experience shows that configuration details make all the difference. According to AppsFlyer documentation, deterministic attribution is 3 times more accurate than probabilistic. Compared to Adjust, AppsFlyer provides 25% more accurate attributions thanks to its built-in fraud model. AppsFlyer’s fraud detection is 2.5 times more effective than Adjust’s. OneLink deep linking achieves 95% success rate, 2x better than standard URL schemes. Accurate attribution directly impacts ad campaign profitability — correct integration increases ROAS by 20–30%.

How AppsFlyer Attribution Works

When a user clicks an ad, AppsFlyer stores a fingerprint or click_id. After installation and first app launch, the SDK sends an install event to the server. The server matches the install to the click using a deterministic method (click_id in the deeplink) or probabilistic method (IP + User-Agent). The deterministic method is 2–3 times more accurate — that's why we recommend configuring OneLink and Universal Links.

How to Integrate the SDK: Step-by-Step

1. Obtain the Dev Key from the AppsFlyer dashboard (Account → App settings).
2. Add the SDK via Swift Package Manager (iOS) or Gradle (Android).
3. Initialize the SDK in AppDelegate (iOS) or Application.onCreate() (Android).
4. Configure the delegate for handling deep linking (Universal/App Links).
5. Enable debug mode on a test device using isDebug = true (DEBUG build only).

Example for iOS (Swift Package Manager)

import AppsFlyerLib

func application(_ application: UIApplication,
                 didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    AppsFlyerLib.shared().appsFlyerDevKey = "YOUR_DEV_KEY"
    AppsFlyerLib.shared().appleAppID = "YOUR_APP_STORE_ID"
    AppsFlyerLib.shared().delegate = self
    AppsFlyerLib.shared().isDebug = false // only in debug builds!
    return true
}

Example for Android (Gradle)

implementation("com.appsflyer:af-android-sdk:6.+")

// Application.onCreate()
AppsFlyerLib.getInstance().init("YOUR_DEV_KEY", conversionDataListener, this)
AppsFlyerLib.getInstance().start(this)

start() on Android must be called in Application.onCreate(), not in an Activity — otherwise deeplink attribution on cold start will be inaccurate.

In-App Events for Campaign Optimization

AppsFlyer sends in-app events to ad networks for algorithmic optimization:

AppsFlyerLib.shared().logEvent(
    AFEventPurchase,
    withValues: [
        AFEventParamRevenue: 990.0,
        AFEventParamCurrency: "RUB",
        AFEventParamContentId: "sku_123",
        AFEventParamOrderId: "order_456"
    ]
)

Use the standard constants AFEventPurchase, AFEventAddToCart, AFEventCompleteRegistration — they match the Facebook and Google format, increasing optimization accuracy.

Critical Importance of SKAdNetwork with iOS 14+

With iOS 14, Apple limited deterministic attribution via ATT. AppsFlyer implements SKAdNetwork attribution: the conversion value (6 bits) encodes user information and is sent to Apple in aggregated form. To ensure correct operation, call AppsFlyerLib.shared().waitForATTUserAuthorization(timeoutInterval: 60) before start() so the SDK waits for the ATT permission. We guarantee that after configuration, iOS attribution accuracy will not decline.

Setting Up OneLink for iOS and Android

OneLink is an AppsFlyer technology for universal links that work on iOS (Universal Links) and Android (App Links):

func application(_ application: UIApplication,
                 continue userActivity: NSUserActivity,
                 restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
    AppsFlyerLib.shared().continue(userActivity, restorationHandler: nil)
    return true
}

Platform Comparison: iOS vs Android

AppsFlyer vs Other MMPs

What's Included in the Work

We perform turnkey integration: SDK integration, Dev Key configuration, in-app events (purchases, registrations, cart), SKAdNetwork configuration, OneLink / Universal Links / App Links, integration with ad networks via postbacks. We also set up fraud protection and dashboards. Basic attribution integration starts at $800; full integration with OneLink and SKAdNetwork from $1500.

We'll evaluate your project in one day — send us the task description. Get expert advice on all attribution questions.

Timeline

Basic attribution with in-app events: 1–2 days. Full integration with OneLink and SKAdNetwork: up to 3 days. Cost is calculated individually based on app complexity. Average attribution accuracy improvement is 40%, and client satisfaction rate is 98%.

Order AppsFlyer integration and start tracking real ad effectiveness within a week.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.