Mobile application crash monitoring user interface
Various methods and systems for tracking incomplete purchases in correlation with application performance, such as application errors or crashes, are provided. In this regard, aspects of the invention facilitate monitoring transaction and application error events and analyzing data associated therewith to identify data indicating an impact of incomplete purchases in relation to an error(s) such that application performance can be improved. In various implementations, application data associated with an application installed on a mobile device is received. The application data is used to determine that an error that occurred in association with the application installed on the mobile device correlates with an incomplete monetary transaction initiated via the application. Based on the error correlating with the incomplete monetary transaction, a transaction attribute associated with the error is determined.
1. A computer-implemented method comprising:
providing, at a developer device, a graphical user interface configured to present crash data associated with crashes of a mobile application on mobile devices, the crashes having occurred during user transactions conducted with the mobile application, wherein at least a portion of the crash data is usable for modifying the mobile application to reduce subsequent occurrences of an error, the crash data comprising:
a list of crash types of the crashes, wherein crash types within the list of crash types are ranked based on a determined monetary impact associated with each of the crash types;
a first transaction attribute associated with the crashes and generated by aggregating application data of the mobile application provided from the mobile devices; and
a second transaction attribute indicating a transaction status, of one or more of the user transactions, determined to correlate with a first set of the crashes.
2. The method of claim 1 , wherein the first transaction attribute comprises a graphical depiction of a trend over time of a number of occurrences of a set of the crashes of a particular one of the crash types.
3. The method of claim 1 , wherein the graphical user interface is configured to present each of the crash types in association with a corresponding graphical depiction of a trend over time of a number of occurrences of a corresponding set of the crashes of the crash type, wherein the first transaction attribute is one of the graphical depictions.
4. The method of claim 1 , wherein the second transaction attribute comprises application data of the mobile application captured from one of the mobile devices in association with a crash of the set of crashes.
5. The method of claim 1 , wherein the transaction status is a monetary transaction determined to be incomplete based on a lack of a subsequent completion event, wherein the second transaction attribute comprises a monetary amount associated with a set of one or more items determined to be abandoned in association with the first set of the crashes.
6. The method of claim 1 , wherein the graphical user interface is configured to present the list of crash types in association with, for each of the crash types, a corresponding one of a set of a first transaction attributes including the first transaction attribute.
7. The method of claim 1 , wherein the graphical user interface is configured to present the list of crash types as a list of trending crash types comprising a list of most frequent crashes over a particular duration of time.
8. The method of claim 1 , wherein the list of crash types is associated with a set of the crashes determined to correspond with incomplete monetary transactions, the incomplete monetary transactions identified based on a detected event indicating initiation of a monetary transaction and a detected lack of a subsequent event indicating completion of the monetary transaction within a corresponding session.
9. The method of claim 1 , wherein the graphical user interface is configured to present each of the crash types in association with (i) a corresponding graphical depiction of a trend over time of a number of occurrences of a corresponding set of the crashes of the crash type, and (ii) a monetary amount associated with a set of one or more items determined to be abandoned in association with the corresponding set of the crashes of the crash type.
10. A system for crash monitoring, the system comprising:
one or more data processors; and
one or more computer-readable storage media containing instructions which when executed on the one or more data processors, cause the one or more processors to perform operations including:
providing, at a developer device, a graphical user interface configured to present crash data associated with crashes of a mobile application on mobile devices, the crashes having occurred during user transactions conducted with the mobile application, wherein at least a portion of the crash data is usable for modifying the mobile application to reduce subsequent occurrences of an error, the crash data comprising:
a list of crash types of the crashes, wherein crash types within the list of crash types are ranked based on a determined monetary impact associated with each of the crash types;
a first transaction attribute associated with the crashes and generated by aggregating application data of the mobile application provided from the mobile devices; and
a second transaction attribute indicating a transaction status, of one or more of the user transactions, determined to correlate with a first set of the crashes.
11. The system of claim 10 , wherein the first transaction attribute comprises a graphical depiction of a trend over time of a number of occurrences of a set of the crashes of a particular one of the crash types.
12. The system of claim 10 , wherein the graphical user interface is configured to present each of the crash types in association with a corresponding graphical depiction of a trend over time of a number of occurrences of a corresponding set of the crashes of the crash type, wherein the first transaction attribute is one of the graphical depictions.
13. The system of claim 10 , wherein the second transaction attribute comprises application data of the mobile application captured from one of the mobile devices in association with a crash of the set of crashes.
14. The system of claim 10 , wherein the transaction status is a monetary transaction determined to be incomplete based on a lack of a subsequent completion event, wherein the second transaction attribute comprises a monetary amount associated with a set of one or more items determined to be abandoned in association with the first set of the crashes.
15. The system of claim 10 , wherein the graphical user interface is configured to present the list of crash types in association with, for each of the crash types, a corresponding one of a set of a first transaction attributes including the first transaction attribute.
16. The system of claim 10 , wherein the graphical user interface is configured to present the list of crash types as a list of trending crash types comprising a list of most frequent crashes over a particular duration of time.
17. One or more computer-storage media storing computer-executable instructions that, when executed by a computing device, perform a method for crash monitoring, the method comprising:
providing, at a developer device, a graphical user interface configured to present crash data associated with crashes of a mobile application on mobile devices, the crashes having occurred during user transactions conducted with the mobile application, wherein at least a portion of the crash data is usable for modifying the mobile application to reduce subsequent occurrences of an error, the crash data comprising:
a list of crash types of the crashes, wherein crash types within the list of crash types are ranked based on a determined monetary impact associated with each of the crash types;
a first transaction attribute associated with the crashes and generated by aggregating application data of the mobile application provided from the mobile devices; and
a second transaction attribute indicating a transaction status, of one or more of the user transactions, determined to correlate with a first set of the crashes.
18. The one or more computer-storage media of claim 17 , wherein the second transaction attribute indicates that the transaction status of a corresponding one of the one or more user transactions is an incomplete monetary transaction.
19. The one or more computer-storage media of claim 17 , wherein the list of crash types is associated with a set of the crashes determined to correspond with incomplete monetary transactions, the incomplete monetary transactions identified based on a detected event indicating initiation of a monetary transaction and a detected lack of a subsequent event indicating completion of the monetary transaction within a corresponding session.
20. The one or more computer-storage media of claim 17 , wherein the graphical user interface is configured to present each of the crash types in association with (i) a corresponding graphical depiction of a trend over time of a number of occurrences of a corresponding set of the crashes of the crash type, and (ii) a monetary amount associated with a set of one or more items determined to be abandoned in association with the corresponding set of the crashes of the crash type.