Create a simple push message

Simple push sends a message to a single target. You can customize the content or use a predefined template.

Custom content suits small-scale scenarios such as testing an Apple push certificate or verifying Android SDK integration. Templates suit repeated pushes to multiple targets. Create a template-based push in the console to test the template feature before using it at scale.

Complete the following steps to create a simple push message.

Prerequisites

• The MPS SDK for iOS is integrated (iOS SDK integration), and the Apple push certificate is configured on the Channel Configuration page. For more information, see Channel Configuration.

• The MPS SDK for HarmonyOS is integrated (HarmonyOS SDK integration), and the HarmonyOS push certificate is configured on the Channel Configuration page. For more information, see Channel Configuration.

• The MPS SDK for Android and relevant vendor channels are integrated (Android SDK integration), and push channel configurations are completed on the Channel Configuration page (Configure Android push channels).

Procedure

1. Log on to the mPaaS console, select the target application, and choose Message Push Service > Message Management.

2. Click Create Message Push Task. In the dialog box that appears, select the Simple Push tab.

3. On the Simple Push tab, configure the push message parameters:

   Parameter	Required	Description
   Message type: Silent	Yes	Specifies whether to display the message: Yes: Silent message. Not displayed on the target device in any form. No: The message is displayed in the notification bar. On Android, behavior varies by push channel: MPS channel: The value is sent to the client as a reference field. Parse the message body to get the value and control display accordingly. Vendor channel: The vendor system parses the field and controls message display automatically. On iOS and HarmonyOS, message display is controlled by the vendor system. No other action is required.
   Message content creation method	Yes	Supports two creation methods: Create: Customize the message content, including the title, body, and display style. Use template: Use a pre-created push template.
   Push template	Yes	Select a template from the Message Template page of the current application. Note This parameter is required only when Message content creation method is set to Use template.
   Template placeholder	Yes	Enter values for the template variables. The system displays input fields based on the placeholders in the selected template.
   Push dimension	Yes	Select the push dimension: Users: Push by user ID. Call the binding API to map user IDs to device IDs (Client API). Android: Push by Android device ID. iOS: Push by iOS device ID. HarmonyOS: Push by HarmonyOS device ID.
   User/Device ID	Yes	Enter the corresponding user ID or device ID based on the selected push dimension. For Android, enter the Ad-token. For iOS, enter the Device Token. For HarmonyOS, enter the Device Token. For Users, enter the user ID (the userid value passed when calling the binding API). Remove any spaces from device IDs obtained from logs or other sources.
   Push priority of Android message channels	Yes	Android only. Options: Vendor channels preferred: Messages are sent through integrated vendor channels when available. For non-integrated vendor channels, messages are sent through the MPS channel. MPS channel: Messages are sent through the MPS channel only. This parameter applies to Android only. iOS and HarmonyOS use vendor channels by default.
   Display style	Yes	Message display style on the client: Default: Shows the title and text. Best for simple messages. Maximum 100 characters, including custom parameters and symbols. Big Text: Shows the title and extended text, allowing users to read without opening the app. Best for longer messages such as news or updates. Maximum 256 characters, including custom parameters and symbols. Rich text: Supports messages with icons and large images. Best for visual content. Keep the text to two lines or fewer. Note Required only when the content creation method is Create.
   Message title	Yes	Enter the message title. Use the preview area on the right to check the display. Note Required only when the content creation method is Create.
   Message content	Yes	Enter the message body. Use the preview area on the right to check the display. Note Required only when the content creation method is Create.
   Icon	No	Notification bar icon displayed to the right of the message content. Supports JPG, JPEG, and PNG formats. Enter a publicly accessible URL. If only a default URL is provided, the system uses it for all vendor channels. Upload channel-specific assets for optimal display. Default icon: Recommended size is 140 × 140 px, within 50 KB. OPPO icon: Recommended size is 140 × 140 px, within 50 KB. Xiaomi icon: Recommended size is 120 × 120 px, within 50 KB. Huawei icon: Recommended size is 40 × 40 dp, within 512 KB. FCM icon: No specific configuration requirements. The system automatically pulls the default icon for adaptation. Note Required only when the content creation method is Create and Display style is Rich Text.
   Large message image	No	Large image displayed below the message content in the notification bar. Enter a publicly accessible URL. If only a default URL is provided, the system uses it for all vendor channels. Upload channel-specific assets for optimal display. Default large image: Recommended size is 876 × 324 px, within 1 MB. Supports JPG, JPEG, and PNG formats. OPPO large image: Recommended size is 876 × 324 px, within 1 MB. Supports JPG, JPEG, and PNG formats. Xiaomi large image: Recommended size is 876 × 324 px, within 1 MB. Supports JPG, JPEG, and PNG formats. iOS large image: User-defined image with no size restrictions. FCM large image: No specific configuration requirements. The system automatically pulls the default icon for adaptation. HarmonyOS channel large image: Recommended size is less than 25000 px. Supports PNG, JPG, JPEG, HEIF, GIF, and BMP formats. Note Required only when the content creation method is Create and Display style is set to Rich Text.
   Push time	Yes	Select when to push the message: Now: Push the message immediately once the message push task is created. Scheduled: Specify a time to push the message. For example, push the message at 8:00 am on June 19th. Cyclic: Push the message at a specific time cyclically within a period. For example, push the message at 8:00 am every Friday from June 1st to September 30th.

   Use the Push Preview area on the right to preview the Notification, Apple Message Body, Android Message Body, and HarmonyOS Message Body for each platform.

