Mobile Push and In-App Messages
Mobile audience profiling

Mobile Audience Profiling

Core Concepts

Mobile application profiling is an important part of your customer engagement. Each connected app install can be personalized to a particular customer, assigned additional customer preferences, and used to track customer behavior.

Mobile customer profile is synced with the Infobip Target (People) module and forms a unified profile of a single customer across devices, platforms, and available channels. With mobile audience profiling, you can reach out to your customers in the right moment with relevant content which drives your audience engagement.

Each application install on a device receives unique install ID - pushRegistrationId.

pushRegistrationIdis a permanent ID assigned to the app once it’s launched up until the moment it’s uninstalled from the device. Each installation has default attributes (device model, OS, app version, etc.) although you can define additional custom attributes.

To target a specific customer with a personalized message, you need to go through the identified Person. Such process is called identified Person. Identified Person is a profile in Target module (People) which has at least one unique identity: externalUserID, phone number, email.

Personalized profile (identified Person) can have several devices connected to it. Data can be shared across devices as well. For example, you can set a subscription on your mobile device and it will be synced on your tablet. For security reasons, you can enable the option which shows all connected devices right in the customers mobile application.

Mobile customer profile

Profiling Phases

Here’s how the profiling process looks like:

Install – Anonymous > Personalized > Depersonalized > Uninstall

The diagram below shows the application lifecycle overview on the Infobip platform.

Profiling phases flow

Personalization

In case your application supports login functionality and/or you want your users to receive notifications targeted by any person attribute, you need to personalize the installation.

Each person can have phone numbers, emails, and/or external user ID, the fields that uniquely identify a person on the Infobip web interface and provide the capability to personalize any application registration with a person profile.

Personalization of mobile applications can be performed through:

When personalizing the Install, keep in mind that personalized profile can have several devices linked to it, but single device can be linked to a single profile only.

Updating Person Attributes

After the Install is personalized you can update standard and custom person attributes in Target module with your mobile application:

Synced attributes will be available for your audience Segmentation.

NOTE

While updating standard attributes: phone numbers, emails, and externalUserId, Infobip web interface automatically adds uniqueness of these attributes to prevent unintentional merge of profiles.

Depersonalization

In case your application supports the logout functionality, you need to depersonalize the install when the user is logged out which will prevent the user from receiving notifications targeted with any person attribute.

Depersonalization can be done with:

Application Install Default System Data and Standard Attributes

Installation system data

NameTypeDescription
pushRegistrationIdstringUnique ID which identifies application instance and specific device.
platformstringPossible values are Android or iOS.
sdkVersionstring

SDK Version which can be found on GitHub:
Mobile SDK iOS releases

Mobile SDK Android releasesMobile SDK Huawei releasesReleases of plugins for:React NativeFlutterCordova
osVersionstringOS Version.
deviceManufacturerstring

Device manufacturer:
iOS - Apple
Android - Samsung, Asus, etc.
For a particular subscriber value, refer to People.

deviceModelstring

Device model, for example, iPhone 12, iPhone 13
For particular subscriber details, refer to People & List of iOS models

applicationVersionstringApplication version
pushRegistrationEnabledbooleanWhether push notifications are enabled on the device. Set to true to only target users who have push registration enabled. For more details refer to iOS SDK Wiki and Android SDK Wiki.
registrationsEnabledbooleanSet to true to only target devices where notifications for the mobile application are turned on by the user.
geofencingEnabledbooleanIs the Geofencing SDK set and are tracking locations enabled by the user.
deviceSecurebooleanIs touch ID or passcode set for the device.
osLanguageStringSet language on a mobile device. Parameter can be overridden by application logic.
notificationsEnabledBooleanEnd user enabled push notifications on lock screen. OS permission.
appVersionStringApplication version installed on mobile device.

Installation standard attributes

PrimaryDevicebooleanTargets the user’s primary device in case the user has more than one device.Parameter management can be performed from the Mobile SDK:

Preferences and Subscriptions

Preferences and subscriptions are managed with Profile Custom attributes. Custom attributes are key-value pairs, where the value can be string, number, boolean or date types. Depending on the business logic of your application, you can choose from:

  • Per user preferences – implemented as person custom attributes and affect all devices connected to identified Profile.
  • Per device preferences – implemented as Installation custom attributes and affect the single device only.

Preferences can be managed with:

Tags are always associated with Person profile and can be managed with:

All the synced data is available for your audience Segmentation and automated communication with Flow.

Cross device synchronization

All personal preferences and subscriptions are automatically synchronized between all devices linked to a single Person profile.

For personalized Profile you can:

Behavioral Events

Behavioral events can the end user activity in mobile application and you can use this data in real time engagement or historical events segmentation. By tracking mobile events, you can better understand your audience and trigger relevant communication at the right moment. Additionally, you can audit details on single person profile changes in People (opens in a new tab).

All synced events data for your audience is available using Segmentation and the communication is automated using Flow.

Event Categories

Mobile SDKs include a set of standard events and have special methods for custom events where you can define specific scenarios and data points.

Standard and custom events have the following metadata associated with the event that is recorded automatically:

  • Timestamp – Timestamp when the event was tracked by Infobip platform
  • Event definition ID
  • Event properties (if any)

Standard Events

Once standard events are enabled, the Mobile SDK starts tracking it without any additional configuration.

EventDetails
InstallOnce a mobile app is installed on a device, an event is merged with the identified person from the anonymous Person if device was personalized.
UninstallEvent that identifies when an uninstall was performed on a device. It remains in the history events in the identified Person profile.
PersonalizeEvent that tracks when an end user registers in your mobile app. The event is based on personalized methods. Event is merged with the identified Person from anonymous person.Remains in history of events in the identified Person profile.
DepersonalizeEvent tracks when an end user logs out from the mobile app. Remains in history of events in the identified Person profile.
App Launch  Events tracks if a mobile application was opened by the end user. Remains in  history of identified and anonymous Person profile.
NOTE

Please note that the App Launch event will be logged in case the previous App Launch event happened more than 30 seconds ago. In case the mobile app was launched, closed and then launched once again in less than 30 seconds, the first App Launch event will be logged only.

Standard Event Properties

The following properties are associated with all standard event:

Custom Events

Custom events are events that you have to define yourself and then track via Mobile SDK.

Here's how to track custom events with a mobile app:

  1. Create event definition in the web interface (opens in a new tab).
  2. Implement events tracking functionality:

Need assistance

Explore Infobip tutorials

Encountering issues

Contact our support

What's new? Check out

Release notes

Unsure about a term? See

Glossary

Research panel

Help shape the future of our products
Service Terms & ConditionsPrivacy policyTerms of use