This article is intended to guide users on how to create notification messages on the Engagelab console.
Create a Notification Message
Enter [Push] - [Create Push] - [Create a Notification Message] page to create a push task. The parameter configuration instructions are as follows:
- Title: the title of the pushed message. Avoid meaningless content such as test, test, and pure number. Otherwise, the notification message may be intercepted by the manufacturer and cannot be received.
- Content: the content of the pushed message. Avoid meaningless content such as test, test, and pure number. Otherwise, the notification message may be intercepted by the manufacturer and cannot be received.
- Sending Time: Select the time to send
- Immediately: Instant message delivery.
- Delayed: The sending time can only be set three minutes after the current time,and the scheduled task cannot exceed one year.
- Constant speed push: Complete push within the set time to reduce server pressure.
- Web: the address to be redirected after you click the notification.
Advanced Options (Optional)
- Time To Live: When a push message to a user, if the user is not online at present, it will be saved as an offline message, which will be pushed to the user the next time he is online.
- This value can be used to specify the duration of offline messages for. That is, within the time limit, users will continue to receive push when they go online, otherwise they will expire.
- The default duration is 1 day. If it is set to 0, it means that offline messages are not reserved, that is, only users who are currently online can receive them, and all those who are not online will not receive them.
- Additional fields: Used for client-side custom event handling.You can add or delete additional fields.
- Silent Notification: Turn on the non-aware function, and when website users receive new notification reminders, they can prevent default behaviors such as vibration, sound, and turning on the device display.
- Message Sending Strategy: You can specify the priority distribution policy for the system channel and the Engagelab channel.
- System channel distribution means that as long as the browser process exists in the operating system, the message can be delivered.
- Engagelab channel distribution means it is delivered through the websocket of Engagelab. It needs the user to open your site page.
- Notification Icon: Icon on the right side of the notification bar.
- The recommended size is 192 * 192px, and the maximum size is 1M.
- Supported formats: JPG, PNG, GIF. Chrome, Firefox, Opera, and Edge browsers are supported.
- Images can be network resources starting with http or https.
- Notification Picture:
- The recommended size is 360 * 180px, and the maximum size is 1M.
- Supported formats: JPG, PNG, GIF. Chrome, Opera, and Edge browsers on the Win platform are supported.
- Pictures can be network resources starting with http or https.
Audience: The target population that needs to be pushed, it is recommended to use the registrationID obtained from the registration log for push during testing.
- All: This fence will be pushed to all currently registered and future registered online users of the app.
- registrationID: push up to 1000 at a time.
After configuring the push parameters, click "Preview" to view the configured push parameters.
Confirm the sending parameters and click "Confirm" to successfully create the push task.
If there are no push targets that meet the conditions, the following error is returned:
Create a custom message
Go to the [Create a Push] - [Custom Message] page to create a push task. For parameter configuration instructions, refer to Create Notification Message.