Push analytics

To go to Push analytics click Analytics -> Push Notifications.

On the first screen we have access to a global analytics – all messages sent in a given period of time for android, ios or both systems.

pa1

We can choose the period of time for the display analytic: today, this week, last week, this month and last month.

Push notifications sent – number of all sent push message.

Application launches count – number of application launch.

Average time spent in app – the time that the average user spends in the application in seconds.

Chart shows the relationship between the amount of sent push, the amount of opening applications, and the average time spent in the application.

pa2

Push clicks for users – chart shows the number of clicked push message.

pa3

In the table we see all sent push messages.

pa4

Date – informs when push was sent.
Push – the name of our push messages.
Sent – number of sent push message.
Clicked – number of clicked push message.
Efficiency – the amount of clicked push messages in relation to sent push messages.
Push influence – the number of application launch in the 24 hours after pushu, minus the average number of launch if we don’t send push message.
Advanced analytics – by clicking the details, we go to advanced analytics for a specific push message.

After entering the advanced analytics of push messages again we see a summary of the amount sent, clicked, effectiveness and impact of push and additional information.

pa5

The table presents statistics of modules used after sending push message
Module opened after push been sent – shows how many users opened module after push message has been sent.
Module opened after push been clicked – shows how many users opened module after push message has been clicked.
Standard module opened (with no push sent) – shows how many users normally opens the module (without sent of the push messages)
Module opened/push clicked (%) – presents the percentage of people who have visited a particular module after clicking on the push message.

pa6

The graph shows the time spent in the application modules after pushu compared to the standard time spent in the application modules.

pa7

The table presents statistics of function or custom event usage after sent of push message.
Luanches after sending push – shows how many users launched function after push message sent .
Launches after clicking push – shows how many users launched function after push message clicked .
Standard launches (without push) – shows how many users normally use the function (without sent of the push messages)
Function launches/ push clicked (%) – It presents the percentage of people who used the function after clicking on the push message.

pa9

The number of calls to a predefined function of purchase after sending Push.

pa8

Graph shows the mean number of function launch after the push sent compared to the standard amount of function launch.

x1 x2

Graphs shows number of push opening for groups of users: daily, weekly, monthly, less often.

Path analysis

Path analysis is functionality which allow us to see how users move around our application. Data obtained through this module helps in app traffic optimization.

To go to Path analysis click Analytics -> Path analysis.

pa1

In the chart we can see in how many steps users reach specific module of our application.

In boxes we can see module name and it’s value which is number of users in this module in particular step.

pa2

Abandoned – percent of users which are leaving your application in particular step.

pa3

When we move on particular path between modules we can see how many users move this way.

pa4

In example 10 users move from module 2 to module 3.

Transitions graph – represents how many clicks occurred between specific modules and functions.

pa5

In this example in the module 1 occurred 50 use of function 1.

Location

Location – allows you to define a group of users based on whether staying or not staying in a specific location for the last x hours, days , weeks or months.

contionlocation

We define locations by clicking on the map icon and selecting respectively on the area.

mapa

Language

Language – It allows you to define a group of users based on whether the device language is the same or different from indicated.

conditionlang

In an exemplary dynamic segment there are people who uses Polish version of the operating system on their mobile devices.

Mobile profile

In APPmanago we have access to the Mobile profile of individual users . To get to them enter in the Users tab.

mp

We can search for a particular contact by entering their email address , select a contact from the list, or select a random user .

kk

Mobile profile is a collection of basic information such as the user’s email address, an application which uses, the language of the device, its operating system and the latest location.

Dynamic segments it shows a dynamic segment in which the user is located.

tl

Timeline – it contains information about actions taken by the user ( application modules viewed or used features ) and messages sent to him ( push email) .

sta

Statistics – contain information about, first start of the application, last start of the application and time the user spent in the aplication.

Time spent in modules – a graph showing the time spent on each application modules.

travel

Travel line – a line of travel on which we can see in which places was our User.

Dynamic segment analytics

If we want to check Dynamic segment analytics we click Automation -> Dynamic segment and click analitics button.

dsa

Dynamic segment analytics is calculated once a day.

ana1

Users in segment – It specifies what is the number of users in a dynamic segment
Android users – It specifies what is the number of Android users in the dynamic segment.
IOS users – It specifies what is the number of IOS users in the dynamic segment.
All users – The amount of all users of the application.

ana2

All users Users in segment by usage frequency – The graph shows the number of the segment by day and daily , weekly , monthly and less often users activity.

Average time spent in modules – chart shows the average time, users spends in the Application modules.

ana3

Two similar graphs showing numbers in the segment divided into systems – Android and IOS .

SALESmanago integration

To integrate APPmanago with SALESmanago go to Settings -> SALESmanago.

sm

Then you can configure:

Application – we chose our mobile aplication
Client ID – enter Client ID which is found in SALESmanago -> Settings-> Integration
API secret – enter API secret which is found in SALESmanago -> Settings-> Integration
Endpoint – enter Endpoint which is found in SALESmanago -> Settings-> Integration
Owner – Enter the owner of contacts from SALESmanago

GCM account

To set up a GCM account go to Settings -> E-mail accounts and click on the “Create account’ button.

gcm
Then you can configure:
Account name: internal account name in the system, used mainly for its identification
Sender ID: enter Project Number which is found in the Overview tab of our project on the Google Developers Console: https://console.developers.google.com
Api KEY: Api KEY from Google Developers Console, available at: Apis & Auth -> Credentials.
GCM server: choose a server from the GCM.

 

 

Configure email account

To set up a new account go to Settings -> E-mail accounts and click on the “Create email account’ button.

m
Then you can configure:

1. Account name – internal account name in the system, used mainly for its identification
2. Email address – type in email address you will use for sending messages
3. Display name – Sender’s name displayed in the incoming mail box of the recipient before the subject line.
4. Reply to (email) – email address for replies to messages sent from this account. If the created address does not exist outside APPmanago you must set up the existing mailbox here.
5. Reply to (name) – name which will appear on replies

Steps 4 and 5 may be skipped if the data is the same as in fields 2 and 3.

Scheduled action

To create Scheduled action enter Communication -> Scheduled action and click Create Scheduled action.

Name – helps us identify our notification in system.

Send date – It allows us to set the date when the notification is to be sent.

Application – we choose in which application, notification should be displayed.

Select dynamic segment from list below – It lets you select audience by defining the dynamic segment.

Action – We choose between sending email or push message. Set action by drag and drop it.

sa