Logging Crash events to amplitude

  • 20 March 2023
  • 3 replies


Our scenario is we have crash data logged to crashlytics & event data logged via amplitude.

We have a recurring crash effecting a significant % of user-base, but, it happens only when app is backgrounded. 

We want to quickly understand if the crashes are preventing users from converting, if so severity / priority of the issue is higher.

It doesn’t seem common from glancing at documentation to log a crash in amplitude, but it feels like a larger investment of time to create a report in Microsoft BI or other to correlate the two data sources.


Does anyone have any advice or experience around this scenario?






Best answer by Saish Redkar 20 March 2023, 18:53

View original

3 replies

Userlevel 7
Badge +10

Hi @lukeandrewjeffery 

I would start with understanding your key use cases here - do you want to understand impact of crash events from a usage perspective only or understand them from a user session POV?

The usual practice is to ingest such backend events via server side implementation. These would normally be out of session events ( session_id = -1 ) if you are already tracking sessions in your app.

So for analysis you can use the segment approach and see the impact based on who received the crash events and who didn’t in the time interval.

However, understanding session metrics for crashes will be a bit weird since these will be out of session events.

Hope this helps.



Ah, sorry, i’ve missed some key information.

I’m speaking of crashes within our Android application on the user’s phone. The events are captured via the segment SDK and sent to amplitude.

The question was broadly around people’s practice of logging a crash event on Android/iOS and sending to amplitude when it occurs 

For anyone following along. We decided not to send crash events to Amplitude from our Android app because 

#1 Nobody else seemed to be doing it / there isn’t anything in the dev docs or in forums

#2 It looks difficult to implement from developer perspective.


This is a bit of a shame for speed of analysis, but, it makes sense with the way amplitude positions itself. They want you to export your behvioural data to a tool which specialises in crashes to understand that better