Third-party channels: Push limitations and message classification
Push notifications can fail due to varying restrictions on vendor channels and the use of message classification by some vendors. To avoid these failures, review the push restrictions for each vendor. Additionally, some vendors require you to apply for a compliant message classification. This article outlines best practices for vendor channel push restrictions and message classification.
Vendor push limits and message classification
Vendor | Type | Daily push quota | Device limit | Other limits |
Huawei | Service and communication messages | Unlimited | Unlimited |
|
Information and marketing messages | Unlimited | News (tertiary classification is News): 5 messages Others: 2 messages | ||
Honor | Service and communication messages | Unlimited | Unlimited |
|
Information and marketing messages | Unlimited | News (tertiary classification is News): 5 messages Others: 2 messages | ||
Xiaomi | Private messages | Unlimited | Unlimited |
|
Public messages | (Number of app installs on MIUI with notifications enabled) × multiplier. The default multiplier is 2. | 5–8 messages per app, per device, per day. | ||
Default | 1x multiplier | 1 message per app, per device, per day. | ||
OPPO | Communication and service / Legacy private messages | Unlimited | Unlimited |
|
Content and marketing / Legacy public messages | Daily quota: 20,000 for < 10,000 cumulative users; cumulative users × 2 for ≥ 10,000. | News (tertiary classification is News): 5 messages Other app types: 2 messages | ||
vivo | System messages | 3 times the number of active users with notifications enabled. | Unlimited |
|
Operational messages | News (tertiary classification is News): 3 times the number of active users with notifications enabled. Others: 2 times the number of active users with notifications enabled. | News (tertiary classification is News): 5 messages Others: 2 messages | ||
Meizu | / | / | More than 4 messages are collapsed. |
|
/ | / | / |
| |
HarmonyOS | Service and communication messages | Unlimited | The total for all message types is limited to 3,000 per app per device daily. |
|
Information and marketing messages | Unlimited | News (requires an "Internet News Information Service License"): 5 messages Others: 2 messages | ||
APNs | / | / | / |
|
Huawei
Push limits
Push limit
Under the Push Notification Quota Management Rules, as of January 5, 2023, daily push quotas for marketing messages are capped based on application type, while quotas for service and communication messages are unlimited:
Message type | Daily push limit | User daily limit |
Service and communication messages | Unlimited | Unlimited |
Informational and marketing messages | Unlimited | News (requires an Internet News Information Service License): 5 Others: 2 |
On September 15, 2023, Huawei implemented a new policy: Huawei's mobile system now controls all notifications, regardless of an app's online or offline status. This policy limits the number of notifications that can be sent and how they are displayed. For details, see New Control Rules and Adaptation for HUAWEI Push Service.
Push QPS limit
QPS = app MAU on the Huawei channel × application category weight × overall allocation coefficient.
MAU: monthly active users.
app category weight: Apps not released on HUAWEI AppGallery are assigned to the Default category with a weight of 1.
overall allocation coefficient: A dynamic coefficient for calculating QPS. You do not need to calculate the QPS value yourself, as it is displayed in AppGallery Connect. For instructions on how to find it, see the Huawei FAQ documentation.
If the calculated QPS for your app is less than 6,000, the system applies a default QPS of 6,000. During periods of high network-wide traffic, system-level throttling may also occur. For more information, see message throttling issues.
To request a QPS adjustment, email Huawei Support at hwpush@huawei.com.
Message classification
According to the message classification standard, HUAWEI Push Service classifies notification messages into two main categories: news and marketing, and service and communication.
Message classification
1. Specific message types
To apply for the category parameter, follow the process described in Applying for Huawei self-classification privileges. You can apply for multiple values.
The Huawei channel offers two self-classification privilege parameters: importance and category.
importance: The notification's alert level. NORMAL is for important messages, and LOW is for general (silent) messages.
category: The notification category, which can be either a cloud-side notification or a local notification:
If you specify categories for both a cloud-side notification and a local notification, only the cloud-side notification category takes effect. Messages are delivered through the Alibaba Cloud channel when the app is online and through the Huawei channel when the app is offline.
If the cloud-side notification category is "Not Applicable" and a local notification category is specified, only the local notification category takes effect. Messages are delivered exclusively through the Alibaba Cloud channel.
If the local notification category is "Not Supported" and a cloud-side notification category is specified, only the cloud-side notification category takes effect. Messages are delivered exclusively through the Huawei channel.
Primary category | Secondary category | Message type | Cloud category value | Local category value | Notification behavior |
Service and communication | Social communication | IM | IM | CATEGORY_MESSAGE | Appears on the lock screen with a ringtone and vibration. The importance is set to NORMAL to indicate an important message. |
VoIP | VOIP | CATEGORY_CALL | |||
Service reminders | Subscription | SUBSCRIPTION | Not supported | ||
Travel | TRAVEL | CATEGORY_NAVIGATION | |||
Health | HEALTH | Not supported | |||
Work reminder | WORK | CATEGORY_REMINDER | |||
Account activity | ACCOUNT | Not supported | |||
Order and logistics | EXPRESS | Not supported | |||
Finance | FINANCE | CATEGORY_SERVICE | |||
Device reminder | DEVICE_REMINDER | Not supported | |||
CATEGORY_EMAIL | |||||
Alarm | Not applicable | CATEGORY_ALARM | |||
Stopwatch | Not applicable | CATEGORY_STOPWATCH | |||
Progress | Not applicable | CATEGORY_PROGRESS | |||
Location sharing | Not applicable | CATEGORY_LOCATION_SHARING | |||
Information and marketing | Content information | Content recommendation | MARKETING | CATEGORY_RECOMMENDATION | Appears as a silent notification in the notification shade. The importance is set to LOW for general messages. |
News | |||||
Financial updates | |||||
Lifestyle information | |||||
Surveys | |||||
Other | |||||
Social activity | CATEGORY_SOCIAL | ||||
Marketing campaigns | Product promotion | MARKETING | CATEGORY_PROMO | ||
Feature recommendation | |||||
Operational activity |
II. High-priority passthrough scenarios
To use VOIP (audio and video calls) or PLAY_VOICE (voice broadcasts) as the category value, you must apply for special permissions on the Huawei platform (see Apply for special permissions for details).
Message classification
Prerequisites: Complete Android SDK Integration (3.x) and Huawei Push Channel Integration.
Once you have obtained Huawei self-classification rights, you can push categorized messages using the EMAS Console or OpenAPI.
EMAS console push
To send a push notification using the EMAS console push service, select the Huawei channel and an appropriate message type in vendor settings - notification channel and notification category.

