Vendor Message Classification Usage Guide

Message classification description

from Android 8.0（API Starting with level 26), all messages must go through the corresponding channel ID (ChannelID) is issued. Currently, in order to improve end-user push experience and create a good and sustainable notification ecosystem, each manufacturer will classify and manage push messages according to the content of the message. Different message classifications are mainly through channel ID (ChannelID) to differentiate. At present, messages are mainly divided into the following two categories:

JiguangChannel message classification usage

If you need to classify and manage messages based on push content, you can customize Channel ID。

• ​Create client-side custom channels。
• The corresponding channel ID is issued when pushing.

channel_id The parameters are in notification of android under the field.

Examples are as follows:

          {
    "platform": "all",
    "audience": {
        "registration_id": [
            "1104a8979278ae64e75"
        ]
    },
    "notification": {
        "android": {
            "alert": "message alert",
            "channel_id": "your channel_id"
        }
    }
}

        

• If you need to deliver manufacturer channel importance level messages, please refer to the usage guide for each manufacturer message category below.

Xiaomi message classification usage guide

Xiaomi message classification description

according to"New rules for classifying Xiaomi push messages", Xiaomi Push divides messages into two categories: "Private message" and "Public message". If the application chooses not to access private messages or public messages, message push will fail.

Note: According to New rules for classifying Xiaomi push messages, there is no default message classification. Developers must access message classification according to the official new regulations and migrate to the newchannelIssued. In other words, when pushing, you must pass channel_id field, otherwise the manufacturer will return a push failure error.JiguangIt will be treated as a "parameter error" type and stage 2 loss processing.

Xiaomi important level information application

For application methods, please refer to Xiaomi’s official documentation. channel Application and access methods。

Note: You must receive an approved email before you can use the private message function! And when pushing, you must pass channel_id field, otherwise the manufacturer will return a push failure error.JiguangIt will be treated as a "parameter error" type and stage 2 loss processing.

Xiaomi message classification usage

Server use

classification The parameters are in options under field;
channel_id The parameters are in options of third_party_channel under the field.

Examples are as follows:

          {
    "options": {
        "classification":1,
        "third_party_channel": {
            "xiaomi": {
                "channel_id": "小米推送平台登记的 channel id"
            }
        }
    }
}

        

Console usage

• For private messages, you need to select "System Message".

• Fill in the Xiaomi push platform registration channel id。

Huawei message classification usage guide

Huawei message classification instructions

Based on the message content, Huawei Push classifies notifications into two categories: service and communication, and information marketing, and differentiates the reminder methods and message styles of different categories of messages, as follows:

Huawei message classification method

Huawei Classification Standard
from2023Starting from September 15, 2020, Huawei Push Service will divide notifications into "Cloud Notifications" and "Local Notifications" based on the "Huawei Message Classification Standards". For specific reference Huawei message classification management solution。

How to use Huawei message classification "Cloud Notification"

"Cloud Notification" server usage

After the application for message classification is approved, you can specify classification、importance To issue,
classification The parameters are in options under the parameter field.
importance The parameters are in options Optional parameters third_party_channel under the field.

The code example is as follows:

          {
    "options": {
        "classification":1,
        "third_party_channel": {
            "huawei": {
                "importance": "NORMAL",
                "category":"IM"
            }
        }
    }
}

        

Using the "Cloud Notification" console

• Service and communication messages need to select "System Messages".

How to use Huawei message classification "local notification"

"Local notification" server usage

Specify category To issue,
The parameter is notification.android Optional parameters.

The code example is as follows:

          {
    "notification": {
        "android": {
            "alert": "Hi, JPush!",
            "title": "Send to Android",
            "category": "CATEGORY_NAVIGATION",
            "priority": "0"
        }
    }
}

        

"Local notification" console usage

Huawei message classification correspondence table

As the message sending scenarios of applications continue to change, the classification standards pushed by Huawei will continue to evolve and be supplemented. Please pay attention to the latest classification instructions in Huawei's official documents. Reference Message classification criteria Query.
Cloud notification importance For the value rules, please refer to the above "How to use Huawei message classification "Cloud Notification"" importance Field description.

Honor message classification usage guide

Honor message classification description

According to the message content, Honor Push classifies notifications into two categories: service and communication, and information marketing, and differentiates the reminder methods and message styles of different categories of messages, as follows:

Honor message classification method

According to Honor’s official description: 2024Before December 31, 2020, developers need to log in to the Honor Developer Service Platform to apply for self-categorization rights and conduct classified management of push service messages. If the application does not have self-categorization rights, or the application has self-classification rights but the push message does not carry them importance field, the push messages of the application will be automatically classified as information marketing messages. For details, please seeHonor message classification method。

How to use Honor message classification

Server use

Specify classification、importance Deliver;
classification The parameters are in options Under the parameter field;
importance The parameters are in options Optional parameters third_party_channel under the field.

