LogoLogo
WebsiteBlog
  • Introduction
  • CDP Overview
  • Identity Resolution
  • CDP Guidelines for Data Sanity and Campaign Governance
  • Login and User Management
    • Login to the platform
    • Change Password / Retrieve your Account
    • Role Based Access Control
      • User Management
      • Roles
    • Single Sign-On (SSO)
  • Events
    • Events Overview
    • App Events
    • Track
    • Identify
    • Page
    • Screen
    • Event Dictionary
  • Sources
    • Sources Overview
    • Android SDK
    • iOS SDK
    • JavaScript SDK
    • React Native SDK
    • Flutter SDK
    • REST API
    • Adobe Analytics Exports
    • SFTP
    • Kafka
    • Offline File Ingestion
  • Destinations
    • Destinations Overview
    • Quora Pixel
    • Hotjar
    • Clevertap
    • Google Analytics 4 (GA4)
    • Meta Pixel
    • Meta Conversion API
    • LinkedIn Insight Tag
    • Adobe Target
    • AppsFlyer
    • AWS S3
    • Criteo
    • Kafka
  • Integrations
    • Rudderstack
    • Azure Blob
    • Adobe Launch Private Extension
    • Adobe Launch Extension
    • Salesforce CRM
    • Microsoft Dynamics 365
  • Customer One View
    • Introduction
    • Basic details, Attributes and Devices
    • Segment and Engagement
    • Activity
  • Segments
    • Getting Started
    • Create a Segment
  • Channels
    • Getting Started
    • A/B Testing
    • SMS
      • Set up an SSP
        • Netcore
        • Twilio
        • Adobe Campaign Classic
        • Gupshup
        • Unifonic
        • Infobip
        • Tubelight
      • Add an SSP
      • Create SMS campaign
      • FAQs
    • Email
      • Set up an ESP
        • SendGrid
        • SendInBlue
        • SparkPost
        • Taximail
        • Netcore
        • Adobe Campaign Classic
        • Mailchimp
        • Oracle Email Delivery
        • Infobip
        • Vision6
      • 🆕Add an ESP
      • Create Email campaign
      • Common use cases with Email Editor
      • Why Email Notification may not get delivered?
      • FAQs
    • App Push Notification
      • Create App Push Notification - Android
      • Create App Push Notification - iOS
      • Why App Push Notification may not get delivered?
      • FAQs
    • WhatsApp
      • Configure a WSP
        • Yellow Messenger
        • Infobip
        • Gupshup
        • BIK.ai
        • Vonage
        • Sinch
        • Tubelight
      • Create WhatsApp campaign
      • FAQs
    • RCS
      • Add an RCS API
      • Example: Netcore RCS API
      • Create an RCS campaign
      • FAQs
    • Web Push Notification
      • Create a Web Push Notification
      • Create a Default Web Push Notification
      • FAQs
    • On-site Notification
      • Create On-site Notifications.
      • Common use cases with On-site Notification.
      • Notification Templates
    • Banner Personalization
      • Create a Personalized Banner
      • Create a Default Banner
    • External API
      • Create Engagement
      • Test your API configuration
      • Example Use Cases of External APIs
        • Use case 1: HubSpot - Create Contacts API
        • Use case 2: Exotel's Make a call API
        • Use case 3: Mailmodo's Send Campaign Email API
  • Ramanujan AI
    • Lead scoring
    • Channel Orchestration
    • Content Generator
      • Generate Web Push Content
  • Journey Builder
    • Overview- Journey Builder
    • View all Journeys
    • Create a Journey
    • Journey Reports
    • FAQs
  • Audience Export
    • Facebook Export Channel
    • Google Ads Export Channel
  • Analytics
    • Dashboard
      • Guiding through the Dashboard
      • Unique Profile
      • Profile and Merge Trends
      • Campaign and Revenue Dashboard
    • Campaign Summary
    • Events Occurrence
    • Event Telemetry
    • App Installs and Uninstalls
    • Funnels
    • Paths
    • Traffic Analysis
    • Cohorts
    • Data sanity between Funnels, Paths and Events
    • FAQs
  • Developer APIs
    • User Profile API
    • WhatsApp Opt-in/Opt-out API
    • Subscription Management
  • Settings
    • Product Label
    • Frequency Caps
    • Contacts
Powered by GitBook
On this page
  • Events
  • Application Installed
  • Application Opened
  • Application Updated
  • Application Backgrounded
  • Application Uninstalled
  • Application Crashed
  • Application Session Started
  • Application Session Concluded
  1. Events

App Events

These events are app-related events and can be used as normal events for segmentation purposes. Some of the events are automatically fired while some events may require manual firing.

Events

Application Installed

This event is automatically fired when the user installs an application.

NO

Application Opened

This event is automatically fired when the user opens an application.

NO

Application Updated

This event is automatically fired when the application gets updated.

NO

Application Backgrounded

This event should be sent when a user backgrounds the application.

YES - for iOS NO - for Android