OpenAPI push method
To call the advanced push API, pass the following parameters:
AndroidMessageHuaweiCategory: Specifies the cloud notification category value or local notification category value for custom classification on the Huawei channel.
AndroidNotificationHuaweiChannel: Specifies the importance parameter for custom classification on the Huawei channel.
Typically, you only need to pass AndroidMessageHuaweiCategory. To deliver service and communication messages in silent mode (no sound or vibration), set the importance field to LOW.
Additional settings
Send a test message
1. To call the advanced push API, set the following parameters:
Set AndroidHuaweiTargetUserType to 1 to enable direct push. Each application can send up to 500 test messages per day, which do not count toward the daily push limit.

AndroidTargetUserType=1: This is equivalent to setting the AndroidHuaweiTargetUserType, AndroidHonorTargetUserType, and AndroidVivoPushMode parameters.

2) When using the EMAS console push service to send a notification push, go to vendor settings and disable the production notification for the Huawei channel.

Awards
Push limits
Push quota
Based on the message classification standard, the Honor push service classifies notification messages into two categories: information and marketing, and service and communication. The table below details the specific message limits.
Message type | Daily push limit | Daily user limit |
Service and communication | Unlimited | Unlimited |
Information and marketing | Unlimited | News: 5 messages Others: 2 messages |
Push rate QPS limit
QPS: 3,000
Honor is not currently accepting applications for quota increases.
Message classification
To improve the user's push experience, the Honor Push Service classifies push messages. For details, see Honor Message Classification Standard.
By December 31, 2024, applications must apply for the self-classification privilege on the Honor Developer Service Platform to classify and manage push service messages.
If an application has not applied for the self-classification privilege, or if it has the privilege but sends a push message that does not contain the importance field, the platform automatically classifies the push message as an information and marketing message.
Message classification
Honor Push Service uses the importance parameter to classify push messages into two categories: Service Communication (NORMAL) and Informational and Marketing (LOW).
Each category has a distinct notification behavior, as described below:
Message type | Value | Description |
Service communication | NORMAL | Displays on the lock screen and in the notification bar. Supports ringtone and vibration. |
Information and marketing | LOW | Silent notification; displays only in the notification bar. |
HONOR Push Service classifies messages in two ways:
Intelligent message classification
Intelligent algorithms automatically classify your messages based on dimensions such as app type and message content.
Custom message classification
Developers can classify messages themselves based on the message classification specifications. To apply, see application for custom classification privileges.
By default, custom message classification applies to all messages. As the Honor Push Service evolves, the classification methods will also be updated. For details, see the Honor Message Classification Standard.
Message classification
Prerequisites: Android SDK integration (3.x) and Honor channel integration.
Once your application for Honor message classification is approved, you can send classified messages using the EMAS console or OpenAPI.
EMAS console
When using the EMAS Console push service to send a push notification, in Vendor Settings - Notification Channel and Notification Category, check Honor Channel and select the corresponding message type.
When you select promotional messages,
importanceis set toLOW, and the message defaults to a silent notification that appears only in the notification shade.When you select service messages,
importanceis set toNORMAL, and by default, the message appears on the lock screen and in the notification shade.

OpenAPI push
When you call the advanced push API, pass the following parameters:
Setting the AndroidNotificationHonorChannel field to LOW classifies the message as a marketing and promotional message. By default, it appears as a silent notification only in the notification shade.
Setting the AndroidNotificationHonorChannel field to NORMAL classifies the message as a service and communication message. By default, it appears on the lock screen and in the notification shade.
Other settings
Sending a test message
1. When calling the advanced push API, set the following parameters:
AndroidHonorTargetUserType = 1: Enables direct push, allowing each application to send up to 500 test messages per day without counting toward the daily push limit.

AndroidTargetUserType=1: This setting has the same effect as configuring the AndroidHuaweiTargetUserType, AndroidHonorTargetUserType, and AndroidVivoPushMode parameters.

2) When using the EMAS Console push service for a notification push, go to vendor settings and disable the Honor channel's production notification.

