Thank you.This type of data indicates that more than 1 server call is being triggered for this page for some reason. It could be related to implementation or some sort of re-direct.Please audit the page and it's implementation from this perspective.

Thank you.Considering the 4 elements being used, how and which report are you comparing it with, within the interface?

Hi Leo,Are you able to see the Add-in tab in Excel and able to click on 'login' from within the ReportBuilder toolbar? If yes, I assume you are facing this issue because firefox may be your default browser.Recently, a change was made where-in ReportBuilder now uses 'Internet Explorer' to show the sing-in page when users click on login.Do you have IE installed on your machine? If yes, please confirm the version.

There can be multiple reasons to it. Most common ones are:BOT TrafficChanges to Paid Search Detection and/or Internal URL filtersAlso, data comparison with GA isn't recommended considering different algorithm and data interpretation methods each tool uses.

Visits should exactly match.If you can share additional details like API Method, Request payload etc., that should help in understanding why visits aren't matching for your environment.

Hi Oscar,Could you please share a screenshot of the report. It'd help better understand the data you are looking at.Thanks.

Hi Tirumal,Crashes are calculated as part of the LifeCycle metrics.When lifecycle metrics are implemented, a call is made to 'Config.collectLifecycleData' in the 'OnResume' method of each activity. In the 'onPause' method, a call is made to 'Config.pauseCollectingLifeCycleData'.In the 'pauseCollectingLifeCycleData', a flag is set to indicate a graceful exit. When the app is launched again or resumed, 'collectLifecycleData' checks this flag. If the app did not exit successfully as determined by t...