# Automatic signals

Source: https://pulse.mightys.dev/docs/automatic-signals/

Next to the signals you send, each SDK sends a few signals by itself, so you can count installs, updates, sessions and screens without writing code. This page lists all of them. They count toward your plan like any other signal.

## The signals

Signals the SDKs send by themselves:

| Signal | When it is sent | Properties | Uses signals | Default |
| --- | --- | --- | --- | --- |
| pulse.session_started | A new session began: the app started, or the first signal after 30 minutes without one. | None | One signal per session | On |
| pulse.new_install | The first launch after the app was installed. | None | One signal per install | On |
| pulse.app_updated | The first launch after the app version or build changed. | previousVersion, previousBuild | One signal per release | On |
| pulse.screen_view | A screen appeared. The same screen twice in a row is sent once. | screen, previousScreen | One signal per screen change | On |

Every automatic signal carries the same debug flag as your own signals, so test builds stay under Test mode. When a user opts out, nothing is sent.

## What each SDK does

One table per signal: when each SDK sends it.

pulse.session_started:

| pulse.session_started | When |
| --- | --- |
| Swift | Every app start and after 30 minutes without a signal. |
| Android (Kotlin) | Every app start and after 30 minutes without a signal. |
| Flutter | Every app start and after 30 minutes without a signal. |
| Unity | Every app start and after 30 minutes without a signal. |
| JavaScript | Node.js and native app wrappers. A normal browser does not send it. |
| .NET | The first signal of a run and after 30 minutes without one. |

pulse.new_install:

| pulse.new_install | When |
| --- | --- |
| Swift | Once, on the first launch. |
| Android (Kotlin) | Once, on the first launch. |
| Flutter | Once, on the first launch. |
| Unity | Once, on the first start. |
| JavaScript | Node.js and native app wrappers. A normal browser does not send it. |
| .NET | Once, in the first session. |

pulse.app_updated:

| pulse.app_updated | When |
| --- | --- |
| Swift | Once per new version or build. |
| Android (Kotlin) | Once per new version or build. |
| Flutter | Once per new version or build number. |
| Unity | Once per new version or build. |
| JavaScript | Node.js and native app wrappers. A normal browser does not send it. |
| .NET | Once per new version or build. |

pulse.screen_view:

| pulse.screen_view | When |
| --- | --- |
| Swift | By itself on UIKit (iOS, iPadOS, tvOS, Mac Catalyst): the view controller class name. |
| Android (Kotlin) | By itself: the class name of each Activity and visible AndroidX fragment. |
| Flutter | With one line: add Pulse.navigatorObserver to your navigator or router. |
| Unity | By itself: the name of the active scene when it changes. |
| JavaScript | By itself in a browser and in native app wrappers: the route path, with numbers and ids replaced by :id. |
| .NET | When you call Pulse.Screen("Name"), or by itself through a platform integration. |

## Switching them off

- In the portal: App settings can switch off screen views, all automatic signals, or one signal type. The change applies from the next launch of the app, with no package update.
- In code: the options below can only switch things off. Leaving them on follows the portal and never turns on what the portal switched off.
- When the SDK cannot read your settings (offline, an error, nothing saved yet), everything stays on.

Options that switch automatic signals off in code:

| SDK | Screen views | Sessions, installs and updates |
| --- | --- | --- |
| Swift | automaticScreenViews = false | automaticSignals = false |
| Android (Kotlin) | automaticScreenViews = false | automaticSignals = false |
| Flutter | automaticScreenViews = false | automaticSignals = false |
| Unity | AutomaticScreenViews = false | AutomaticSignals = false |
| JavaScript | automaticScreenViews = false | automaticSignals = false |
| .NET | PulseOptions.AutomaticScreenViews = false | PulseOptions.AutomaticSignals = false |

[How Test mode works](https://pulse.mightys.dev/docs/test-mode/)