Xiaomi
Push restrictions
Push quota
As of February 1, 2023, Mi Push classifies messages into two categories in accordance with the New Rules for Mi Push Message Classification: private messages and public messages. Applications that do not opt to use the private or public message channels will be routed through the default channel.
Message type | Total daily limit | Daily user limit |
Default | 1x | 1 message |
Public informational message | With an Internet News Information Service License: 3x Other: 2x | With an Internet News Information Service License: 8 messages Other: 5 messages |
Private message | Unlimited | Unlimited |
The daily push quota for public trust messages is: number of users with notifications enabled for the app on MIUI × multiplier. The default multiplier is 2. For applications that hold an Internet News Information Service License, the multiplier is 3. If the number of users with notifications enabled is less than 10,000, it is counted as 10,000.
The number of users with notifications enabled for the app on MIUI is the count of users who have activated the app and manually enabled the master notification switch.
The daily push quota is based on the delivery count. If the daily delivery count exceeds the quota, further messages are throttled.
Push QPS limit
Xiaomi Push tiers the push rate (QPS) primarily based on the number of users who have enabled the app's notifications.
QPS: Requests per second. Each request can target up to 1,000 devices. For example, at 3,000 QPS, you can reach up to 3 million devices per second.
QPS tiers are based on the number of devices with notifications enabled:
Enabled notification switches | QPS |
≥ 10,000,000 | 3,000 |
5,000,000–9,999,999 | 2,500 |
1,000,000–4,999,999 | 2,000 |
100,000–999,999 | 1,000 |
< 100,000 | 500 |
Xiaomi is not currently accepting requests to increase QPS.
Application listing restrictions
Xiaomi requires that your app be published before you can enable its push service.
Message classification
If your push quota is insufficient, consider optimizing your push policy. If your messages qualify as private messages, you can apply for the private message channel. Once approved, these messages are not subject to push quotas.
The Xiaomi channel supports a maximum of 8 channels per application. Please plan accordingly.
Message category
According to the Xiaomi Push message classification policy, Xiaomi Push classifies messages into two categories: private message and public message. If an app is not configured for private or public messages, Xiaomi Push routes them through the default channel.
Private message: Push and delivery volumes are unlimited. For details, see Private message use cases. Application required. To apply, see How to apply for and integrate a channel.
Public message: Push and delivery volumes are limited. For details, see Public message quota rules. Application required. To apply, see How to apply for and integrate a channel.
Default: This setting applies if you do not apply for a private or public message channel. It imposes the strictest limits: only one message can be delivered per application, per device, per day.
If you need a higher message quota, for example, to handle a high volume of complaints about undelivered messages, you can also request a quota increase from Xiaomi Push. For instructions, see Xiaomi Message Volume Appeal.
Message classification
Prerequisites: Complete Android SDK integration (3.x) and Xiaomi channel integration.
Once your application for Xiaomi self-classified messages is approved, the system automatically generates a channel_id for each message category. You can use the EMAS console and OpenAPI to push classified messages.
EMAS Console push
To send a push notification using the EMAS console push service, navigate to vendor settings - notification channel and notification category, select the Xiaomi channel, and enter the approved channel_id. If you leave this field blank, the push service uses the default channel.

