## Overview
---
Everything your customers do in your mobile application is recorded in the system in real time, queued and automatically sent in batches to Synerise. Information such as the source of the visit, the URL address they have visited, and the chain of actions that followed are saved in Synerise as events and their parameters.
The scope of information gathered about events is wide. Synerise collects predefined event parameters which can be extended according to the preferences and needs of the Synerise customers.
The basic information about the tracked events includes:
- **Action name** – an indicator of the activity type, such as `screen.view`
- **Label** – human-readable information about the activity, such as the page title. Must be at least one character.
This is a deprecated field. It's not saved in the database. so it can't be used in Decision Hub or Automation Hub.
- **Time** – the time when the event occurred
- **Customer identification** – an identifier of the customer who performed the activity
- **Parameters** – additional parameters, depending on the type of the event
Click here to see example of an event
Some events are predefined, meaning they have a fixed set of fields that must be sent. For example, a `product.view` event must include the product ID.
You can [enrich events with data from catalogs in Synerise](/docs/assets/events/adding-event-parameters#enriching-events-with-data-from-catalogs), for example, a product or service event where only an ID has been provided can be enriched with other details such as the description, image URL, and more.
## Queue and flushing
As a compromise between how quick events are sent and battery life, events are collected into batches and _queued_ for sending (_flushing_) after enough events are collected or too much time passes (_timeout_), according to SDK settings.
Since Android SDK 5.17.0 and iOS SDK 4.17.0, the default settings flush the queue immediately when a push event is added to it.
You can change the queue size, timeout, list of events which trigger flushing, and other event tracking settings as described in the ["Tracker" section of the "Settings" article](/developers/mobile-sdk/settings#tracker).
To flush the queue on demand, use the following methods:
| OS | Method |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| Android | [Tracker.flush()](/developers/mobile-sdk/method-reference/android/tracking#flush-events-from-tracker) |
| iOS | [flushEvents(completionHandler: (() -> Void)?)](/developers/mobile-sdk/method-reference/ios/tracking#flush-events-from-tracker) |
| React Native | [flushEvents(onSuccess: () => void)](/developers/mobile-sdk/method-reference/react-native/tracking#flush-events-from-tracker) |
| Flutter | [Synerise.tracker.flush()](/developers/mobile-sdk/method-reference/flutter/tracking#flush-events-from-tracker) |
## Events tracked automatically
---
### Auto-Tracking
Automatic tracking is available only for **Android SDK** and **iOS SDK**. Auto-tracking is not supported for applications built with **Jetpack Compose** and **SwiftUI**. These applications should use [declarative tracking](#declarative-tracking).
Auto-tracking allows you to monitor each type of the customer activity in your mobile application and it is enabled by default. Every interaction (such as click, view, swipe) with any element in the application can be sent as an event to Synerise together with a collection of details concerning the event, which are available in the overview on [the profile's card](/docs/crm/crm-profile). The frequency and the kind of the tracked events are customizable, as you can switch on tracking a particular types of interactions.
#### Configuration {id=auto-tracking-configuration}
Auto-tracking events is:
- Enabled by default for Android.
- Disabled by default for iOS.
Available modes for auto-tracking:
- `DISABLED` - Listeners are disabled (**default mode for iOS SDK**).
- `PLAIN` - Listeners are set to track screen-visits only.
- `FINE` - Listeners are attached to nearly everything that is clickable in your app, including screen visits that record the [visited screen event](#customer-visited-a-screen) (**default mode for Android SDK**).
You may configure auto-tracking with various options to customize your expected behavior and track events you want. See possible configuration options below:
1. It enables/disables auto-tracking.
2. It sets auto-tracking mode.
3. It is an array of classes that you want to exclude from auto-tracking.
4. It is an array of tag numbers for views that you want to exclude from auto-tracking.
#### Events from Auto-Tracking
| Action name | Description | Label | Additional information tracked |
|--------------------|-----------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| screen.view | This event is generated when any screen of a mobile app is displayed by a mobile app user. | Activity, Fragment names (for example, `ProductDetailsFragment`) | |
| screen.interaction | This event is generated every time a mobile app user interacts with any element of the application UI. | `viewText` or the name of control type (if not able to read a value) | Depending on the UI element type tracked, Synerise automatically reads and passes any values that are set depending on type, such as: time, date, position, progress, state, value, or if the element has been selected. |
Depending on the UI element type tracked, Synerise automatically reads and passes any values that are set depending on type, such as: time, date, position, progress, state, value, or if the element has been selected.
| Action name | Description | Activity class | Label |
|--------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------|
| screen.view | This event is generated when any screen of a mobile app is displayed by a mobile app user. | `UIViewController` | View controllers name (for example, MyApp.ProductDetailsViewController) |
| screen.interaction | This event is generated every time a mobile app user interacts with any element of the application UI. | `UIButton` `UISwitch` `UISegmentedControl` `UISlider` `UIStepper` `UIDatePicker` | `viewText` or name of control type (if not able to read value) |
### Events tracked internally
In addition to declarative event tracking and Auto-Tracking, many events are generated by the SDK and the Synerise infrastructure.
Read more about all [Synerise events](/docs/assets/events/event-reference/default-events)
#### Lifecycle events
Some events are automatically generated by the SDK or backend as a result of the profile's activity.
| Action name | Source | Description |
|--------------------|--------------------|------------------|
| client.applicationStarted | **SDK** | A user opened the mobile application. This event contains additional info such as operating system, device model, the sdk version etc. |
| client.applicationCrashed | **SDK** | Report about a mobile application crash, with additional data for troubleshooting. |
| click.errorReceiver | **SDK** | The event is called when the SDK cannot start an intent because there is no attached Activity (`ActivityNotFoundException`). |
| session.start | **BACKEND** | A user opened the mobile application and a session was opened. The session ends when 30 minutes pass since the last activity. |
| session.end | **BACKEND** | 30 minutes passed since the last activity and the session was closed. |
In the following example of a`client.applicationStarted` event, the highlighted data is added automatically:
{
"action": "client.applicationStarted",
"eventUUID": "9f9f81ce-fb3d-432d-8f88-a4ce20ac3c0d",
"label": "AppStarted",
"params": {
"deviceType": "SMARTPHONE", // SMARTPHONE or TABLET
"deviceId": "B36535BD-7C80-4D90-A941-26CD4DB7FA7C",
"osLanguage": "pl", // Language set in operating system
"appVersionCode": "8", // Build number of the mobile app
"systemPushConsent": "enabled", // System consent for push notifications
"source": "MOBILE_APP",
"networkType": "WIFI", // WIFI or CELL
"cellCountry": "--",
"deviceModel": "iPhone13,1", // Model of a device
"os": "ios", // iOS or Android
"applicationType": "UNKNOWN",
"deviceRooted": "false",
"applicationName": "SDK Sample App Swift",
"appVersion": "4.16.0", // Version of the mobile app
"cellCarrier": "--",
"origin": "APP_STARTED",
"deviceManufacturer": "Apple", // Manufacturer of a device
"sdkVersion": "4.16.0", // SDK version in the mobile app
"sdkPreviousVersion": "4.15.0", // SDK version previously installed in the mobile app
"sdkPluginVersion": "1.2.0", // SDK plugin version in the mobile app (in hybrid apps, for example built with Flutter)
"osVersion": "17.3.1", // OS version of a device
"deviceId": "B36535BD-7C80-4D90-A941-26CD4DB7FA7C",
"deviceResolution": "1080x2338", // Resolution of device screen
(...)
}
}
#### Profile events
Some events are automatically generated as a result of an action or interaction with the profile such as registration, authorizations, and more.
Check details of [profile's events](/docs/assets/events/event-reference/profiles).
| Action name | Source | Description |
|--------------------|--------------------|-----------------------------------------------------------------------------------------|
| client.anonymousLogin | **BACKEND** | An anonymous profile generated a new authentication token. |
| client.simpleAuthLogin | **BACKEND** | A user logged in with [Simple Profile Authentication](/developers/mobile-sdk/user-identification-and-authorization/simple-authentication) |
| client.register | **BACKEND** | A profile was registered successfully. This event is only generated for Registration-as-a-Service. |
| client.tryToLogInToInactiveAccount | **BACKEND** | A profile tried to log in to an inactive account. |
| client.login | **BACKEND** | A user logged in mobile application. This event is only generated for OAuth and Synerise Authentication (aka RaaS). |
| client.logout | **BACKEND** | A user logged out from the mobile application. By default, this event is generated only when you use Synerise Authentication (aka RaaS). |
| client.merge | **BACKEND** | Two or more profiles were merged into one. |
| profile.updated | **BACKEND** | A profile was updated. |
#### Push Notifications events
Some events are automatically generated as a result of an action or interaction of the profile with push notifications.
To ensure correct tracking of push notification events, you must [configure push notifications](/developers/mobile-sdk/configuring-push-notifications) first.
Check details of [push notification events](/docs/assets/events/event-reference/mobile-push).
| Action name | Source | Description |
|--------------------|--------------------|-----------------------------------------------------------------------------------------|
| push.view | **SDK** | A push notification was shown to the app user. |
| push.notView | **SDK** | A push notification was sent, but the device did not display it due to the `areNotificationsEnabled` setting on the device. This event is only generated for Android 7.0 or later. |
| push.click | **SDK** | A push notification was tapped. |
| push.button.click | **SDK** | **DEPRECATED** A button in a push notification was tapped. |
| push.openInApp | **SDK** | A push notification was tapped and the app was opened. This event is only generated for iOS. |
| push.dismiss | **SDK** | A push notification was dismissed. The event requires configuring [Notification Service Extension](/developers/mobile-sdk/configuring-push-notifications/ios#synerise-notification-service-extension) for full support. |
| push.imageTimeout | **SDK** | An image in a mobile push notification could not be loaded. |
| push.controlGroup | **BACKEND** | A mobile push notification was not sent because the recipient belongs to the control group. |
| push.send | **BACKEND** | A push notification was sent to a profile. |
| push.notSent | **BACKEND** | A push notification failed to be created by the backend. Usually occurs when notification encryption is enabled in your business profile, but your application did not generate a key pair. |
| push.capping | **BACKEND** | A push notification was not sent due to message limits set for this type of communication. |
| push.skipped | **BACKEND** | A push notification was not sent because Silence Hours were active. If the process of sending multiple messages overlaps with Silence Hours, sending is stopped in progress. |
| push.tokenUpdate | **BACKEND** | A Firebase registration token was updated in the Synerise system. |
| push.tokenDelete | **BACKEND** | A Firebase registration token was deleted when a backend tried to send a push notification. Usually occurs when it is a problem with user's token. |
| push.notRegistered | **BACKEND** | A push notification was not sent due to an invalid Firebase token. |
| push.invalidRegistrationId | **BACKEND** | A push notification was not sent due to an incorrectly assigned registrationId in Firebase. |
| push.mismatchSenderId | **BACKEND** | A push notification was not sent, because the Firebase project to which the profile was registered changed. |
In these events campaign data is always tracked. See specified part of `push.view` event below:
{
"action": "push.view",
"eventUUID": "eca5662f-ecfd-418a-af5c-e65ba10ca252",
"label": "Test Simple Push",
"params": {
"id": "ecf5678d-c137-44d1-964f-83bc8d15511e", // Campaign ID
"variantId": 11598412, // Variant ID of the campaign
"campaignTitle": "Test Simple Push", // Campaign title
"campaignType": "Mobile push", // Campaign type
(...)
}
}
#### In-App Messages events
Sort events are automatically generated as a result of an action or interaction with in-app messages by the user of the mobile app.
Read more about the details of [in-app messages events](/docs/assets/events/event-reference/inapp).
| Action name | Source | Description |
|--------------------|--------------------|-----------------------------------------------------------------------------------------|
| inApp.show | **SDK** | An in-app message was shown to the app user. |
| inApp.capping | **SDK** | An in-app message was not displayed due to [capping](/docs/campaign/in-app-messages/create-inapp-message#capping) or [frequency limits](/docs/campaign/in-app-messages/create-inapp-message#frequency). |
| inApp.click | **SDK** | The content of an in-app message was tapped. |
| inApp.controlGroup | **SDK** | An in-app message was not displayed because the recipient belongs to the control group. |
| inApp.discard | **SDK** | An in-app message was closed. |
| inApp.hide | **SDK** | An in-app message was hidden. |
| inApp.customHook | **SDK** | A custom action (implemented by your app developers and included in the in-app definition) from an in-app message was triggered. |
| inApp.renderFail | **SDK** / **BACKEND** | An in-app message was not displayed due to an error. This may be caused, for example, by an error in the Jinjava syntax or a connection problem. |
In these events campaign data is always tracked. See specified part of `inApp.show` event below:
{
"action": "inApp.show",
"eventUUID": "e982ed4d-9179-4bc3-9266-322ff4a8f2eb",
"label": "In-app message was displayed in mobile app",
"params": {
"id": "83e13e0b-7930-4866-a2cf-088dcbe0b222", // Campaign ID
"variantId": "c3bbfc16-a79e-474f-a255-ef7ee1333148", // Variant ID of the campaign
(...)
}
}
#### Other campaigns events
Other events are which automatically generated as a result of an action related to campaigns.
| Action name | Source | Description |
|--------------------|--------------------|-----------------------------------------------------------------------------------------|
| screen.content | **SDK** | A Screen View campaign was generated and fetched for the profile in the mobile app. It contains data with a sorted tree of the documents. |
| client.activatePromotion | **BACKEND** | A promotion was activated by the profile. |
| client.deactivatePromotion | **BACKEND** | A promotion was deactivated by the profile. |
| recommendation.generated | **BACKEND** | A recommendation set was generated for a profile. |
| recommendation.view | **SDK** | A recommendation frame was displayed to a user. The parameters may include a list of the items in the frame, depending on your implementation. Event from Content Widget. |
| recommendation.seen | **SDK** | A recommendation frame was displayed to a user. The parameters may include a list of the items in the frame, depending on your implementation. Event from Content Widget. |
| recommendation.click | **SDK** | A recommended item was clicked. Event from Content Widget. |
| product.like | **SDK** | The Content Widget includes a "like" button that was tapped by the user. |
| product.dislike | **SDK** | The Content Widget includes a "dislike" button that was tapped by the user. |
## Declarative tracking
---
Declarative tracking is a feature of our SDK that allows you to declare additional actions for tracking.
Product views, screen views, clicking a sign up button, contact with the call center, and more: you can implement anything and declarative tracking will help you to do that.
DO NOT send `transaction.charge` events as custom events.
Transactions must be tracked with these endpoints:
- [`/v4/transactions`](https://developers.synerise.com/DataManagement/DataManagement.html#operation/CreateATransaction) (single transaction)
- [`/v4/transactions/batch`](https://developers.synerise.com/DataManagement/DataManagement.html#operation/BatchAddOrUpdateTransactions) (multiple transactions)
### Basic custom event
In the most basic scenario, you can pass an event as in the examples below:
Such events are passed to Synerise as the `CustomEvent` type, since the `action` can be anything that you want.
- The action name must follow the `context.action` convention. For example: `screen.view`, `product.buy`, `social.share`
- The action name must be up to 32 characters long and must match the following regular expression:
```
^[a-zA-Z0-9\.\-_]+$
```
### Custom events with more parameters
If you want to send more complex events, you can include additional parameters:
The following keys are reserved and you can't send them: **modifiedBy**, **apiKey**, **eventUUID**, **ip**, **time**, **businessProfileId**. If you add them to an event, they are ignored.
### Predefined events
Synerise offers a set of predefined event types that require a minimum set of data for the backend.
They can be sent by using Setters as in the following example. The example uses the [Product viewed](#product-viewed) event.
| **Android** | **iOS** | **React Native** | **Flutter** |
| --------------- | ----------------- | ----------------------- | ----------------------- |
| [Tracker.send(event)](/developers/mobile-sdk/method-reference/android/tracking#send-event) method | [Tracker.send(_:)](/developers/mobile-sdk/method-reference/ios/tracking#send-event) method | [Synerise.Tracker.send(event)](/developers/mobile-sdk/method-reference/react-native/tracking#send-event) method | [Synerise.tracker.send(event)](/developers/mobile-sdk/method-reference/flutter/tracking#send-event) method |
## Predefined event list
---
The list contains the list of predefined events which you can implement.
### Customer registered
---
This event may be used if you do not use [Synerise registration/authentication](/developers/mobile-sdk/user-identification-and-authorization/overview) features and rely fully on your own mechanisms, but still want to gather events when a customer registers.
**Action name of the generated event**: client.register
**Example**:
```Java
RegisteredEvent event = new RegisteredEvent("label")
Tracker.send(event);
```
```Kotlin
val event = RegisteredEvent("label")
Tracker.send(event)
```
```Swift
let event: RegisteredEvent = RegisteredEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|----------------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [RegisteredEvent](/developers/mobile-sdk/class-reference/android/events#registeredevent) | Label |
| iOS | [RegisteredEvent](/developers/mobile-sdk/class-reference/ios/events#registeredevent) | Label |
| React Native | [RegisteredEvent](/developers/mobile-sdk/class-reference/react-native/events#registeredevent) | Label |
| Flutter | [RegisteredEvent](/developers/mobile-sdk/class-reference/flutter/events#registeredevent) | Label |
### Customer logged in event
---
This event may be used if you do not use [Synerise login/authentication](/developers/mobile-sdk/user-identification-and-authorization/overview) features and rely fully on your own mechanisms, but still want to gather events when a customer logs in.
**Action name of the generated event**: client.login
Logged in event
**Example**:
```Java
LoggedInEvent event = new LoggedInEvent("label")
Tracker.send(event);
```
```Kotlin
val event = LoggedInEvent("label")
Tracker.send(event)
```
```Swift
let event: LoggedInEvent = LoggedInEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|-------------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [LoggedInEvent](/developers/mobile-sdk/class-reference/android/events#loggedinevent) | Label |
| iOS | [LoggedInEvent](/developers/mobile-sdk/class-reference/ios/events#loggedinevent) | Label |
| React Native | [LoggedInEvent](/developers/mobile-sdk/class-reference/react-native/events#loggedinevent) | Label |
| Flutter | [LoggedInEvent](/developers/mobile-sdk/class-reference/flutter/events#loggedinevent) | Label |
### Customer logged out
---
This event may be used if you do not use [Synerise login/authentication](/developers/mobile-sdk/user-identification-and-authorization/overview) features and rely fully on your own mechanisms, but still want to gather events when a customer logs out.
**Action name of the generated event**: client.logout
**Example**:
```Java
LoggedOutEvent event = new LoggedOutEvent("label")
Tracker.send(event);
```
```Kotlin
val event = LoggedOutEvent("label")
Tracker.send(event)
```
```Swift
let event: LoggedOutEvent = LoggedOutEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|---------------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [LoggedOutEvent](/developers/mobile-sdk/class-reference/android/events#loggedoutevent) | Label |
| iOS | [LoggedOutEvent](/developers/mobile-sdk/class-reference/ios/events#loggedoutevent) | Label |
| React Native | [LoggedOutEvent](/developers/mobile-sdk/class-reference/react-native/events#loggedoutevent) | Label |
| Flutter | [LoggedOutEvent](/developers/mobile-sdk/class-reference/flutter/events#loggedoutevent) | Label |
### Product viewed
---
Use this event to track customer visits to a product in your mobile application.
**Action name of the generated event**: product.view
Event sent when the mobile app user sees an item
**Example**:
```Java
ProductViewEvent event = new ProductViewEvent("label", "productId", "productName");
Tracker.send(event);
```
```Kotlin
val event = ProductViewEvent("label", "productId", "productName")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|-------------------------------------------------------------------------------------------------------------------------|------------------------|
| Android | [ProductViewEvent](/developers/mobile-sdk/class-reference/android/events#productviewevent) | Label, ProductId, Name |
| iOS | [ProductViewedEvent](/developers/mobile-sdk/class-reference/ios/events#productviewedevent) | Label, ProductId, Name |
| React Native | [ProductViewedEvent](/developers/mobile-sdk/class-reference/react-native/events#productviewedevent) | Label, ProductId, Name |
| Flutter | [ProductViewedEvent](/developers/mobile-sdk/class-reference/flutter/events#productviewedevent) | Label, ProductId, Name |
### Product added to favorites
---
Use this event to track adding a product to favorites in your mobile application.
**Action name of the generated event**: product.addToFavorite
Event sent when a mobile app user adds an item to favorites
**Example**:
```Java
AddedToFavoritesEvent event = new AddedToFavoritesEvent("label");
Tracker.send(event);
```
```Kotlin
val event = AddedToFavoritesEvent("label")
Tracker.send(event)
```
```Swift
let event: ProductAddedToFavoritesEvent = ProductAddedToFavoritesEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|
| Android | [AddedToFavoritesEvent](/developers/mobile-sdk/class-reference/android/events#addedtofavoritesevent) | Label |
| iOS | [ProductAddedToFavoritesEvent](/developers/mobile-sdk/class-reference/ios/events#productremovedfromcartevent) | Label |
| React Native | [ProductAddedToFavouritesEvent](/developers/mobile-sdk/class-reference/react-native/events#productaddedtofavoritesevent) | Label |
| Flutter | [ProductAddedToFavouritesEvent](/developers/mobile-sdk/class-reference/flutter/events#productaddedtofavoritesevent) | Label |
### Product added to cart
---
Use this event to track adding a product to a cart in your mobile application.
**Action name of the generated event**: product.addToCart
Event sent when a mobile app user adds an item to cart
**Example**:
```Java
UnitPrice unitPrice = new UnitPrice(price, Currency.getInstance(Locale.US));
AddedToCartEvent event = new AddedToCartEvent("label", "sku", unitPrice, 1);
Tracker.send(event);
```
```Kotlin
val unitPrice = UnitPrice(price, Currency.getInstance(Locale.US))
val event = AddedToCartEvent("label", "sku", unitPrice, 1)
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|
| Android | [RemovedFromCartEvent](/developers/mobile-sdk/class-reference/android/events#removedfromcartevent) | Label, Sku, FinalPrice, Quantity |
| iOS | [ProductRemovedFromCartEvent](/developers/mobile-sdk/class-reference/ios/events#productremovedfromcartevent) | Label, SKU, FinalPrice, Quantity |
| React Native | [ProductRemovedFromCartEvent](/developers/mobile-sdk/class-reference/react-native/events#productremovedfromcartevent) | Label, SKU, FinalPrice, Quantity |
| Flutter | [ProductRemovedFromCartEvent](/developers/mobile-sdk/class-reference/flutter/events#productremovedfromcartevent) | Label, SKU, FinalPrice, Quantity |
### Recommendation viewed
Use this event to track when a recommendation is displayed to a customer.
**Action name of the generated event**: recommendation.view
**For iOS and Android only**: If you use the [Widget](/developers/mobile-sdk/displaying-recommendations/content-widget/android) to present recommendations, this event is tracked automatically.
**Example**:
```Java
List items = Arrays.asList("PRODUCT_ID_1", "PRODUCT_ID_2!");
RecommendationViewEvent event = new RecommendationViewEvent("LABEL", items, "12345", "1234", "corr", params)
Tracker.send(event)
```
```Kotlin
val items = listOf("PRODUCT_ID_1", "PRODUCT_ID_2")
val event = RecommendationViewEvent("LABEL", items, "12345", "1234", "corr", params)
Tracker.send(event)
```
This is a legacy event. You should use [recommendation.view](#recommendation-viewed) instead.
Use this event to track recommendation display to a customer.
**Action name of the generated event**: recommendation.seen
**For iOS and Android only**: If you use the [Widget](/developers/mobile-sdk/displaying-recommendations/content-widget/android) to present recommendations, this event is tracked automatically.
**Example**:
| OS | Event | Required fields |
|--------------|---------------------------------------------------------------------------------------------------------------------------------------| --- |
| Android | [RecommendationClickEvent](/developers/mobile-sdk/class-reference/android/events#recommendationclickevent) | Label, ProductId,Name, CampaignId, CampaignHash |
| iOS | [RecommendationClickEvent](/developers/mobile-sdk/class-reference/ios/events#recommendationclickevent) | Label, ProductId, Name, CampaignId, CampaignHash |
| React Native | [RecommendationClickEvent](/developers/mobile-sdk/class-reference/react-native/events#recommendationclickevent) | Label, ProductId, Name, CampaignId, CampaignHash |
| Flutter | [RecommendationClickEvent](/developers/mobile-sdk/class-reference/flutter/events#recommendationclickevent) | Label, ProductId, Name, CampaignId, CampaignHash |
### Customer appeared in location
---
Use this event to track a customer's presence at a location by passing geographic coordinates.
1. Send a [silent push](/developers/mobile-sdk/campaigns/silent-push) with the Synerise command `GET_LOCATION`.
2. SDK retrieves the location.
3. Use the data from the `GET_LOCATION` response to send the `AppearedInLocation` event.
**Action name of the generated event**: client.location
The "appeared in location" event is sent after a silent push
**Example**:
```Java
AppearedInLocationEvent event = new AppearedInLocationEvent("label", 48.1599, 11.5761);
Tracker.send(event);
```
```Kotlin
val event = AppearedInLocationEvent("label", 48.1599, 11.5761)
Tracker.send(event)
```
```Swift
let latitude: CLLocationDegrees = CLLocationDegrees(52.237049)
let longitude: CLLocationDegrees = CLLocationDegrees(21.017532)
let location: CLLocation = CLLocation(latitude: latitude, longitude: longitude)
let event: AppearedInLocationEvent = AppearedInLocationEvent(label: "LABEL", location: location)
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|----------------------------------------------------------------------------------------------------------------- |----------------------------|
| Android | [AppearedInLocationEvent](/developers/mobile-sdk/class-reference/android/events#appearedinlocationevent) | Label, Latitude, Longitude |
| iOS | [AppearedInLocationEvent](/developers/mobile-sdk/class-reference/ios/events#appearedinlocationevent) | Label, Latitude, Longitude |
| React Native | [AppearedInLocationEvent](/developers/mobile-sdk/class-reference/react-native/events#appearedinlocationevent) | Label, Latitude, Longitude |
| Flutter | [AppearedInLocationEvent](/developers/mobile-sdk/class-reference/flutter/events#appearedinlocationevent) | Label, Latitude, Longitude |
### Customer activity timer
---
Use this event to measure the duration of any customer activity - send Hit timer when a customer starts an activity and send it again with a different time signature when the customer finishes. After that, you can use the [Decision Hub](/docs/analytics) to measure, for example, average activity time. You can add a custom parameter to the timer events so you can recognize them.
**Action name of the generated event**: client.hitTimer
**Example**:
```Java
HitTimerEvent event = new HitTimerEvent("label");
Tracker.send(event);
```
```Kotlin
val event = HitTimerEvent("label")
Tracker.send(event)
```
```Swift
let event: HitTimerEvent = HitTimerEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|-------------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [HitTimerEvent](/developers/mobile-sdk/class-reference/android/events#hittimerevent) | Label |
| iOS | [HitTimerEvent](/developers/mobile-sdk/class-reference/ios/events#hittimerevent) | Label |
| React Native | [HitTimerEvent](/developers/mobile-sdk/class-reference/react-native/events#hittimerevent) | Label |
| Flutter | [HitTimerEvent](/developers/mobile-sdk/class-reference/flutter/events#hittimerevent) | Label |
### Customer searched
---
Use this event to track search queries - every time a customer types a query in the search box in your mobile application, this event will be generated.
**Action name of the generated event**: client.search
**Example**:
```Java
SearchedEvent event = new SearchedEvent("label");
Tracker.send(event);
```
```Kotlin
val event = SearchedEvent("label")
Tracker.send(event)
```
```Swift
let event: SearchedEvent = SearchedEvent(label: "LABEL")
Tracker.send(event)
```
```JavaScript
var object: Object = {
sharedEvents: '5',
field: 'test',
}
let event = new SharedEvent('Shared Event Label', object)
Synerise.Tracker.send(event)
```
```Dart
SharedEvent event = new SharedEvent('label',{});
Synerise.tracker.send(event);
```
| OS | Event | Required fields |
|--------------|--------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [SharedEvent](/developers/mobile-sdk/class-reference/android/events#sharedevent) | Label |
| iOS | [SharedEvent](/developers/mobile-sdk/class-reference/ios/events#sharedevent) | Label |
| React Native | [SharedEvent](/developers/mobile-sdk/class-reference/react-native/events#sharedevent) | Label |
| Flutter | [SharedEvent](/developers/mobile-sdk/class-reference/flutter/events#sharedevent) | Label |
### Customer visited a screen
---
This event is used when a customer visits a particular screen in your application.
**Action name of the generated event**: screen.view
Event sent when a mobile app user visits a screen
**Example**:
```Java
VisitedScreenEvent event = new VisitedScreenEvent("label");
Tracker.send(event);
```
```Kotlin
val event = VisitedScreenEvent("label")
Tracker.send(event)
```
```Swift
let event: VisitedScreenEvent = VisitedScreenEvent(label: "LABEL")
Tracker.send(event)
```
| OS | Event | Required fields |
|--------------|----------------------------------------------------------------------------------------------------------------------|-----------------|
| Android | [VisitedScreenEvent](/developers/mobile-sdk/class-reference/android/events#visitedscreenevent) | Label |
| iOS | [VisitedScreenEvent](/developers/mobile-sdk/class-reference/ios/events#visitedscreenevent) | Label |
| React Native | [VisitedScreenEvent](/developers/mobile-sdk/class-reference/react-native/events#visitedscreenevent) | Label |
| Flutter | [VisitedScreenEvent](/developers/mobile-sdk/class-reference/flutter/events#visitedscreenevent) | Label |
### Crash Event
---
This event is used when the application crashes.
The event is sent automatically by **Synerise SDK** when you enable [crash handling](/developers/mobile-sdk/miscellaneous#crash-handling) while configuring the SDK.
You can send it by yourself when you handle an uncaught exception.
**Action name of the generated event**: client.applicationCrashed
**Example**:
Push events are tracked automatically for Android and React Native (if the notifications have been configured for React Native according to [iOS](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-ios) or [Android](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-android) ).
**Action name of the generated event**: push.view
```Swift
let event: PushViewedEvent = PushViewedEvent(label: "LABEL")
Tracker.send(event)
```
Push events are tracked automatically for Android and React Native (if the notifications have been configured for React Native according to [iOS](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-ios) or [Android](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-android) ).
**Action name of the generated event**: push.click
```Swift
let event: PushClickedEvent = PushClickedEvent(label: "LABEL")
Tracker.send(event)
```
Push events are tracked automatically for Android and React Native (if the notifications have been configured for React Native according to [iOS](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-ios) or [Android](/developers/mobile-sdk/configuring-push-notifications/react-native#setting-up-android) ).
**Action name of the generated event**: push.dismiss
```Swift
let event: PushCancelledEvent = PushCancelledEvent(label: "LABEL")
Tracker.send(event)
```