4. (Optional) Configure the following advanced settings:

   • Redirect upon click: Action performed when a user taps the notification. This value is sent to the client as a reference field for you to implement.

     • Web page: Users will be redirected to a Web page.

     • Custom page: Users will be redirected to a native page.

   • Redirection address: The destination page when a user taps the notification.

     • For Web page, enter the target URL.

     • For Custom page, enter the native page address (Android: ActivityName; iOS: VCName).

   • Custom message ID: A system-generated unique identifier for the message. You can customize it. Maximum 64 characters.

   • Note

     You only need to configure a custom ID if the message type is silent.

   • Validity period: Message retention time in seconds. If delivery fails because a device is offline or a user is logged out, MPS retries within this period when the device reconnects or a new binding request is made. Default: 180 seconds.

     Note

     The message validity period cannot be shorter than 180 seconds or longer than 72 hours.

   • Extension parameters: Turn on the switch, click Add parameter, set the key-value pair, and click any area to save. Extension parameters are passed to the client with the message body. Three types are available:

     • System extended parameters

       System-reserved parameters with fixed values: notifyType, action, silent, pushType, templateCode, channel, and taskId.

     • System extended parameters with special meanings

       System-reserved parameters with configurable values:

       Parameter	Description
       sound	Custom ringtone file path. Effective only for Xiaomi and Apple devices.
       badge	Application icon badge number. For Android, you must handle the badge logic in your app. For Apple devices, the system automatically displays the configured badge value on the app icon.
       mutable-content	APNs custom push identifier. Including this parameter in a push indicates support for UNNotificationServiceExtension in iOS 10. If this parameter is not included, it is a normal push. Set the parameter value to 1.
       badge_add_num	The number to add to the badge for Huawei channel pushes.
       badge_class	The application's entry Activity class corresponding to the desktop icon for the Huawei channel.
       big_text	Enables big text style. Set to 1. Effective only for Xiaomi and Huawei devices.

     • User-defined extended parameters

       Custom key-value pairs sent with the message body for client-side processing.

   • SMS supplement service: Resends messages via SMS to users who did not receive the app push due to network issues, background restrictions, or delays. After enabling, configure the SMS signature, template, and resend policy.

     Note

     • Currently, the SMS supplement service is only available in the Hangzhou non-finance region.

     • If you are using the SMS supplement service for the first time, go to the SMS Supplement Service page and follow the prompts to activate Short Message Service. For more information, see Use the SMS supplement service.

     • SMS signature: A personalized signature in the text message. This must be configured in the Short Message Service console.

     • SMS template: The content of the text message to be sent. This must be configured in the Short Message Service console.

     • SMS supplement policy: Provides two policies: Concurrent and Resend.

       • Concurrent: Sends app push and SMS simultaneously. Use for large-scale broadcasts to ensure delivery.

       • Resend: Sends SMS only to users who did not receive the app push.

     • SMS template variables: If the selected template contains variables, specify their values. The system replaces the variables with the specified values before sending.

5. Click Submit. The created message appears in the simple message record list.

   You can also push messages through APIs (Server-side API reference).

Related operations

• Create a message - Multiple push

• Manage simple push messages

• Manage scheduled push task