Singular will track "auto-generated" events if an SDK or S2S integration is enabled. These auto-generated events may appear in user level event exports or certain partner postbacks (if the partner is receiving the auto-generated event name), or in Internal BI postbacks. The table below lists a few of these common auto-generated events, what the auto-generated event name is, and how they are triggered and tracked
| Event | Event Name | When it is Tracked |
| Install | __START__ | Automatically tracked when sessions are being sent via the SDK or S2S integration. |
| Session | __SESSION__ | Automatically tracked when sessions are being sent via the SDK or S2S integration. |
| SDK Revenue | __iap__ | Tracked if revenue is reported via the "revenue" method in the Singular iOS or Android SDK |
| Any Revenue | __REVENUE__ | Tracked if any revenue is tracked. For example, the __REVENUE__ event will trigger whenever revenue from the SDK via __iap__ is triggered, and also triggered if you are reporting revenue via S2S with an event name like "purchase". It not recommended to use this if __iap__ or other S2S revenue postbacks are configured for the same postback endpoint as duplicate revenue might be reported. |
| Uninstall | __UNINSTALL__ | Automatically tracked if uninstall is enabled for your iOS or Android app, and at least one uninstall has been tracked. If an uninstall is detected for a device, it is triggered once a day. |
| Reinstall | __REINSTALL__ | Automatically tracked if uninstall is enabled via the SDK/S2S. If an __UNINSTALL__ for a device is tracked, and then a subsequent __SESSION__ is triggered, the __REINSTALL__ event is also triggered |
