# For the developer: automatic collection specifics

Article: Basic events

Automatic collection depends on the platform and app settings. Ask the developer to check which events are already transferred and what needs to be connected additionally.

| Events | What they record | Collection specifics |
| --- | --- | --- |
| Installs | First launch of the app with the initialized AppMetrica SDK | Collected by the SDK automatically |
| Sessions | Period of user interaction with the app | Collected by the SDK. A return after the specified timeout starts a new session; the end of the current one is recorded when the next one starts. Learn more: [Android](https://appmetrica.yandex.ru/docs/en/sdk/android/analytics/android-listen), [iOS](https://appmetrica.yandex.ru/docs/en/sdk/ios/analytics/ios-listen) |
| Deeplink openings | Opening the app via a universal link or a custom URI scheme | Automatic tracking of openings is supported in Android and iOS SDK starting from version 4.0. Deeplinks handled in an already running app require additional setup |
| [Crashes](https://appmetrica.yandex.com/docs/en/data-collection/about-crashes-and-errors) | Abnormal app terminations | Collection is provided in the SDK. Readable logs may require mapping, SO, or dSYM files |
| Push tokens | Device identifiers in push notification delivery systems | Used when working with push notifications; receiving them depends on the configuration of the corresponding integration |
| [In-App purchases and subscriptions](https://appmetrica.yandex.com/docs/en/data-collection/about-revenue) | Purchases and subscription status changes | Automatic collection is available for supported store purchases. It and subscription status tracking are configured according to the platform instructions |