OpenAPI push
To call the advanced push API, specify the following parameters:
AndroidNotificationXiaomiChannel is the channel_id assigned after your message classification request is approved. Omit this parameter to use the default channel.
Private message template
Application template
According to the Update on New Regulations for Xiaomi Message Templates, new rules take effect at 00:00 on July 1, 2026. The final integration deadline is 23:59 on December 31, 2026. All private messages must include both a channel_id and a template ID to be delivered. If you have an existing integration for Xiaomi private messages, you must upgrade it by December 31, 2026, to avoid message delivery disruptions.
Once your application for a Xiaomi private message template is approved, you can push private messages. To learn how to apply and integrate, see the Xiaomi Push private message template integration guide.
Private message template
To send a push using the PushV2 or MassPushV2 APIs, specify the parameters under PushTask.Notification.Android.Options.Xiaomi in the PushTask object:
ChannelThe channel_id obtained from your approved channel application. Required when using a Xiaomi private message template.TemplateIdThe ID of the Xiaomi private message template.TemplateParamsThe parameters for the Xiaomi private message template, formatted as a JSON object string.
Use the following parameters to push with the Push or MassPush APIs:
AndroidNotificationXiaomiChannelThechannel_idfor your approved Xiaomi notification channel. This is required when pushing notifications with a Xiaomi private message template.AndroidXiaomiTemplateIdThe ID of the Xiaomi private message template.AndroidXiaomiTemplateParamsThe parameters for the Xiaomi private message template, formatted as a JSON object string.
Specifying a template ID requires the Xiaomi channel. Template parameters, in turn, require a template ID.
OPPO
Push limits
To improve the user notification experience and maintain a healthy push ecosystem, OPPO PUSH controls the push volume and push rate (QPS). If the push volume or QPS exceeds the push limit, the OPPO platform throttles the service and returns an error message via the message receipt. Adhere to the push limits when sending messages. For more information, see the OPPO PUSH service limitations.
Push limit
OPPO Push has two permission types: formal permission and test permission. The new message classification includes two categories: Communication and Service and Content and Marketing. If your app has not integrated the new message classification, it uses the legacy categories: Private Message and Public Message. The limits are as follows:
Push permission | Message type | App category | Total daily limit | User daily limit |
Official permission (the app is listed on the OPPO App Store) | Communication and Service (formerly private message) | / | Unlimited | Unlimited |
Content and Marketing (formerly public message) | News (level-3 category is News) | 20,000 per day if cumulative users < 10,000; cumulative users × 2 per day if cumulative users ≥ 10,000. | 5 messages | |
Other app types | 2 messages | |||
Test permission (the app is not listed on the OPPO App Store) | Communication and Service (formerly private message) | / | Not supported | |
Content and Marketing (formerly public message) | / | 1,000 | 2 messages | |
Cumulative user count: The total number of users of an application integrated with the push service who have installed, activated, and enabled the master notification switch within the last 30 days, excluding users who have uninstalled the application. This data is updated daily, and you can query it on the OPPO Push Operations Platform.
If an application is unpublished on the OPPO App Store, you must apply for test permission and add test devices.
Applications with official push permission can also add test devices on the OPPO Push Operations Platform under configuration management > test device. The push limit per device does not apply to messages sent to these test devices.
Push qps limit
OPPO PUSH applies different QPS limits based on an application’s cumulative user tier.
QPS (Quantity per second) is the maximum number of users you can send OPPO PUSH notifications to per second. For example, an application-level rate limit of 3,000 QPS means your application can send notifications to up to 3,000 users per second. All interfaces share this application-level rate limit.
Total users | QPS |
≥ 10 million | 5,000 |
≥ 5 million and < 10 million | 3,000 |
< 5 million | 2,000 |
Message categories
OPPO currently offers both new and legacy message classification methods. Applications that enabled OPPO Push before November 20 can choose to use either the new message classification method or the legacy self-built channel. Starting November 20, applications that enable OPPO Push for the first time must use the new message classification capability, as the legacy self-built channel is no longer supported. To ensure successful delivery, messages must include the new message classification field.
If your push quota is insufficient, optimize your push policy. Depending on the message type, apply for permissions for the new message category or private message channel. Using these channels makes your content, marketing, and official channels more efficient.
Updated message classification
OPPO Push has optimized its message delivery channels and message classification, and will launch a new message classification method on October 31, 2024.
New message classification
According to the OPUSH Message Classification Rules, OPPO now categorizes notifications into two main categories: Communication and Services, and Content and Marketing. If the Communication and Services category is not specified, messages will default to Content and Marketing. Values and notification behaviors differ depending on the message type:
Message category | Type |
| Notification method |
|
Communications and services | instant messaging, audio, and video calls | IM | Default: notification bar and lock screen. This can be upgraded to a high-priority notification method, which adds a banner, ringtone, and vibration. (Application required. See High-priority Notification Application for details.) |
|
personal account and asset changes | ACCOUNT | |||
personal device reminder | DEVICE_REMINDER | |||
personal order/logistics status changes | ORDER | |||
personal schedule/to-do | TODO | |||
personal subscription | SUBSCRIPTION | |||
Content and marketing | news and information | NEWS | Appears only in the notification bar. | The value is 1. |
content recommendation | CONTENT | |||
platform promotion | MARKETING | |||
social update | SOCIAL |
OPPO's new message classification: Application
To use the new message category capability, you must enable it on the OPPO Push Platform. For details, see 3. New message category integration process in the Message Category Rules. After you enable this feature, messages default to the new message category format. Evaluate the impact before proceeding.
If you do not integrate the communication and services category, your messages will default to the content and marketing category, which requires no application.
If you need to send messages in the communication and services category, you must apply for permission online. For details, see 4.1 Default notification application in the Message Category Rules. After your application is approved, the OPPO Push Platform automatically adds the communication and services message category. By default, these notifications appear on the notification bar and lock screen. If you have already enabled permissions for the legacy private message channel, you do not need to reapply.
If you integrate the communication and services message category and also require high-priority notifications, you can submit an application as described in 4.2 High-priority notification application in the Message Category Rules. High-priority notifications appear on the notification bar, lock screen, and as a banner, and include sound and vibration. Because these notifications can be disruptive to users, apply for and use them with caution.
The new OPPO message classification feature currently supports OS 13 and later. Support for OS 12 and earlier versions will be rolled out gradually.
New message category
Prerequisites: You have completed Android SDK integration (3.x) and OPPO channel integration.
After your application for the new OPPO message classification permission is approved, you can use OpenAPI to send categorized messages. We recommend specifying AndroidMessageOppoCategory along with the legacy channel ID to reach users on older OS versions.
OpenAPI push method
When calling the advanced push API, pass the following parameters:
AndroidMessageOppoCategory: Specifies the value for the category parameter in OPPO's new message classification.
AndroidMessageOppoNotifyLevel (optional): Specifies the value for the notify_level parameter in OPPO's new message classification. If you use this parameter, you must also specify the AndroidMessageOppoCategory parameter.
Legacy channel message classification
Legacy channel message classification
The OPPO Message Classification Guidelines define two message categories: private message and public message. If an app has not integrated message classification, its messages default to the public message category and are subject to its rules. The private channel has no limits on push or delivery volumes.
Message type | Configuration method | Value |
private message | Create a channel in your app. After your application is approved, register it on the OPPO Push Platform and set its attribute to private message. | channel ID |
public message | Enabled by default | / |
Requesting direct messages:
Follow the instructions in Setting up Android 8.0 Notification Channels to create a notification channel in your app's code and assign it a channel ID. Then, release the app version containing the new channel.
Email OPPO to have the channel designated as a private message channel. For instructions, see the OPPO Private Message Email Template.
Register the channel on the OPPO Push Platform and set its attribute to private message.
Once a channel ID is set, it cannot be changed or deleted.
When creating a private message channel, see Channel adaptation.
The private message channel permissions take effect only after the channel is created and released on the client, registered on the OPPO Push Platform, and the email request for these permissions is approved.
Within the Android 8.0 notification channel settings, the code sample for creating a channel includes feature settings, such as vibration and sound. These settings apply only to notification channels on Android 8.0 and later. To configure these features for the OPPO offline channel, you must use the custom notification style interface (3.x).
Legacy channel message classification
Prerequisites: You have completed Android SDK integration (3.x) and OPPO vendor channel integration.
Once the OPPO private message channel permission is enabled, you can use the EMAS console and OpenAPI to send messages by category.
EMAS console push
To send a push notification using the EMAS console's push service, configure the following:
Under vendor settings - notification channel and notification category, select OPPO channel.
Under push settings, if you specify a channel ID, offline notifications are sent through the OPPO private message channel. If you do not specify a channel ID, offline notifications are sent through the OPPO public message channel by default.

