Skip to content
Docs menu: Automatic signals

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
SignalWhen it is sentPropertiesUses signalsDefault
pulse.session_startedA new session began: the app started, or the first signal after 30 minutes without one.NoneOne signal per sessionOn
pulse.new_installThe first launch after the app was installed.NoneOne signal per installOn
pulse.app_updatedThe first launch after the app version or build changed.previousVersion, previousBuildOne signal per releaseOn
pulse.screen_viewA screen appeared. The same screen twice in a row is sent once.screen, previousScreenOne signal per screen changeOn

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_startedWhen
SwiftEvery app start and after 30 minutes without a signal.
Android (Kotlin)Every app start and after 30 minutes without a signal.
FlutterEvery app start and after 30 minutes without a signal.
UnityEvery app start and after 30 minutes without a signal.
JavaScriptNode.js and native app wrappers. A normal browser does not send it.
.NETThe first signal of a run and after 30 minutes without one.
pulse.new_install
pulse.new_installWhen
SwiftOnce, on the first launch.
Android (Kotlin)Once, on the first launch.
FlutterOnce, on the first launch.
UnityOnce, on the first start.
JavaScriptNode.js and native app wrappers. A normal browser does not send it.
.NETOnce, in the first session.
pulse.app_updated
pulse.app_updatedWhen
SwiftOnce per new version or build.
Android (Kotlin)Once per new version or build.
FlutterOnce per new version or build number.
UnityOnce per new version or build.
JavaScriptNode.js and native app wrappers. A normal browser does not send it.
.NETOnce per new version or build.
pulse.screen_view
pulse.screen_viewWhen
SwiftBy 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.
FlutterWith one line: add Pulse.navigatorObserver to your navigator or router.
UnityBy itself: the name of the active scene when it changes.
JavaScriptBy itself in a browser and in native app wrappers: the route path, with numbers and ids replaced by :id.
.NETWhen 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
SDKScreen viewsSessions, installs and updates
SwiftautomaticScreenViews = falseautomaticSignals = false
Android (Kotlin)automaticScreenViews = falseautomaticSignals = false
FlutterautomaticScreenViews = falseautomaticSignals = false
UnityAutomaticScreenViews = falseAutomaticSignals = false
JavaScriptautomaticScreenViews = falseautomaticSignals = false
.NETPulseOptions.AutomaticScreenViews = falsePulseOptions.AutomaticSignals = false

How Test mode works