@NorData
It is possible that the Adobe SDK might not be correctly configured to track each launch event. The "launch" event should be triggered every time the app is opened, including when it is resumed from the background. If it's only being triggered during a cold start (when the app is launched from a fully closed state and not when the app is installed or resumed from the background), the number of launches could be underreported.
If the app is crashing or encountering errors shortly after being launched, the "launch" event might not be recorded correctly. This could lead to a scenario where users attempt to open the app, but the launch event isn't captured due to the app failing to fully initialize.
Next steps:
-- Verify Implementation: Double-check the SDK implementation to ensure that the launch event is correctly configured and firing as expected on both Android and iOS.
-- Monitor App Crashes: Check crash reports to see if users are experiencing issues that could prevent the launch event from being recorded.
-- Contact Adobe Support: If you continue to see discrepancies after verifying the implementation, it might be helpful to reach out to Adobe Support to ensure there are no processing issues on their end.
Hope this helps!
