I have used Appsflyer for almost two to three years.
My main use case for Appsflyer is data analytics testing, where there are multiple events for user actions and particular properties for those events. I have been using Appsflyer to validate whether those events are triggered properly once the user has performed the action and whether all the properties are displayed accurately for those events. This is the main purpose of Appsflyer that I have used.
I validate those events with Appsflyer by leading the iOS platform in the OTT domain. For the user who has signed in as an anonymous user, they launch the application, and once they sign in, there is a user action for signing in. The event will be a successful sign-in. As soon as I log in with any user on the iPhone, I check within a minute or within five minutes for this particular event of successful sign-in. The device name, for example, if I view that I am using an iPhone 14, it will be displayed as iPhone 14. If I am using it from Bangalore, Karnataka, the location will be displayed as Bangalore. To track that specific user journey, I click on that recent event action and validate whether all the properties are displayed or not. Another way to validate is for a specific user using an SSO ID or user ID; based on that unique ID, I search in Appsflyer, download the data, and open it in Excel in CSV format to validate whether all events and properties are displayed accurately. This is how I test.
After performing all the user actions, I conduct sanity, smoke, and regression testing in data analytics testing. I perform all those scenarios end-to-end, and only after that do I go to Appsflyer, searching with a unique ID, maybe an SSO ID for a signed-in user, or a device ID for an anonymous user. I obtain the specific data and download it after five minutes, giving some time for it to save all those user actions. I verify whether all the properties are displayed accurately for that user action that was performed. This is what I basically test.