Application Crashed

This event should be sent when you receive a crash notification from your app.

YES

Application Uninstalled

This event should be sent when you receive a user uninstalls the application.

YES

Application Session Started

This event is automatically fired when a user spends over 10 seconds on the app.

NO

Application Session Concluded

This event is automatically fired when a user is inactive for 20 minutes on the app.

NO

Application Installed

This event is automatically fired when the user installs an application.

Properties:

Property

Type

Description

userId

String

Unique ID of the user

type

String

Type of event (track in this case)

event

String

Name of the event

properties

Object

Additional properties related to the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Installed",
  "properties": {
    "version": "1.2.3",
    "build": "1234"
  }
}

properties definition:

Property

Type

Description

version

String

The version installed.

build

String

The build number of the installed app.

Application Opened

This event is automatically fired when the user opens an application.

Properties:

Property

Type

Description

userId

String

Unique ID of the user

type

String

Type of event (track in this case)

event

String

Name of the event

properties

Object

Additional properties related to the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Opened",
  "properties": {
    "from_background": false,
    "referring_application": "GMail",
    "url": "url://location"
  }
}

properties definition:

Property

Type

Description

from_background

String

referring_application

String

The value of UIApplicationLaunchOptionsSourceApplicationKey from launchOptions. Automatically collected on iOS only.

url

String

The value of UIApplicationLaunchOptionsURLKey from launchOptions.Collected on iOS only.

version

String

The version installed.

build

String

The build number of the installed app.

Application Updated

This event is automatically fired when the application gets updated.

Properties:

Property

Type

Description

userId

String

Unique ID of the user

type

String

Type of the event (track in this case)

event

String

Name of the event

properties

Object

Additional properties of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Updated",
  "properties": {
    "previous_version": "1.1.2",
    "previous_build": "1234",
    "version": "1.2.0",
    "build": "1456"
  }
}

properties definition:

Property

Type

Description

previous_version

String

The previously recorded version.

previous_build

String

The previously recorded build.

version

String

The new version.

build

String

The new build.

Application Backgrounded

This event should be sent when a user backgrounds the application.

Properties:

Property

Type

Description

userId*

String

Unique ID of the user

type*

String

Type of the event (track in this case)

event*

String

Name of the event

properties

Object

Additional properties of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Backgrounded",
  "properties": {} //add any properties you like
}

Application Uninstalled

Fire this event when a user uninstalls the application.

Properties:

Property

Type

Description

userId*

String

Unique ID of the user

type*

String

Type of the event (track in this case)

event*

String

Name of the event

properties

Object

Additional properties of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Uninstalled",
  "properties": {} //add any properties you like
}

Application Crashed

Fire this event when you receive a crash notification from your app.

Properties:

Property

Type

Description

userId*

String

Unique ID of the user

type*

String

Type of the event (track in this case)

event*

String

Name of the event

properties

Object

Additional properties of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Crashed",
  "properties": {} //add any properties you like
}

Application Session Started

This event is automatically fired when a user spends over 10 seconds on the app to mark an active session.

Property
Type
Description

userId*

String

Unique ID of the user

type*

String

Type of the event (track in this case)

event*

String

Name of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Session Started"
}

Application Session Concluded

This event is automatically fired when a user is inactive for 20 minutes on the app which ends the user session.

Once the app is put into the background, the user inactivity starts.

Case 1: When the app is closed and opened the next day

For example, the user opened the app at 11:00 AM on Tuesday and the following events happened in sequence:

Event 1 - 11:00 AM (Tuesday)

Event 2 - 11:05 AM (Tuesday)

Event 3 (Application backgrounded) - 11:06 AM (Tuesday)

Event 4 (Session Started) - 12:00 PM (Wednesday)

Session Length = Event 3 - Event 1 - Session concluded event should be fired at 12:00 PM (Wednesday)

Case 2: When the app is opened closed the same day

Event 1 - 11:00 AM (Tuesday)

Event 2 (Background) - 11:05 (Tuesday)

Event 3 - 11:30 (Tuesday)

Session length = 11:05 - 11:00 (5 minutes) - session concluded should be fired at 11:30 (Event 3)

Property
Type
Description

userId*

String

Unique ID of the user

type*

String

Type of the event (track in this case)

event*

String

Name of the event

properties

Object

Additional properties of the event

Example:

{
  "userId": "019mr8mf4r",
  "type": "track",
  "event": "Application Session Concluded",
  "properties": {
    "length": "45000",
    "sessionId": "f92j2tj",
    "lastEventTimestamp": "1638458316949" 
  }
}

properties definition:

length

String

Total session length in seconds right from first event was recorded

sessionId

String

Unique ID to identify the session

lastEventTimestamp

String

The timestamp of the last event that was recorded before inactivity

PreviousEvents OverviewNextTrack

Last updated 1 year ago

If application from “Background” to “Inactive” state prior to foregrounding (as opposed to from “Not Running” state).

transitioned