Download the latest Unity plugin from GitHub.

Use one of the following installation methods.

To set up the required Android permissions:

Set the following permissions in AndroidManifest.xml:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />

Apps targeting API level 31 (Android 12) should add the following permission to AndroidManifest.xml to access the Android Advertising Identifier:

<uses-permission android:name="com.google.android.gms.permission.AD_ID" />

• The key is unique and identifies the account. In some cases there is an app-level key. 
• Dev key is mandatory.

To get the dev key:

1. In AppsFlyer, go to Configuration > App Settings.
2. Get the dev key. 

To send events:

• Specify the event name and parameters.
• See related lists: 
  • List of recommended event names and structures
  • List found in AFInAppEvents class.

[Best practice] Use event names and parameters for the following reasons:

• Standard naming: AppsFlyer can automatically map events to SRNs such as Meta ads, Google, and Twitter.
• Backward compatibility: No issue arises if AppsFlyer changes an event name or parameter. The implementation is backward compatible.

Report revenue by adding the af_revenue parameter to in-app events.

• Populate af_revenue with numeric values. Negative values are permitted. 
• The af_revenueparameter populates AppsFlyer revenue counters and raw data fields. Doing so enables marketers to view revenue in the dashboard.
• Revenue can be sent using other parameters, but the AppsFlyer platform won't recognize it as revenue. Click here for more details. 
• Revenue values must not contain comma separators, currency symbols, or text.
  Example revenue event: 1234.56

Best practice: Learn about currency settings, display, and currency conversion.

 Currency code requirements when sending revenue events

• Default currency: USD
• Use a 3-character ISO 4217 code (an example follows).
• Set the currency code by calling the API:
  

  AppsFlyer.setCurrencyCode("ZZZ")

Example: In-app purchase event with revenue

This purchase event is for 200.12 Euros. For the revenue to reflect in the dashboard use the following. 

System.Collections.Generic.Dictionary<string, string> purchaseEvent = new 
System.Collections.Generic.Dictionary<string, string> ();
purchaseEvent.Add(AFInAppEvents.CURRENCY, "EUR");
purchaseEvent.Add(AFInAppEvents.REVENUE, "200.12");
purchaseEvent.Add(AFInAppEvents.QUANTITY, "1");
purchaseEvent.Add(AFInAppEvents.CONTENT_TYPE, "category_a",);
AppsFlyer.sendEvent ("af_purchase", purchaseEvent);

Record negative revenue

Record negative revenue using a minus sign.

• Revenue value is preceded by a minus sign.
• The event name has a unique value, "cancel_purchase". This lets you identify negative revenue events in raw data reports and in the Dashboard.

Example: App user receives a refund or cancels a subscription.

System.Collections.Generic.Dictionary<string, string> purchaseEvent = new 
System.Collections.Generic.Dictionary<string, string> ();
purchaseEvent.Add(AFInAppEvents.CURRENCY, "USD");
purchaseEvent.Add(AFInAppEvents.REVENUE, "-200");
purchaseEvent.Add(AFInAppEvents.QUANTITY, "1");
purchaseEvent.Add(AFInAppEvents.CONTENT_TYPE, "category_a");
AppsFlyer.sendEvent ("cancel_purchase", purchaseEvent);

The plugin provides server verification for in-app purchases.

To validate a purchase, operating system specific instructions:

#if UNITY_ANDROID && !UNITY_EDITOR
 AppsFlyerAndroid.validateAndSendInAppPurchase(
 "publicKey", 
 "signature", 
 "purchaseData", 
 "price", 
 "currency", 
 null, 
 this);
#endif

#if UNITY_IOS && !UNITY_EDITOR
 AppsFlyeriOS.validateAndSendInAppPurchase(
 "productIdentifier", 
 "price", 
 "currency", 
 "tranactionId", 
 null, 
 this);
#endif

Method parameters

• Event name: maximum 45 characters
• Event value: must not exceed 1000 characters - if longer we can truncate it
• Supports non-English characters for in-app events (and other APIs)
• Pricing and revenue:
  • Only use numbers and decimals such as 5 or 5.2
  • Up to 5 numbers after the decimal are permitted. For example, 5.12345

Record in-app events by calling sendEvent and include the event name and value parameters.
See In-app events for more details.

Example: How to record an in-app purchase event

For a comprehensive list of ready-made code snippets per vertical, see our guides for rich in-app events per verticals.

