AppsFlyer is a leading Mobile Attribution & Marketing Analytics platform that allows app marketers to easily measure the performance of all their marketing channels - paid, organic and social - from a single real-time dashboard.
mParticle’s integration with AppsFlyer includes a required Kit integration and an optional server-side integration. The Kit forwards event data from your app to AppsFlyer on the client side, and also handles app install attribution, uninstall tracking, and deeplinking, including deferred deeplinking. Supplementary data from outside your app can be forwarded to mParticle via our Events API and sent on to AppsFlyer server-to-server.
Connect your iOS and/or Android workspaces to AppsFlyer. You will need to provide your Dev Key, which you can access from the Settings page of your organization’s AppsFlyer dashboard. For an iOS connection, you will also need your Apple App ID. Make sure you remove the ‘ID’ prefix. For example, if your App ID is
id12345, just enter
12345. For more information on setting up a new mParticle connection, see the Platform Guide.
|You can find your Dev Key within the AppsFlyer settings page.
|Apple App ID
|You can find your app’s Apple ID in the app page in iTunes Connect.
mParticle’s AppsFlyer integration requires that you add the AppsFlyer Kit to your iOS or Android app. Just by adding the binary to your app:
UIApplication (iOS) and
Activity (Android) lifecycle events to the AppsFlyer SDK.
mParticle publishes the AppsFlyer Kit as separate iOS and Android libraries which have a transitive dependency on the mParticle core libraries. You can add them to your app via Carthage, Cocoapods, Swift Package Manager, or Gradle:
# Sample Podfile
target '<Your Target>' do
github "mparticle-integrations/mparticle-apple-integration-appsflyer" "~> 8.0"
To integrate the SDK using Swift Package Manager, open your Xcode project and navigate to File > Swift Packages > Add Package Dependency
Enter the repository URL `https://github.com/mparticle-integrations/mparticle-apple-integration-appsflyer` and click Next.
You can leave the version settings as default and click Next one more time to complete adding the package dependency.
// Sample build.gradle
// Ensure the Kit version matches that of the mParticle Core SDK that you're using
AppsFlyer’s SDK requires the forwarding of the Google Play Install Referrer Intent. The AppsFlyer kit will take care of this for you as long as you’ve added mParticle’s
ReferrerReceiver to you manifest, or you are manually forwarding the Intent to our
ReferrerReceiver class. The mParticle SDK will then forward the Install Referrer intent to each configured kit, including AppsFlyer.
Please see the Android SDK setup guide to ensure your manifest is configured properly.
The AppsFlyer SDK exposes client-side deep linking and attribution APIs, all of which are supported by the mParticle AppsFlyer kit and are covered in this section. The core use-cases are:
Each platform has very specific requirements to ensure that the above functionality is supported. The minimum requirements are:
devKey configured above matches your AppsFlyer app.
AndroidManifest.xml has the proper Intent Filters to match any deep link domains that you’re testing.
mParticle’s SDKs will automatically initialize the AppsFlyer SDK, forwarding the required
UIApplication lifecycle events and the
continueUserAcivity events for iOS and Android, as well as registering a delegate such that you can retrieve deep linking and attribution parameters on the client-side to customize your user’s in-app experience.
Specifically, the AppsFlyer SDK exposes one distinct callback:
mParticle’s API includes a wrapper for this callback, and both the iOS and Android kits expose a constant to inform you when the callback has been fired and if it was successful. On both platforms, the iOS/Android kit will register a delegate/callback with the AppsFlyer SDK on initialization and for the lifetime of the app’s process, and will call your completion handler block (iOS) or
AttributionListener (Android) whenever there is new conversion data available.
When a user clicks a OneLink link, the AppsFlyer SDK retrieves available OneLink data from the AppsFlyer servers. Then, the UDL API calls the
didResolveDeepLink() method which returns a
DeepLinkResult object containing a status and (if successful) a
DeepLink object containing the
deep_link_sub1-10 parameters you can use to customize the resulting in-app outcome.
However, when users deep link directly using universal or app links, the
didResolveDeepLink method returns the full link unparsed since the app opens directly without going through AppsFlyer first. You can read more about AppsFlyer’s deep linking methods here.
The following core test scenarios that should be verified:
The AppsFlyer Kit will forward app events and eCommerce events to AppsFlyer. Custom Mappings are available to map your custom app events onto AppsFlyer’s event names. Refer to the iOS and Android SDK docs for details on instrumenting your app for event tracking:
Note that AppsFlyer enforces a limit of 45 characters for event names.
The source code for each kit, as well as sample apps, are available on Github:
mParticle can forward app events and commerce events received via our Events API to AppsFlyer’s server-API. Note that AppsFlyer requires data to be linked to a unique AppsFlyer ID, generated client-side by the AppsFlyer Kit. mParticle stores the AppsFlyer ID in its internal user profile. This means that:
att_authorization_status is available:
Was this page helpful?