Examples are as follows:

          {
    "options": {
        "classification":1,  // 特别说明：此字段优先级更高，当classification指定值和importance指定值不一致时，以此字段值为准
        "third_party_channel": {
            "honor": {
                "importance": "NORMAL"
            }
        }
    }
}

        

Console usage

• Service and communication messages need to select "System Messages".

• Service and communication messages need to be set up importance for NORMAL。

OPPO Message Classification Usage Guide

OPPO Message classification description

• OPPO Manufacturer 2024.11.20 implementOPPONew rules for message classification, messages are divided into two categories: "Communication and Services" and "Content and Marketing", corresponding toJiguangPlatform "system news" and "operation news", based on the attention paid to different types of news,OPPOThe official corresponding permissions are as follows:

OPPO Push quantity limit

OPPO Message classification usage

• Step1: Server attention (classification、channel_id、category、notify_level) 4 fields, detailed field descriptions are as follows, or viewJPush API document。
  
• Step2: When configuring push messages, carry the above fields, and the messages will be delivered in the corresponding reminder mode.
  

Examples are as follows:

          {
    "options": {
        "classification":1,
        "third_party_channel": {
            "oppo": {
                "channel_id": "OPPO 官网登记的通道 ID"
                "category": "IM"
                "notify_level": 16
            }
        }
    }
}

        

Console usage

• You need to select "System Message" for private messages. Please select the correct one based on the actual situation.

• fill in OPPO Message classification parameters, make sure the data is filled in correctly.

vivo Message Classification Usage Guide

vivo Message classification description

• Valid users with notification turned on: application integrated push-sdk The subscription is successful, and the device has been connected to the Internet within the past 14 days and the notification permission is enabled for the user.
• Number of effective users with notification enabled＜10000, then the operational message level defaults to 10000。
• The number of valid users with enabled notifications and the magnitude of operational messages that can be sent can be queried in the push operation background.
• The push limit is calculated based on the "arrival amount". If the arrival amount exceeds the limit on the same day, it will be included in the control.
• Test messages are not limited by magnitude and frequency control. Please fill in the information when sending a test message pushMode=1 (0: official push; 1: test push; default is 0 if left blank). If not filled in, if the copywriting is the same, it will be regarded as a duplicate operation message and be deduplicated.

vivo System message usage

1. pass API Pass in the corresponding parameters
Special Note: Pass API The interface supports message classification and delivery classification parameter, which is in options under the optional parameters field. There are 2 complete classification fields, as explained below:

Examples are as follows:

          {
    "options": {
        "classification":1,
        "third_party_channel": {
            "vivo": {
                "distribution": "secondary_push",
                "category":"IM"
            }
        }
    }
}

        

• Console usage: For system messages, you need to select "System Messages".

  

• Configuration complies with vivo taxonomic category。

  

2． Intelligent classification secondary correction

• Passing "0" in the parameter represents operational messages, which will be directly deducted from the total amount of operational messages without secondary correction by intelligent classification, and are subject to frequency control limited by the number of messages received by the user.
• Passing "1" in the parameter represents a system message. After secondary correction by intelligent classification, if the intelligent classification identifies that it is not a system message, it will be automatically corrected as an operating message, and the operating message quota will be deducted; if it is identified as a system message, the quota will be deducted from the total system message.

vivo local notification

• Official regulations reference: vivo local notification
• According to official regulations, through App long connectionJiguangRemotely delivered by channel Push also belongs to vivo Local notification scope, developers must pay attention to it, throughJiguangWhen the channel is issued, the specified channel_id The value needs to be inAppThe code layer is created and needs to be passed vivo Open platform review.

This parameter is in notification.android under the field. As follows:

Examples are as follows:

          {
    "notification" : {
        "android" : {
             "alert" : "hello, JPush!",
             "title" : "JPush",
             "channel_id" : "活动提醒",
             "category":"category001",
             "intent": {
                "url": "intent:#Intent;component=com.jiguang.push/com.example.jpushdemo.SettingActivity;end"
             }
        }
    }
}

        

Meizu message classification usage guide

Meizu message classification description

according to"Meizu’s new push message rules》，⾃2025Starting from May 7, 2019, Meizu Push will divide messages into two categories: "Private message" and "Public message", allowing developers to classify messages themselves according to Meizu Push message classification specifications. The platform will daily inspect the access status of message classification. If push content is found to be inconsistent with the corresponding scenario, it will be strictly dealt with.

Meizu message classification usage

pass API docking use

Special Note: Pass API The interface supports message classification and delivery classification parameter, which is in options under the optional parameters field. There are 2 complete classification fields, as explained below:

Examples are as follows:

          {
    "options": {
        "classification":1,  // 请开发者特别注意正确设置此字段值
        "third_party_channel": {
            "meizu": {
                "distribution": "secondary_push"
            }
        }
    }
}

        

Console usage

• For system messages, you need to select "System Message".