OpenAPI push
When calling the Advanced Push API, pass the AndroidNotificationChannel parameter. This parameter serves two purposes:
When the app is online, the Alibaba Cloud channel delivers messages. The AndroidNotificationChannel parameter specifies the notification channel created by the client.
When the app is offline, the OPPO third-party channel delivers messages. The AndroidNotificationChannel parameter specifies the OPPO private message channel that you applied for.
Direct message template
Application template
OPPO requires new users to push Communication and Service messages (formerly private messages) using message templates. Existing users must migrate by December 31, 2025. To integrate private message templates, see the OPUSH private message template validation capability integration guide.
Direct message template
Once your private message template is approved, you can use the PushV2 and MassPushV2 interfaces to send pushes. The relevant parameters are in the PushTask object at PushTask.Notification.Android.Options.Oppo:
PrivateMsgTemplateIdID of the private message template.PrivateTitleParametersParameters for the private message template title.PrivateContentParametersParameters for the private message template content.
To send a push using the Push interface, use the following parameters:
AndroidOppoPrivateMsgTemplateIdThe private message template ID.AndroidOppoPrivateTitleParametersThe title parameters for the private message template.AndroidOppoPrivateContentParametersThe content parameters for the private message template.
vivo
Push limits
Daily push limit
According to the Push message limits, vivo Push classifies messages into two main categories: system message and operational message. If message classification is not integrated, messages default to operational message. Different categories have different limits:
Message classification | Application category | Total push limit | Limit per user |
system message | / | 3 times the number of active users with notifications enabled (You can apply for an unlimited message quota.) | Unlimited |
marketing message | News & Information (Requires an Internet News Information Service License, and your app must be in the "News & Information" category. To apply, see the News App Volume and Frequency Permission Application.) | 3 times the number of active users with notifications enabled | 5 messages |
Others | 2 times the number of active users with notifications enabled | 2 messages | |
test message | For applications under review on the vivo platform, push permissions are "Restricted". With restricted permissions, you can only send test messages via API to a maximum of 20 test devices. These test messages are exempt from volume and frequency capping. | ||
Active users with notifications enabled are users who have enabled notifications for an application integrated with the vivo channel and whose device has been online in the past 14 days.
If there are fewer than 10,000 active users with notifications enabled, the operational message quota defaults to 10,000.
You can check the number of active users with notifications enabled and the available operational message quota in the vivo push operations console.
The push limit is based on deliveries. If daily deliveries exceed the limit, the system applies throttling.
Application publishing restrictions
If an application is not available on an app store, its push permission is displayed as Limited. This status does not permit sending production messages, but only allows sending push notifications to test devices.
An application published to an app marketplace has production push permissions and can send production messages as well as test messages to test devices.
Push time limit
To avoid disturbing users, the server only pushes messages to vivo phones between 7:00 and 23:00. System messages are exempt from this restriction. If you send an operational message outside this time window, the server returns error code 10071 and does not deliver the message.
Push content limitations
1. Test messages: Limited to English letters and numbers
The API restricts content to prevent developers from accidentally sending test messages to users during debugging.
Note: Test messages and production messages follow the same rules. The test identifier includes the Chinese characters '测试' and the English word 'test'.
System message | Operational message | |
Secondary category: IM | Secondary category: Not IM | |
No content restrictions | The following content is blocked: Symbols only Symbols and numbers The word 'test' combined with symbols The word 'test' combined with numbers The word 'test' combined with symbols and numbers JSON format | The following content is blocked: Numbers only Symbols only Symbols and numbers The word 'test' combined with symbols The word 'test' combined with numbers The word 'test' combined with symbols and numbers JSON format (Note: Messages that contain the word 'test' and Chinese characters are allowed.) |
2. Restrictions on Duplicate Operational Message Interception
The vivo platform does not allow pushing duplicate operational messages. Avoid targeting the same audience with the same copy more than once within a calendar day.
The client's deduplication mechanism prevents the same device from receiving duplicate operational messages within a single calendar day. (This does not apply to system messages.)
Push QPS limit
The vivo push QPS automatically adjusts based on the number of active users with notifications enabled, with a default range of 3,000 to 5,000/s.
QPS is the maximum number of users you can push to per second. For example, a QPS of 3,000 allows a maximum of 3,000 API calls per second for a single push, or 30 API calls per second for a list push that targets 100 users per request.
Valid users | Push rate |
0–5 million | 3,000 |
5–8 million | 4,000 |
>8 million | 5,000 |
Message classification
As described in the Push message classification overview, vivo Push has two main message categories: system message and operational message; unclassified messages default to operational messages and are subject to their rules.
Message classification
Top-level category:
The system message and operational message categories do not require you to apply, but you must ensure that your push content complies with vivo's definitions for categorized messages.
vivo performs regular inspections. Sending operational messages through the system message channel is prohibited. If you fail to comply with the defined scenarios, you will be subject to strict penalties. For more information, see vivo's operational supervision and penalties.
The default quota for an application's system messages is three times the number of its active users with notifications enabled. If you need a higher quota, you can apply for unlimited system messages through the vivo ticket system.
To apply for the unlimited system message permission, you must integrate with secondary message classification and provide the required information. The platform evaluates your application based on your message classification. For subscription reminder messages, you must first obtain system message archive permission and then apply for the unlimited system message permission. For more information, see the vivo Push Service Ticket Operation Guide.
Subcategory:
If a secondary message category in the table below matches your app's push scenario, you can use it directly. If the message is a subscription message, you need to request system message archiving through the ticketing system. See vivo Push Service Ticket Operation Guide.
If none of the secondary message categories in the table below matches your app's push scenario, email the vivo team to request special classification parameters. You can only use them after vivo approves your request.
Level-1 category | Level-1 value | Level-2 category | Level-2 value | Notification method |
System message | AndroidNotificationVivoChannel: 1 | Instant message | IM | Banner, lock screen, ringtone, and vibration. |
Account and assets | ACCOUNT | |||
To-do | TODO | |||
Device information | DEVICE_REMINDER | |||
Order and logistics | ORDER | |||
Subscription reminder | SUBSCRIPTION | |||
Promotional message | AndroidNotificationVivoChannel: 0 | News | NEWS | Displays silently in the notification shade only. |
Content recommendation | CONTENT | |||
Marketing campaign | MARKETING | |||
Social update | SOCIAL |
Message categories
Prerequisites: Android SDK integration (3.x) and vivo vendor channel integration.
Once vivo approves your categorized message application, you can use the EMAS console and OpenAPI to send categorized push notifications.
EMAS console
To send push notifications using the EMAS console push service, go to vendor settings - notification channel and notification category, select the vivo channel, and select the appropriate message type.

