--- metadata: - name: generator content: Diplodoc Platform v5.66.1 alternate: - https://appmetrica.yandex.by/docs/en/data-collection/basic-events.md - https://appmetrica.yandex.by/docs/ru/data-collection/basic-events.md - https://appmetrica.yandex.by/docs/zh/data-collection/basic-events.md - href: https://appmetrica.yandex.by/docs/en/data-collection/basic-events.md type: text/markdown title: Markdown version - href: https://appmetrica.yandex.by/docs/en/llms.txt?revision=r22076204 rel: describedby --- > **Documentation Index:** Fetch the complete configuration index at https://appmetrica.yandex.by/docs/en/llms.txt?revision=r22076204 # Basic events {% note info %} Basic events are free and unlimited. Their number is not limited, and they don't consume the limit of custom events. [Learn more about plans](https://appmetrica.yandex.by/docs/en/common/pricing/ru-currency.md). {% endnote %} Basic events are a standard set of AppMetrica events. They have data transfer methods and built-in reports. Basic events don't consume the quota of custom events. Some basic data is collected by the SDK automatically after integration. For the rest, the developer needs to configure the transfer. Automatic collection capabilities depend on the platform, the version of the connected analytics library, and its settings. ## What events are collected automatically {#auto-collection} #| || **Events** | **What they record** | **Collection specifics** || || Installs | First launch of the app with analytics connected | After connecting analytics, the first launch is recorded automatically. || || Sessions | App visits | App visits are collected automatically. The rules for splitting visits into sessions are set in the settings. || || Deeplink openings | Opening the app via a link | Link transitions can be collected automatically. Links opened inside a running app require additional setup. || || [Crashes](https://appmetrica.yandex.by/docs/en/data-collection/about-crashes-and-errors.md) | Abnormal app terminations | To get a clear description of a crash, the developer may need to upload additional files. || || Push tokens | Device identifiers in push notification delivery systems | Working with notifications requires the appropriate integration. || || [In-App purchases and subscriptions](https://appmetrica.yandex.by/docs/en/data-collection/about-revenue.md) | Purchases and subscription status changes | The developer configures the collection of purchases and subscription changes taking into account the app store. || |# ## What events need to be configured {#configurable-collection} #| || **Events** | **What is transferred** | **How to configure** || || [Ecommerce](https://appmetrica.yandex.by/docs/en/data-collection/about-ecommerce.md) | Actions with products, cart, and orders | Describe the actions and give the developer a task to collect them || || [Product Flow](https://appmetrica.yandex.by/docs/en/data-collection/offers.md) | Offer display, checkout start, steps, and result | Describe the scenario stages and ask the developer to transfer them || || [Ad Revenue](https://appmetrica.yandex.by/docs/en/data-collection/about-adrevenue.md) | Revenue from each ad impression | Ask the developer to connect ad revenue data || || [In-App Revenue](https://appmetrica.yandex.by/docs/en/data-collection/about-revenue.md) | Purchase events sent manually | Ask the developer to collect purchases; for subscriptions, additionally connect status change tracking || || [Errors](https://appmetrica.yandex.by/docs/en/data-collection/about-crashes-and-errors.md) | Custom messages about problems in the app | Describe important errors and give the developer a task to collect them || |# In addition to events, you can transfer [profile attributes](https://appmetrica.yandex.by/docs/en/data-collection/about-profiles.md) — user characteristics. They also don't consume the limit of custom events, but describe the user's state rather than a separate action. ## How to start collecting {#how-to-start} 1. Find the required data type in the table. 1. Check with the developer which events are already collected. 1. If additional setup is needed, open the instructions for the selected type and pass them to the developer. 1. Run a test scenario and check the data in the corresponding report. If there is no suitable basic type, use a [custom event](https://appmetrica.yandex.by/docs/en/data-collection/custom-events.md). Don't create a custom duplicate of data that is already collected without a separate task for such duplication. 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. {% cut "For the developer: automatic collection specifics" %} Download the instructions for the developer (TXT): {% file src="../../_assets/instructions/basic-developer-en.txt" name="basic-developer-en.txt" type="text/plain; charset=utf-8" %} #| || **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 about session setup: [Android](https://appmetrica.yandex.by/docs/en/sdk/android/analytics/android-listen.md), [iOS](https://appmetrica.yandex.by/docs/en/sdk/ios/analytics/ios-listen.md). || || 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.by/docs/en/data-collection/about-crashes-and-errors.md) | 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.by/docs/en/data-collection/about-revenue.md) | 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 || |# {% endcut %} If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible. Contact support Suggest an improvement for documentation