Checking AppsFlyer🔗
- Make sure that initialization parameters are set correctly. You must use the Apple iTunes Id for your application as the appId (aka iTunesID) for AppsFlyer; on Android, this field is irrelevant. Make sure that DevKey (aka app_key) matches the one specified in your application's settings on the AppsFlyer website.

- Add a call to the checkIntegration method while minimizing the application in accordance with MRGS documentation. Start the application, wait for the initialization to complete, check the logs. Make sure the "checkIntegartion' report shows the correct parameters for AppsFlyer and the value is
allExternalSDKStarted: true. - Conduct AppsFlyer Integration Test. Open your application's settings on the AppsFlyer website. Add your device to the white list (fill in the IDFA field for your iOS device or Google Advertising Identifier for your Android device).

IMEI, Vendor id, etc.
Do not use other identifiers.
- Uninstall your application from the device.
- Run the installation test (SDK Integration Tests -> Non organic Install).

- Install the application via TestFlight link or simply follow the generated link, manually install the application and run it. You can try to minimize/maximize the application few times. Sometimes you need to wait 5-10 minutes before a message appears on the AppsFlyer test page confirming that the test was passed.

- Close the application, but do not uninstall it. Return to the tests section and run the In-app Events Test (select the same device on which you run the NonOrganic Install Test).

- Run the application, make a test payment, wait for the money to accrue, view the test dashboard of the test (sometimes you need to wait 5-10 minutes). There should be a payment event.

- If the tests fail, try enabling the MRGS debug mode for Unity, Android or iOS. After that, enable the AppsFlyer debug mode. To do this, set the debug flag to "true" upon AppsFlyer initialization.
- Run the application, review the logs, where near the tag "appsflyer" you can see requests sent to the server. Response code 200 in the last line indicates that the event was sent correctly. Thoroughly study the request parameters. Perhaps you will see a discrepancy with your configuration, namely: advertiserId differs from the IDFA/GAID that you specified in the test, or app_id does not match yours. appsflyerKey is not displayed, but the first and last letters must match.
Last update: 2023-12-28
Created: 2020-02-27
Created: 2020-02-27