OpenAPI push method
When calling the Advanced Push API, pass the corresponding parameters:
AndroidNotificationVivoChannel: Specifies the primary category value. Use 0 for an operational message (default) or 1 for a system message.
AndroidMessageVivoCategory: Specifies the secondary category value, which must follow the message classification rules and be in uppercase.
We recommend only passing a value for the AndroidMessageVivoCategory parameter and omitting the AndroidNotificationVivoChannel parameter.
If you also pass a value for the AndroidNotificationVivoChannel parameter, ensure the value of AndroidMessageVivoCategory corresponds to the specified AndroidNotificationVivoChannel. Otherwise, the API will report an error.
Message templates
Apply for a template
vivo requires that five categories of system messages—Subscription Reminders, Account and Assets, Schedule and To-Dos, Device Information, and Orders and Logistics—use message templates. This requirement does not apply to operational messages or instant messages. For legacy applications, starting April 1, 2027, messages in these five system message categories will not be delivered unless they use a message template. For detailed rules and integration steps, see the vpush message template integration guide.
Log in to the vivo Push Operation Platform, select your application, and go to vpush Template Management. To obtain an available template ID, select an official template or apply for a custom template. Custom templates must be approved before use.
For subscription reminder messages, you must also create and bind a subscription channel and set up client subscription authorization as described in the integration guide. Simply configuring server-side template parameters is insufficient for this integration.
Push using a message template
Once your template is approved, when you call the PushV2 API, set the following parameters under PushTask.Notification.Android.Options.Vivo. When you call the MassPushV2 API, set them under Notification.Android.Options.Vivo for each task in the PushTasks array:
TemplateId: The vivo message template ID. Type: string.TemplateParams: The vivo message template parameters, specified as a stringified JSON object. The keys are the variable names defined in the template, and the values are their corresponding content.
The following example shows the parameter format for vivo. Use your actual template ID and replace all variable names and values to match your template:
{
"TemplateId": "your-template-id",
"TemplateParams": "{\"keywords1\":\"SampleOrderNumber\",\"keywords2\":\"SampleStoreName\"}"
}When you call the Push API, set the following request parameters. For the MassPush API, set these parameters for each task in the PushTask array:
AndroidVivoTemplateId: The vivo message template ID.AndroidVivoTemplateParams: The vivo message template parameters, specified as a stringified JSON object. The format is the same as for theTemplateParamsparameter described above.
When you pass template parameters, you must also include the template ID and values for all variables defined in the template. Variable names do not include the double curly braces from the template. The template itself determines the message category, so you do not need to specify the vivo message classification parameters.
Public parameters such as the title and content must still be specified as required by the API. The platform generates the notification's title and content from the template and its parameters.
If you set both the vivo atomic notification parameters and a template ID, the system prioritizes the atomic notification and ignores the template configuration.
Other settings
Test message
1. To call the advanced push API, set the following parameters:
AndroidVivoPushMode = 1: Enables direct push, allowing each application to send up to 500 daily test messages that do not count toward the daily push limit.

AndroidTargetUserType=1: This setting is equivalent to setting the AndroidHuaweiTargetUserType, AndroidHonorTargetUserType, and AndroidVivoPushMode parameters.

2) When sending notifications using the push service in the EMAS console, disable production notifications for the vivo channel in vendor settings.

