AppsFlyer Integration

AppsFlyer is a global platform for mobile marketing analytics and attribution that helps track ad campaign performance and optimize mobile app user acquisition. It comprehensively analyzes user behavior data to evaluate the effectiveness of marketing strategies and provides transparent visibility into performance across various marketing channels.

By integrating Hackle with AppsFlyer, you can import mobile app acquisition data as User Properties and use them for A/B Test targeting or detailed analysis.

Want to integrate AppsFlyer with Hackle?

Integrate AppsFlyer with Hackle and experience deeper analysis and growth.

👉 Contact us now

Setting Up AppsFlyer Integration

Hackle Dashboard Configuration

1. Before integrating, both the Hackle SDK and AppsFlyer SDK must be installed in your service.

2. Go to Workspace Settings > External Integration in the Hackle Dashboard. (Link)

   
3. Select AppsFlyer.

   You can check the AppsFlyer integration status and the API Key required for integration. The integration status will change to "Integration Complete" once the API Key is registered in AppsFlyer and events are successfully received in Hackle from AppsFlyer. Proceed to the next step in the AppsFlyer Dashboard.

   

AppsFlyer Dashboard Configuration — Adding a Partner

Menu -> Configuration -> Partner Marketplace

Navigate to Partner Marketplace

Search for Hackle in Partner Marketplace and click the Hackle partner

Navigate to Integration Management

Partner Integration Configuration

• Hackle API Key Setup Enter the API Key issued from the Hackle Dashboard above.

• Hackle Partner Permissions Setup

Menu -> Configuration -> Active Integrations (Permissions tab)

• Default Postback Configuration

For user acquisition source, select All Media Sources, Including Organic

Change user acquisition source

You have now completed the AppsFlyer Dashboard configuration for sending data from AppsFlyer to Hackle. Finally, complete the SDK integration work to connect the transmitted data with other Hackle data.

SDK Integration Work

To properly use data sent from AppsFlyer in Hackle, you must send the Hackle Device ID to the AppsFlyer SDK.

Configure the AppsFlyer integration code as shown below. The Hackle Device ID can only be retrieved properly after the Hackle SDK is initialized (init).

HackleCustomId is sent with all postbacks and is used to identify users.

Postback events are billed the same as regular events.

HashMap<String, Object> customData = new HashMap<String,Object>();

String deviceId = HackleApp.getInstance().getDeviceId();
customData.put("hackleCustomId", deviceId);

AppsFlyerLib.setAdditionalData(customData);

let deviceId = Hackle.app()!.deviceId
let customData = ["hackleCustomId": deviceId]

AppsFlyerLib.shared().customData = customData

App Install Event ($af_install)

App install events are sent to Hackle as an event called $af_install.

In-App Event ($af_inapp)

Additionally, by configuring in-app event postbacks, you can also send events collected through AppsFlyer to Hackle in the form of $af_inapp. Events collected via postback cannot be used as triggers for In-App Messages or Push Messages that require real-time processing, but they can be used for data analysis purposes such as checking conversion status or querying amounts.

In-App Event Configuration

Event Timestamp Adjustment

By default, events collected via postback are stored based on the time the event is sent from AppsFlyer to the Hackle server. In this case, there may be a difference of a few minutes from when the actual event occurred. If you send the Timestamp parameter in the postback parameters for install and in-app events, the event is stored based on the actual time the event occurred in AppsFlyer.

Timestamp