System.Collections.Generic.Dictionary<string, string> purchaseEvent = new 
System.Collections.Generic.Dictionary<string, string> ();
purchaseEvent.Add(AFInAppEvents.CURRENCY, "USD");
purchaseEvent.Add(AFInAppEvents.REVENUE, "200");
purchaseEvent.Add(AFInAppEvents.QUANTITY, "2");
purchaseEvent.Add(AFInAppEvents.CONTENT_TYPE, "category_a");
purchaseEvent.Add(AFInAppEvents.CONTENT_ID, "092");
AppsFlyer.sendEvent (AFInAppEvents.PURCHASE, purchaseEvent);

Sometimes users generate in-app events, while they have no internet connection. AppsFlyer caches the event and reports when possible. 

• The plugin sends events to AppsFlyer servers and waits for a response.
• If the plugin doesn’t get a 200 response, the event is stored in the cache.
• After receiving the next 200 response, the cached event is re-sent to the server.
• If the cache holds multiple events, they are sent to the server one after the other.

OneLink:

• Detects the device type (Android and iOS, desktop, etc.) when a user clicks, then
• Redirects the user to the correct destination: Google Play, iOS app store, out-of-store markets, or web pages.

To implement multi-platform attribution links and review the basics of deep linking, see the OneLink redirection guide.

Use deep linking to direct existing users to specific activities and customized content. 

An app owner and a developer must work together to set up deep linking with OneLink:

• App owner must access the AppsFlyer dashboard
• Developer must access the app

See setting up deep linking with OneLink.

Deferred deep linking lets you deep link new users to direct them to specific activities and customized content with the first launch after an app install. 

Standard deep linking also directs users to specific activities and customized content, but an app must already be installed on the user's device.

To set up deferred deep linking with OneLink:

• Developer needs access to the AppsFlyer platform.
• AppsFlyer platform setup for deferred and standard deep linking is the same.
• Must implement additional logic in the app to deep link users and provide them with customized content after they install and launch the app.

Check deferred deep linking for more information.

The plugin provides conversion or engagement data after every install or deep-linking event. Use this data to customize content or the app's programmatic behavior.

To receive deep link data:

• Implement callback onAppOpenAttribution(found inIAppsFlyerConversionDataclass); it is called by the AppsFlyer plugin.
• Returned OneLink/attribution link parameters trigger an app to open.
• Parse the values and apply the logic to trigger the relevant app page.

public void onAppOpenAttribution(string attributionData)
 {
 AppsFlyer.AFLog("onAppOpenAttribution", attributionData);
 Dictionary<string, object> attributionDataDictionary = AppsFlyer.CallbackStringToDictionary(attributionData);
 // add direct deeplink logic here
 }

Check deep linking data for more information.

To obtain AppsFlyer conversion data:

1. Implement the IAppsFlyerConversionDatabase.
2. Call the initSDK method with this as the last parameter.
3. Use the onConversionDataSuccess method to redirect the user. 

See API reference for onConversionDataSuccess.

using AppsFlyerSDK;

public class AppsFlyerObjectScript : MonoBehaviour , IAppsFlyerConversionData
{
    void Start()
    {
        /* AppsFlyer.setDebugLog(true); */
        AppsFlyer.initSDK("devkey", "appID", this);
        AppsFlyer.startSDK();
    }

    public void onConversionDataSuccess(string conversionData)
    {
        AppsFlyer.AFLog("onConversionDataSuccess", conversionData);
        Dictionary<string, object> conversionDataDictionary = AppsFlyer.CallbackStringToDictionary(conversionData);
        // add deferred deeplink logic here
    }

    public void onConversionDataFail(string error)
    {
        AppsFlyer.AFLog("onConversionDataFail", error);
    }

    public void onAppOpenAttribution(string attributionData)
    {
        AppsFlyer.AFLog("onAppOpenAttribution", attributionData);
        Dictionary<string, object> attributionDataDictionary = AppsFlyer.CallbackStringToDictionary(attributionData);
        // add direct deeplink logic here
    }

    public void onAppOpenAttributionFailure(string error)
    {
        AppsFlyer.AFLog("onAppOpenAttributionFailure", error);
    }
}

Allowlist the test device.

Simulate organic and non-organic installs.

Simulate an organic install

Organic installs are unattributed installs; they are usually the result of installs made directly via app stores. To simulate an organic install, follow these instructions.

Simulate a non-organic install

Non-organic installs are attributed installs; they are usually the result of an ad engagement. To simulate a non-organic install, follow these instructions.