Meizu
Message classification
Meizu Push classifies messages as either "private message" or "public message". Unclassified messages default to public messages. For details, refer to the Meizu Push Message Classification Guide.
Type | Push content | Push quota |
Private message |
| Unlimited |
Public message |
| The daily push quota varies by application category. See the "Push limit - push quota" section for details. |
Push parameters
When pushing with the PushV2 and MassPushV2 APIs, specify the parameters in PushTask.Notification.Android.Options.Meizu:
NoticeMsgType0: Public message (default)
1: Private message
When using the Push interface, specify the following parameters:
AndroidMeizuNoticeMsgType0: Public message (default).
1: Private message.
Push limits
For limits on the Meizu Push Service, such as message volume and push rate, see Meizu Push message limits.
Push message limit
The daily push limit for public messages per device is as follows:
Secondary category | Tertiary category | Daily notification limit |
News & Reading | news and information (Requires an Internet News Information Service Permit) | 5 |
Categories that lack an Internet News Information Service Permit, such as e-book, magazine, audiobook, anime and comics, humor, sports, and classifieds | 3 | |
casual puzzle strategy and simulation sports and racing board and card role-playing Video & Entertainment system tools communication and social Education Photo & Video Lifestyle Navigation Shopping Business kids zone Finance Health & Fitness | All | 3 |
other | All | 3 |
To request a higher push quota, contact Meizu Push at push_support@dreamsmart.com.
Push rate and limits
Each application has the following default limits: a push rate of 10,000 devices per 10 seconds, a maximum of 100 tags, and a daily limit of 1,000 pushes.
The API has a default daily limit of 10,000 push tasks.
If a device receives four or more messages from the same application, the messages will be collapsed. On system versions prior to Flyme 10, repeatedly untapped messages are moved to the message box in the upper-right corner.
If a device remains inactive for 30 days, the system automatically unsubscribes it.
Push limits
The Google channel does not distinguish between message types, but there are limits for each application and device:
Per application | 1,500,000 messages per minute |
Per device | 1,000 messages per minute |
Channel limits
Google has deprecated the legacy Firebase Cloud Messaging API (which succeeded Google Cloud Messaging, or GCM). To send notifications through the Google push channel, use the latest Firebase Cloud Messaging (FCM) HTTP v1 API. For integration details, see Google push channel integration.
If you still use the legacy GCM channel to send notifications, the Google channel will no longer accept your messages. Upgrade immediately to prevent delivery failures. For instructions, see the Firebase channel upgrade guide.
HarmonyOS
Push restrictions
Per the HarmonyOS push management rules, HarmonyOS categorizes notification messages into two main categories: Service and Communication, and News and Marketing. Each category has a different receive limit for the HarmonyOS channel.
Type | Push limit | Per-user limit |
Service and communication category | Unlimited | The daily limit of 3,000 messages per device for each app is a combined total that includes content, marketing, and other scenario-based messages. |
Content and marketing category | Unlimited | News category: 5 messages (requires an Internet News Information Service License) Other category: 2 messages |
Message classification
HarmonyOS categorizes notification messages to improve the end user's notification experience and foster a healthy, sustainable notification ecosystem.
Message classification
According to the HarmonyOS notification category standard, HarmonyOS classifies notifications into two categories: Service and Communication and Information and Marketing. If a notification category is not specified, HarmonyOS classifies your push notifications as Information and Marketing by default, and they are subject to push notification limits:
Follow the application process in Apply for the self-classification privilege for HarmonyOS notification messages to apply for one or more message types that meet your business needs.
For the HarmonyOS channel, the following table lists the supported
categoryvalues for the self-classification privilege and their corresponding notification methods.
Primary category | Secondary category | Type | Value | Notification method |
services and communications | social communication | IM | IM | Displays on the lock screen and triggers a ringtone and vibration. |
VoIP | VoIP | |||
service reminders | subscription | subscription | ||
travel | travel | |||
health | health | |||
work | work | |||
account | account | |||
express | express | |||
finance | finance | |||
device reminder | device reminder | |||
information and marketing | content and information | financial updates | MARKETING | Appears only in the notification shade, without sound or vibration. |
lifestyle information | ||||
survey | ||||
other | ||||
content recommendation | ||||
news | ||||
social updates | ||||
marketing campaigns | feature recommendation | |||
promotional campaign | ||||
product promotion |
Message classification
Prerequisites: The HarmonyOS SDK and a vendor channel have been integrated.
With an approved HarmonyOS self-classification entitlement, you can use the EMAS console and OpenAPI to push classified messages.
EMAS console push
When using the EMAS mobile push service to send notifications to a HarmonyOS application, select the corresponding notification category in the HarmonyOS settings.

OpenAPI push method
When calling the Advanced Push API, pass the appropriate parameters.
HarmonyCategory: The value of the category parameter for the HarmonyOS channel.
Alibaba Cloud proprietary channel
When a device is online, messages are sent via the Alibaba Cloud channel. Notification behavior is controlled by HarmonyOS notification channels, which are configured with the SlotType parameter. The available values and their descriptions are as follows:
SlotType | Category | Value | Description |
SOCIAL_COMMUNICATION | social communication | 1 | Enables notifications with an icon in the status bar, a banner, and sound. |
SERVICE_INFORMATION | service information | 2 | Enables notifications with an icon in the status bar and sound, but no banner. |
CONTENT_INFORMATION | content information | 3 | Enables notifications, but without an icon in the status bar, a banner, or sound. |
CUSTOMER_SERVICE | customer service | 5 | This type is for user-initiated customer service messages between a user and a merchant. Enables notifications with an icon in the status bar, but without a banner or sound. |
OTHER_TYPES | other | 0xFFFF | Enables notifications, but without an icon in the status bar, a banner, or sound. |
Prerequisite: You have integrated the HarmonyOS SDK.
Create a notification channel on HarmonyOS. For more information, see HarmonyOS development steps.
After creating the channel, you can use the EMAS console and OpenAPI to push categorized messages:
Using the EMAS console
When pushing messages from the EMAS console through the Alibaba Cloud online notification channel, select the corresponding notification channel type in HarmonyOS Settings.

