Terms

Term

Explanation

Notification

Also known as a notification bar message. A notification automatically appears in the notification bar on a mobile device. A user can open or clear the notification. iOS notifications are sent through Apple Push Notification service (APNs). Android and HarmonyOS notifications are sent through Mobile Push's own channel or an auxiliary channel.

Message

Also known as a pass-through message or a custom message. A message does not automatically appear in the notification bar. After the client receives the message, it must handle how the message is displayed or what action to take. Messages for iOS, Android, and HarmonyOS are all sent through Mobile Push's own channel.

Device ID (DeviceId)

The unique identifier for a device in the push service. It is generated by the software development kit (SDK) and is a 32-character string of numbers and lowercase letters. Obtain it through code. To get the device ID: For Android, use the getDeviceId method of CloudPushService. For iOS, use the getDeviceId method of CloudPushSDK. For HarmonyOS, use the aliyunPush.getDeviceId method.

Account

An account attached to a device. It can be any account that your business requires. A device can be attached to only one account. An account can be attached to multiple devices.

Alias

An alias attached to a device. It can be any alias that your business requires. A device can be attached to a maximum of 128 aliases. An alias can be attached to a maximum of 128 devices.

Tag

A tag attached to a device. It can be any tag that your business requires. An application can have a maximum of 10,000 tags. There is no limit to the number of devices that can be attached to a tag.

Push by device ID

Call getDeviceId on the client to get the device ID. Then, send the push through the console, OpenAPI Portal, or OpenAPI.

Push by account

Call the bindAccount operation on the client and pass your business account as a parameter. For example, if your app uses a phone number for logon, you can use the phone number to call bindAccount. Then, send the push through the console, OpenAPI Portal, or OpenAPI.

Push by alias

After attaching an alias to a device, filter the aliases based on your business logic to send message pushes.

Push by tag

After attaching a tag to a device, filter the tags based on your business logic to send message pushes.

Full push

Also known as a broadcast push. It refers to sending a push to all devices.

Offline message cache

A cache duration can be set for message pushes. Offline devices receive the message only if they come online before the cache expires.

Batch push

Combine multiple push requests into an array and send the push by calling the batch push API. This can effectively reduce the queries per second (QPS) of requests.

Continuous push

Reuse the same message ID to send pushes over a period of time. This allows the results of this batch of pushes to be aggregated under the same message ID.

Vendor Channel Push

Also known as an auxiliary channel push. This is a system-level push service provided by the mobile phone manufacturer. If the network is available and the push message is legitimate, messages sent through the third-party channel can be delivered to the corresponding mobile phone model regardless of whether the application is running. The message is delivered as long as the device is powered on.

Proprietary channel

Alibaba Cloud Channel Service (ACCS), the Alibaba Cloud push service. It is the basic push channel for Alibaba products.

Successfully Accepted

A push is accepted only if the target device is valid and can potentially receive the message. The device must not have expired. By default, Android devices must have been active within the last 90 days, and iOS devices must have been active within the last 24 months. Pushes cannot be sent to devices that have been inactive longer than these periods. The user must not have disabled the push feature.

The number of accepted pushes is the total number of target devices in the original request minus the devices to which the push could not be sent.

Number of sent pushes (actual deliveries)

The number of messages that were successfully sent. For the proprietary channel, a mobile terminated message can be sent when the device establishes a connection. This action is called sending. For a third-party channel, a message is considered sent when it is successfully delivered to the third-party server.

Number of arrivals

Also known as the number of deliveries. The calculation method varies for different devices:

iOS devices: iOS notifications are delivered to Apple's APNs servers. A notification is considered to have arrived if the Apple server does not return an error message.

Android and HarmonyOS devices: The number of arrivals for a device is the sum of deliveries from the proprietary channel and third-party channels. Each channel provides a delivery receipt.

Online delivery rate

Number of arrivals through the online channel / Number of pushes sent through the online channel.

Sent rate

Number of sent pushes / Number of accepted pushes.

Arrival rate

Number of arrivals / Number of sent pushes.

AppKey

The unique identifier for an application in Mobile Push. It is required for SDK initialization and for sending pushes by calling OpenAPI. Obtain it from the application certificate on the App List page in the Mobile Push console.

AppSecret

The key for an application. It is required for SDK initialization. Obtain it from the application certificate on the App List page in the Mobile Push console.

DeviceToken

A 64-bit device identifier returned when an iOS device registers with Apple. An iOS device has both a DeviceId and a DeviceToken. Do not confuse them.

Message ID (MessageId)

The ID that identifies a single push. It is returned when you send a push by calling an OpenAPI. You can also view it in the Mobile Push console.

Multiple package names

Add package names for each channel in advance. This allows a single push to reach packages on all channels.