Send your event data from RudderStack to AppsFlyer.
16 minute read
AppsFlyer is a mobile attribution and marketing analytics platform. It offers intuitive dashboards, real-time data reports, and a unique deep linking technology to understand your customers better.
Find the open source code for this destination in the GitHub repository.
Once you have confirmed that the source platform supports sending events to AppsFlyer, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select AppsFlyer.
Assign a name to the destination and click Continue.
Connection settings
The following connection settings are required to configure AppsFlyer as a destination in RudderStack:
Authorization Type: Select the authorization type from the dropdown:
Authorization with dev key: In the AppsFlyer Dev Key field, enter the AppsFlyer dev key.
Authorization with server to server key: In the AppsFlyer server to server Key field, enter the server to server token.
App ID: Enter your Apple or Android app ID.
Android App ID: This the application ID used in your app/build.gradle file.
Apple App ID: This is the iTunes Application ID and it is mandatory for the iOS applications.
To connect a source other than Android or Apple (iOS, watchOS, iPadOS, tvOS), you need to add a user transformation that adds the OS information required in the events. Refer to the Connecting AppsFlyer to non-Android/iOS sources section below for more information.
Use Rich Event Names: Enable this setting to include your app’s screen or page name in the screen or page event names.
Add properties at root in eventValue: Enable this setting to include the custom properties at the root level of eventValue field. Otherwise, RudderStack sends them in the properties field inside eventValue.
Sharing Filter: By default, the value for this setting is set to all. You can use this setting to meet any regulatory requirements like GDPR and CCPA, complying with user opt-out mechanisms, and for any other business use-case. For more information, refer to the AppsFlyer Help Center.
Client-side Event Filtering: This setting is applicable only if you are sending events to AppsFlyer via device mode. It lets you specify which events should be blocked or allowed to flow through to AppsFlyer. Refer to the Client-side Event Filtering guide for more information on this setting.
Status Callback URLs: Specify the callback URLs to be used for user deletion requests. You can provide multiple callback URLs by separating them by a comma.
API Token: Enter your AppsFlyer API token. For more information on obtaining your API token, refer to this AppsFlyer guide.
For user deletion, you must specify both Status Callback URLs and API Token.
Use device-mode to send events: Enable this setting to send events from the Android/iOS SDK to Appsflyer via device mode.
Starting from version 2.3.0 of AppsFlyer Android and iOS device mode, RudderStack supports sending all the custom properties of track events, along with the standard properties.
Adding device mode integration
Once you add AppsFlyer as a destination in the RudderStack dashboard, follow these steps to add it to your project depending on your integration platform:
After adding the dependency, you need to register RudderAppsflyerFactory with your RudderClient initialization as a factory of RudderConfig. To do so, import the RudderAppsflyerFactory.h file in your AppDelegate.m file:
#import "RudderAppsflyerFactory.h"
Starting from AppsFlyer iOS device mode version 2.0.0 and above, the RudderStack SDK does not automatically initialize the AppsFlyer SDK. You need to initialize the AppsFlyer SDK as shown:
Starting from AppsFlyer Android device mode version 2.0.0 and above, the RudderStack SDK does not automatically initialize the AppsFlyer SDK. Initialize the AppsFlyer SDK as shown:
For AppsFlyer React Native device mode version 1.1.0 or above, follow these steps:
(b) Initialize the AppsFlyer SDK:
importrudderClientfrom"@rudderstack/rudder-sdk-react-native";importappsflyerfrom'@rudderstack/rudder-integration-appsflyer-react-native';import{setOptions}from'@rudderstack/rudder-integration-appsflyer-react-native';// Setting options for initializing the appsflyer sdk
setOptions({// dev key from the appsflyer dashboard
"devKey":"<dev_key>",// whether we want to run the appsflyer SDK in the debug mode
"isDebug":true,// whether we want to register for the listeners which would return the conversion data
"onInstallConversionDataListener":true,// ID assigned by the Apple app store for any app which is either published or in the process of getting published
"appleAppId":"<apple_app_id>",// whether we want to register for the listeners which would return the deeplink data
"onDeepLinkListener":true,// the number of seconds for which the appsflyer iOS SDK should wait to allow the app to retrieve the user consent.
"timeToWaitForATTUserAuthorization":60})// Configuration object to be passed while initializing the Rudder React Native // SDK
constconfig={dataPlaneUrl: DATA_PLANE_URL,// Passing appsflyer factory here, since we want to run appsflyer as a device mode destination.
withFactories:[appsflyer]};// Finally, initializing the RudderStack React Native SDK
awaitrudderClient.setup(WRITE_KEY,config);
As seen above, the properties onInstallConversionDataListener and onDeepLinkListener are set to true in the setOptions API to get access to the conversion as well as the attribution data.
Register the callbacks with the listeners:
import{onAppOpenAttribution,onAttributionFailure,onDeepLink,onInstallConversionData,onInstallConversionFailure}from'@rudderstack/rudder-integration-appsflyer-react-native';varonInstallConversionDataCanceller=onInstallConversionData((data)=>{console.log("On Install Conversion Success data is ",data);if(JSON.parse(res.data.is_first_launch)==true){if(res.data.af_status==='Non-organic'){varmedia_source=res.data.media_source;varcampaign=res.data.campaign;console.log('This is first launch and a Non-Organic install. Media source: '+media_source+' Campaign: '+campaign);}elseif(res.data.af_status==='Organic'){console.log('This is first launch and a Organic Install');}}else{console.log('This is not first launch');}})varonAppOpenAttributionCanceller=onAppOpenAttribution((data)=>{console.log("On App Open Attribution Success and the data is ",data);// write your own custom logic here
})varonAttributionFailureCanceller=onAttributionFailure((data)=>{console.log("On App Attribution Failure and the data is ",data);// write your own custom logic here
})varonInstallConversionFailureCanceller=onInstallConversionFailure((data)=>{console.log("On Install Conversion Failure data is ",data);// write your own custom logic here
})varonDeepLinkCanceller=onDeepLink((data)=>{console.log("On Deeplink data is ",data);// write your own custom logic here
})
Depending on the React Native components you are using, you can trigger an appropriate method, for example:
If it’s a class-based component, trigger the remove() method in componentWillUnMount():
If it's a functional component, trigger the `useEffect()` hook:
importReact,{useEffect,useState}from'react';import{AppState,SafeAreaView,Text,View}from'react-native';importappsFlyerfrom'react-native-appsflyer';varonInstallConversionDataCanceller=appsFlyer.onInstallConversionData((res)=>{if(JSON.parse(res.data.is_first_launch)==true){if(res.data.af_status==='Non-organic'){varmedia_source=res.data.media_source;varcampaign=res.data.campaign;console.log('This is first launch and a Non-Organic install. Media source: '+media_source+' Campaign: '+campaign);}elseif(res.data.af_status==='Organic'){console.log('This is first launch and a Organic Install');}}else{console.log('This is not first launch');}},);varonAppOpenAttributionCanceller=appsFlyer.onAppOpenAttribution((res)=>{console.log(res);});appsFlyer.initSdk({devKey:'K2a*********99',isDebug: false,appId:'41******5',},(result)=>{console.log(result);},(error)=>{console.error(error);},);constHome=(props)=>{useEffect(()=>{return()=>{// Optionaly remove listeners for deep link data if you no longer need them after componentWillUnmount
if(onInstallConversionDataCanceller){onInstallConversionDataCanceller();console.log('unregister onInstallConversionDataCanceller');onInstallConversionDataCanceller=null;}if(onAppOpenAttributionCanceller){onAppOpenAttributionCanceller();console.log('unregister onAppOpenAttributionCanceller');onAppOpenAttributionCanceller=null;}};});return({'App'});};
Open AppDelegate.m in the ios folder of your app and include the following snippet:
#import "RudderIntegrationAppsflyerReactNative.h"
-(BOOL)application:(UIApplication*)applicationopenURL:(NSURL*)urloptions:(NSDictionary*)options{[[AppsFlyerAttributionshared]handleOpenUrl:urloptions:options];returnYES;}// Open URI-scheme for iOS 8 and below
-(BOOL)application:(UIApplication*)applicationopenURL:(NSURL*)urlsourceApplication:(NSString*)sourceApplicationannotation:(id)annotation{[[AppsFlyerAttributionshared]handleOpenUrl:urlsourceApplication:sourceApplicationannotation:annotation];returnYES;}// Open Universal Links
-(BOOL)application:(UIApplication*)applicationcontinueUserActivity:(NSUserActivity*)userActivityrestorationHandler:(void(^)(NSArray*_Nullable))restorationHandler{[[AppsFlyerAttributionshared]continueUserActivity:userActivityrestorationHandler:restorationHandler];returnYES;}
To add AppsFlyer to your Cordova project:
Navigate to the root folder of your application and run the following command:
Initialize the AppsFlyer Android SDK by overriding the onCreate method in MainActivity.java file (located in your app’s android/app/src/main/java/com/your_org/your_app_name/ folder). This ensures that AppsFlyer’s Android SDK is initialized beforehand and is available for the Rudderstack Flutter SDK.
Initialize the AppsFlyer iOS SDK by adding the following code at the top of the didFinishLaunchingWithOptions method in the AppDelegate.swift file (located in your app’s ios/Runner/ folder):
It is highly recommended to send events to AppsFlyer via cloud mode only in the following scenarios:
To use RudderStack’s Transformations feature to transform your events
To send server-side events
To send events to AppsFlyer via cloud mode, you need the AppsFlyer ID generated by the Appsflyer SDK that is integrated with your app. See Obtaining the AppsFlyer ID for reference.
Once you obtain the AppsFlyer ID, you can send events to AppsFlyer via cloud mode by including the externalId key within your events’ context. The format of externalId is as shown:
The type of externalId. This must always be set to appsFlyerExternalId.
Obtaining the AppsFlyer ID
As mentioned above, the AppsFlyer ID is generated by the Appsflyer SDK integrated with your app.
If the AppsFlyer SDK is directly loaded on your app, refer to this AppsFlyer documentation to obtain the AppsFlyer ID.
If your AppsFlyer SDK is loaded through RudderStack (device mode integration), then you can obtain the AppsFlyer ID by including the code snippet in your app, depending on your platform of integration:
RudderStack’s track call is mapped to the standard AppsFlyer events wherever possible.
The following table lists the event mapping from RudderStack to AppsFlyer:
RudderStack event
AppsFlyer event
Products Searched
af_search
Product Viewed
af_content_view
Product List Viewed
af_list_view
Product Added to Wishlist
af_add_to_wishlist
Product Added
af_add_to_cart
Checkout Started
af_initiated_checkout
Order Completed
af_purchase
Product Removed
remove_from_cart
first_purchase
first_purchase
Promotion Viewed
af_ad_view
Promotion Clicked
af_ad_click
Payment Info Entered
af_add_payment_info
Product Shared
af_share
Cart Shared
af_share
Product Reviewed
af_rate
For any event not present in the above table, RudderStack makes the following changes to the event name before sending it to AppsFlyer via the native SDK:
Converting the entire event name to lower case
Replacing any space with an underscore
Along with the above event mapping, RudderStack also maps the event properties to the corresponding AppsFlyer event properties, as shown below:
RudderStack property
AppsFlyer property
query
af_search_string
price
af_price
product_id
af_content_id
category
af_content_type
currency
eventCurrency
products
RudderStack formulates this list as per the List View specification and passes it to the property af_content_list.
quantity
af_quantity
order_id
af_receipt_id
revenue
af_revenue
A sample track call for an iOS app is shown below:
[[RSClientsharedInstance]track:@"Accepted Terms of Service"properties:@{@"foo":@"bar",@"foo_int":@134}];
Screen
For all screen calls sent from the SDK, RudderStack calls AppsFlyer’s trackEvent method with screen as the event name. All the event properties are passed to AppsFlyer without any modification.
For the automatically recorded screen calls, RudderStack obtains a Boolean property called automatic.
Advertising ID
RudderStack utilizes the advertising ID for the AppsFlyer destination if it is set as per the following specifications:
You can find the advertising ID in your event’s context.device.advertisingId.
ATTrackingManager
If the ATTrackingManager.trackingAuthorizationStatus is passed according to ATTrackingManager authorization consent, RudderStack will utilize it for the AppsFlyer destination.
You can find trackingAuthorizationStatus in your event’s context.device.attTrackingStatus.
Error messages
This section covers some of the possible error messages you may encounter while using this integration.
The SDK automatically sets the OS Name and it can be found in context.os.name.
Appsflyer ID is not set. Rejecting the event.
This error occurs when the appsflyerExternalId is not set. Refer to the Sending events via the RudderStack cloud mode section for more information on setting the appsflyerExternalId.
Debugging
RudderStack sets the logLevel in AppsFlyer based on the logLevel set for the RudderClient. If it is set to DEBUG or more, RudderStack sets the logLevel to VERBOSE for AppsFlyer.
For anything below that, RudderStack sets the logLevel to NONE for AppsFlyer.
FAQ
Where do I get the AppsFlyer dev key?
You can find the AppsFlyer Dev Key by logging into your AppsFlyer account and navigating to the Apps Settings page in your dashboard. For more information, refer to this AppsFlyer Help Center page.
I get an error saying “Build input file cannot be found” for iOS device mode. What should I do?
The latest AppsFlyer SDK requires XCode 12. Make sure you meet this requirement. You may have to downgrade your AppsFlyer SDK to build with a lower version of XCode.
You can declare the pod version in your Podfile as shown:
pod'Rudder-Appsflyer',' 1.0.0'
How do I get the AppsFlyer ID to send events from my mobile sources via the RudderStack cloud mode?
To send events to AppsFlyer via cloud mode, you first need to obtain the AppsFlyer ID generated by the Appsflyer SDK.
You can get this ID by either directly loading the native AppsFlyer SDK on your app, or loading it via RudderStack (device mode integration).
In case of a device mode integration, include the following code snippet (depending on your platform of integration) in your app to get the AppsFlyer ID:
you obtain the AppsFlyer ID, you can send events via cloud mode by by including the externalId key within your events’ context. For more information, refer to the Sending events via the RudderStack cloud mode section above.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.