Please enable JavaScript.
Coggle requires JavaScript to display documents.
AppsFlyer events tracking risks - Coggle Diagram
AppsFlyer events tracking risks
Dependencies
Lost Internet connection
Crash of the platform
Crash of the apps
Data corruption
Personal data may be exposed in the Raw data reports
Data of different users may be mixed and therefore exposed
Can the customer user id affect the data vulnerability?
Data Correctness
Data not transferring between the apps to AppsFlyer
Data of different users is mixed
Inconsistent id's to track users
Missing Customer User ID
Fresh install may make an impact on the customer user id column and not record them
Platform specification
time specifications when different events are tracked
how many events at a time are handled
after what time span the recorded events are no longer visible
Environment
Events tracked on dev, no staging, no prod
Events tracked on dev,, on staging, no prod
Events tracked on staging, no dev, no prod
Events tracked on staging, on prod, no dev
Time intervals
Events may not be recording because of short time span between different events
Events may disappear after certain time
Events may record too late because of AppsFlyer platform problems
Error handling
Crash due to AppsFlyer not able to capture events
Lost internet connection error
Some events may not have a Customer User ID after a fresh install
Device compability
Events are not recorded on some OS versions
Fresh install/ App kill ay affect the recording of the customer user id
Performance
Some events may have missing data due to the app's state
Test how the events are recorded by making deposits after registration
Test how the events are recorded by making deposit after killing the app first
Non-organic events may be recorded as organic
Organic event may be recorded as non-organic