All Products
Search
Document Center

Usage analysis

Last Updated: Sep 08, 2021
Important: Since June 28, 2020, mPaaS has stopped support for the baseline 10.1.32. Please use 10.1.68 or 10.1.60 instead. For how to upgrade the baseline from version 10.1.32 to 10.1.68 or 10.1.60, see mPaaS 10.1.68 upgrade guide (Andorid/iOS) or mPaaS 10.1.60 upgrade guide (Andorid/iOS).

MPS provides statistics on message push data including pushed messages, successfully pushed messages, message arrivals, opened messages, and ignored messages, and supports filtering the data by platform, version, push channel, push type, and other criteria, and exporting the data reports.

Prerequisites

  • You have integrated MPS SDK based on the mPaaS framework.
  • You have completed client tracking by referring to the following topics. All data involved in usage analysis are collected from the SDK tracking logs.

View usage analysis report

To view the statistical data about MPS usage, you should complete the following steps:

  1. Log in to the mPaaS console, select the target app, and enter the Message Push Service > Usage analysis tab page.
  2. Set filter criteria to query statistical data. You can filter by platform, version, push channel, push type, and time, or input a complete task ID to search.
    Note: Searching data with task ID only works for messages delivered through multiple or broadcast push. You can view the task ID on the Push task list page.
    • Platform: The options include All platforms, Android - workspaceId, and iOS - workspaceId. Available options depend on the existing push platforms with message push and the push console which launches message push. For example, if no message has been pushed to iOS devices, the iOS - workspaceId option is unavailable. In these options, workspaceId indicates the workspace ID of the push console.
    • Version: The value depends on tracking log reported by the client SDK. MPS gets the app version based on MAS statistics.
    • Push channel: The options include All push channels, MPS self-built channel, and Third-party channel (such as MIUI, HMS, vivo, OPPO and iOS). Only when any message push through the push channel occurred, the corresponding option is available. For example, if no message has been pushed through MIUI (MiPush) channel, the MIUI option is unavailable.
    • Push type: The options include All push types, SIMPLE, TEMPLATE, MULTIPLE, and BROADCAST. Only when message push of the push type occurred, the corresponding option is available. For example, if no simple push occurred, the SIMPLE option is unavailable.
    • Time range: A maximum of 90 days is allowed.

1

Cri metrics overview

Display the critical push data within a certain period, including the push count, pushed messages, message arrivals, opened messages, ignored messages, etc.

Metrics Description
Push count The total number of messages pushed by the backend, which is counted by backend.
Pushed messages MPS automatically collects statistics on the actual number of messages that have been pushed in the specified time period, which is counted by backend. The statistics doesn’t care whether the messages were pushed within the specified time period.
  • One push task may contain multiple target IDs, and MPS needs to push a message to each of these targets.
  • If a token has expired or a user binding relationship does not exist, the target ID is invalid and MPS will not count the messages pushed to this target.
Message arrivals The actual number of messages that have arrived at the client, which is counted by client. The statistics doesn’t care whether the messages were pushed within the specified time period.
For example, if the message arrivals during 2021.8.1 ~ 2021.8.7 is 100, it means 100 pieces of messages arrived at client during the period. Among those 100 pieces of messages, some may be pushed before August 1.
The data statistics varies with the push channels:
  • Android self-built channel: After messages are successfully pushed to devices, statistics are collected based on tracking log data reported by the client SDK.
  • iOS and Android third-party channels: After messages are pushed through specified channels, statistics are collected based on push results returned by backend services of these channels.
Arrival rate Arrival rate = (Message arrivals/Pushed messages) × 100%.
Opened messages The actual number of messages that have been opened on the client, which is counted by client. The value depends on tracking log data reported by the client SDK. MPS obtains the number of opened messages based on MAS statistics. The statistics doesn’t care whether the messages arrived at client within the specified time period.
For example, if the number of opened messages during 2021.8.1 ~ 2021.8.7 is 88, it means 88 pieces of messages were opened by users during the period. Among those 88 pieces of messages, some may have arrived at client before August 1.
Open rate Open rate = (Opened messages/Message arrivals) × 100%
Ignored messages The number of messages that are manually ignored by users on the client. The statistics doesn’t care whether the messages arrived at client within the specified time period. The value depends on tracking log data reported by the client SDK. MPS obtains the number of ignored messages based on MAS statistics.
For example, if the number of ignored messages during 2021.8.1 ~ 2021.8.7 is 66, it means 66 pieces of messages were manually ignored by users during the period. Among those 66 pieces of messages, some may have arrived at client before August 1.
Ignorance rate Ignorance rate = (Ignored messages/Message arrivals) × 100%

Push data trend

Message push statistical data is presented in a line chart. You can click the metric legend under the chart to hide or display the curve of a metric.

In the upper left corner of the chart, you can select Query by quantity or Query by rate to view the metric statistics in quantity or rate curves.

  • Query by quantity: Displays curves of pushed, arrived, opened, and ignored messages.
  • Query by rate: Displays curves of the arrival rate, open rate, and ignorance rate.

In the upper right corner of the chart, you can select a granularity to display the chart by minute, hour, or day.

  • Minutes: The horizontal axis displays the time points (accurate to minutes) of pushed, arrived, opened, and ignored messages.
  • Hours: The horizontal axis displays the time points (accurate to hours) of pushed, arrived, opened, and ignored messages.
  • Days: The horizontal axis displays the time points (accurate to days) of pushed, arrived, opened, and ignored messages.
Note: If you set a duration longer than one day, Minutes and Hours will be unavailable.

Push details

Daily or hourly push details listed in the table are consistent with data displayed in the core metric chart.

  • The time points in the Time column are obtained from the horizontal axis of the core metric chart.
  • The list contains the following core metrics: Push count, Pushed messages, Message arrivals (arrival rate), Opened messages (open rate), and Ignored messages (ignorance rate).

Click Export in the upper right corner to download the corresponding data.

2