Using the OpenAPI
When calling the Advanced Push API, set the HarmonyNotificationSlotType parameter to the corresponding SlotType value from the preceding table.
Other settings
Send test message
1) When you call the advanced push API, set HarmonyTestMessage to true. You can push up to 1,000 test messages per project.

2) When using the EMAS console push service to push an application notification to a HarmonyOS app, enable test messages in HarmonyOS settings.
To improve user experience and resource efficiency, we have introduced a series of optimizations for our data processing service. These optimizations address two main areas. First, the original scheduling algorithm allocated resources imprecisely, causing some nodes to be overloaded while others remained idle. Second, for data querying, the old engine's performance was slow when dealing with large datasets. For example, queries on 100GB and 200GB tables took approximately 5 and 12 minutes, respectively. Because the system lacks detailed data distribution statistics, the query planner often makes suboptimal choices.
Recommendations
To improve the delivery rate, guide users in your app to enable notification subscriptions and push notifications, and apply for the vendor self-classification privilege.
Classify messages to prevent critical messages from consuming the non-critical message quota or ending up in a non-critical message list.
Consider converting non-critical messages into optional subscriptions.
In non-activation scenarios, reduce pushes to inactive users to avoid wasting resources on ineffective deliveries.
Limit your push frequency to avoid disturbing users and prompting them to disable the notification permission.
Increase quotas through subscriptions
Sending too many operational messages (such as marketing and public messages) can quickly exhaust the daily quota for a single device on a vendor channel. In contrast, system messages (such as service and communication messages or private messages) have no quota. To send more messages to a single device, classify them accurately and prioritize sending system messages to preserve the quota for operational messages. To do this, implement a user subscription mechanism in your app. Requirements for user subscriptions vary by vendor channel:
Vendor channel | Category name | OpenAPI parameter | Description |
Huawei | Service and Communication → service reminder → subscription |
| Content that users actively subscribe to and agree to receive via push notification. Subscriptions are only available for the following use cases. Huawei does not support applications for other use cases.
Note To request subscription messages, you must meet all the following requirements and provide complete screenshots as proof:
|
Honor | Service and Communication → service reminder → subscription |
| Content that users subscribe to and activity reminders they set.
The push notification content must state that the message is based on a user's subscription. For example, the message title or body should include phrases like "Subscription Message" or "Your subscription to [item]". Note: Subscription must be a user-initiated action. Do not send push notifications to users who have not subscribed. |
Xiaomi | private message → personal subscription |
| User-initiated subscriptions: alerts for followed market trends; reminders for when a followed streamer goes live; updates from a specially followed account or author; updates for paid subscription content. Note To request subscription messages, you must meet the following requirements and provide complete proof:
|
OPPO | New message classification→ personal subscription |
| Reminders that a user actively sets and consents to receive via push notification, such as: 1. Reminders for live streams and book updates; 2. Alerts for price drops on products or flights, and group-buy deal reminders; 3. Alerts for followed market trends; 4. Check-in reminders set by the user; 5. Updates for paid subscription content. Note To request this message type, you must meet the following requirements and provide complete proof: 1. Your application must support "subscribe" and "unsubscribe" functions, and the UI must display text such as "Subscribe" or "Reserve." 2. Subscription must be a user-initiated action; do not send push notifications to users who have not subscribed. 3. After a user subscribes, the application's UI must clearly state that they will receive related push notifications, for example, "You will receive push notifications for [item]." 4. The scope of a subscription must be specific and not overly broad, for example, subscribing to "market news" is considered too broad. |
Legacy private message → Updates on a topic manually followed by the user |
|
Note:
| |
vivo | system message → subscription reminder |
| Messages that a user actively subscribes to and expects to receive at a specific time:
Note To request subscription messages, you must meet the following requirements, provide complete proof, and complete the system message archiving process:
|
HarmonyOS | Service and Communication → service reminder → subscription |
| Content that users actively subscribe to and agree to receive via push notification. Subscriptions are only available for the following use cases. HarmonyOS does not support applications for other use cases.
Note To request subscription messages, you must meet all the following requirements and provide complete screenshots as proof:
|
The requirements for each vendor channel are as follows:
Users must explicitly consent to subscribe, and an unsubscribe option must be provided. Upon subscribing, users must be notified that they will receive push notifications. The call-to-action for subscribing cannot use vague copy like "follow."
Subscription content must not be overly broad and should be organized by category.
The push notification's copy must clearly indicate that it is a subscription-based message.
Activity pushes over full pushes
To stay within the push volume limits for operational messages on vendor channels and to reduce costs, we recommend avoiding large-scale pushes. A better approach is to push based on device activity. The general idea is to tag each device with an activity level and then send pushes to the corresponding tags. Consider the following method:
When the app starts, query the tags on the current
deviceto check if the currentactivity tagexists. For example, atagsuch astag202403can represent the year and month. You can also apply tags weekly. However, if you apply tags daily, be aware of the limit on the number of tags in atag expression.If the
devicedoes not have the currentactivity tag, apply it.On the server-side, when calling the
push API, use a tag expression to target specific devices. For example:TargetValue={"and": [{"tag": "tag202402"}, {"tag": "tag202403"}]}.To prevent accumulating too many
tags, periodically delete expired ones. For example, on a monthly basis, deleteactivity tags that are more than 24 months old.
Invalid device deletion
Enable the receipt log to diagnose sent_fail or arrive_fail errors, and remove invalid devices to improve OpenAPI efficiency. For receipt error codes, see Partial error codes and causes for the Mobile Push vendor channel.
