Mobile Install Attribution Setup: MMP Integration

Install Attribution Setup

We have configured attribution for 50+ mobile apps — from fintech startups to gaming with budgets ranging from 500,000 to 10 million rubles per month. Typical pain: the ad budget is spread across five channels (Google UAC, Meta Ads, TikTok, Telegram, ASA), installs are happening, conversions exist, but marketing doesn't know which channel brought the buyer. Without proper attribution, up to 40% of the budget (e.g., 120,000 out of 300,000 rubles) goes to bots and non-targeted installs. Our guarantee: transparent reporting per installer and cost savings.

How Attribution Works: MMP in the Middle of the Chain

Mobile Measurement Partner — an independent third party between ad networks and your app. Principle: user clicks on an ad — MMP records the click with campaign parameters. After installation, the app SDK matches the device with the saved click and attributes it to the source. Key players: AppsFlyer, Adjust, Branch, Kochava. For Russia, AppsFlyer and Adjust are the standard.

Matching mechanics after iOS 14.5 split:

• Deterministic (exact): via SKAdNetwork postbacks — when the user granted ATT permission
• Probabilistic (probabilistic): via fingerprint (IP + User-Agent + click time) — without ATT, accuracy 60–70%

On Android, Google Play Referrer API provides an accurate attribution token without permissions.

How to Integrate AppsFlyer SDK on iOS and Android

iOS (Swift)

// AppDelegate.swift
import AppsFlyerLib

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

func applicationDidBecomeActive(_ application: UIApplication) {
    AppsFlyerLib.shared().start() // after ATT response
}

According to the official AppsFlyer documentation (AppsFlyer Developer Guide), start() should not be called before ATT response — otherwise Apple will block the postback. Correct sequence: show ATT → wait for response → call start().

Android (Kotlin)

AppsFlyerLib.getInstance().init("YOUR_DEV_KEY", object : AppsFlyerConversionListener {
    override fun onConversionDataSuccess(data: Map<String, Any>) {
        val campaign = data["campaign"] as? String
        val mediaSource = data["media_source"] as? String // "googleadwords_int" for Google UAC
    }
    override fun onConversionDataFail(error: String) {}
    override fun onAppOpenAttribution(data: Map<String, Any>) {}
    override fun onAttributionFailure(error: String) {}
}, this)

AppsFlyerLib.getInstance().start(this)

On Android, add the dependency com.android.installreferrer:installreferrer:2.2 — without it, Google UAC attribution will be probabilistic.

Why Postbacks Are Critical for Ad Campaign Optimization

Without postbacks, ad networks do not receive signals about target events (purchase, registration). Google UAC and Meta optimize for install, not in-app events. Setting up postbacks to each network is mandatory. A typical mistake: not specifying the event_name for purchase in the Meta postback, causing the network to consider just an install as a conversion. The cost of fixing such an error is 10,000 to 30,000 rubles per day of wasted budget.

Deeplink Attribution: Where It Often Breaks

OneLink (AppsFlyer) / Universal Links / App Links allow attributing not only the install but also a specific deeplink. A user clicks a link in Telegram, installs the app, and lands on the correct screen with proper attribution.

Typical errors:

• Universal Links stop working after an app update — the apple-app-site-association file is not updated or the Bundle ID changed.
• Missing onAppOpenAttribution — repeat deeplink visits are not attributed.
• On Android, no intent-filter for App Links is specified, and the system opens the browser instead of the app.

MMP Comparison: AppsFlyer vs Adjust vs Branch

Our experience: for fintech with high cost per install, AppsFlyer is better due to more accurate anti-fraud. For e-commerce with deep deeplinking, Branch provides better user experience.

Integration Process

Verifying Attribution Correctness

What's Included in the Work

• MMP selection and licensing (if required)
• SDK integration on both platforms (iOS + Android)
• ATT flow and SKAdNetwork configuration
• Postback setup for 3+ ad networks
• Deeplink attribution implementation (OneLink / Branch Links)
• Testing and verification

Guarantee: we provide a test report and postback verification. Our engineers are certified in AppsFlyer and Adjust.

Timelines and Cost

• Basic MMP integration on both platforms: 3–5 days
• With deeplink and all ad postbacks: up to 7 days
• Cost is estimated individually — contact us for an assessment. The budget typically varies depending on complexity.

Mistakes to Avoid

• Calling start() before ATT — Apple blocks postbacks.
• Missing onAppOpenAttribution handler — loss of repeat visit attribution.
• Ignoring Apple App Site Association — Universal Links fail.
• Incorrect event name in postback — network does not optimize for the target action.
• Using a single postback URL for all networks — each network requires its own format.

Order attribution integration — we will set up the MMP for your stack and ad channels in 5–7 days. Get a consultation for your project.

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.