The reach rate and speed of app notification pushes are often compromised to various degrees due to factors such as app processes not in the background, notifications disabled, and excessive vendor channels.
If you have a type of push that requires high reach rate and speed (such as approval notifications and transaction notifications), you can use the supplementary SMS push feature provided by TPNS. This feature sends important information to users through SMS messages when they cannot receive app pushes, maximizing the reach rate and speed of messages.
Sends system-related messages to app users, including common notifications and SMS messages about upgrade/maintenance, service activation, price adjustment, order confirmation, logistics update, message confirmation, and payment.
Sends messages to registered and potential users, including promotional information about sales campaign, business promotion, new product feature, and member care, to increase app exposure and user engagement.
Before you use SMS push, you need to bind a mobile number for each user. The TPNS SDK provides an API for binding mobile numbers.
You need to save Tencent Cloud's API keys on the TPNS platform first, so that TPNS has the permission to send messages via the SMS platform. The configuration steps are as follows:
Note:A key pair consists of a
SecretId
andSecretKey
. Each user can have up to two key pairs.
SecretId
and SecretKey
and click Confirm to save.A complete SMS message consists of a signature and body. You can go to the SMS console to create SMS signatures and body templates.
Currently, TPNS supports using the supplementary SMS push feature via RESTful API calls only. You need to add the following fields to the message body when calling the push API:
Parameter | Type | Required | Description |
---|---|---|---|
resend_by_sms | bool | No | Whether to enable supplementary SMS push. true : yes; false : no; default: false |
sms_info | Object | No | Required for supplementary SMS push. The specific structure is as follows: SmsInfo |
Parameter | Type | Required | Description |
---|---|---|---|
delay_trigger_time | int | Yes | Time of trigger delay in seconds, that is, after you push normally, how long it will wait before performing the supplementary push if no trigger event is received. The minimum value is 300s. |
trigger_condition | int | Yes | Event that triggers the supplementary SMS push.0 : send a supplementary SMS message to devices on which notifications are disabled.1 : sends a supplementary SMS message when no reach event is received within delay_trigger_time .2 : sends a supplementary SMS message when no click event is received within delay_trigger_time . |
sms_sign_name | String | No | SMS signature |
sms_template_id | String | Yes | SMS template ID |
sms_app_id | String | Yes | appId of the SMS platform |
sms_template_params | Array of string | No | Parameters that must be carried in the template |
You can find the SMS signature, SMS template ID, and SMS platform’s appId
in the SMS console. For more message parameters, see Push API.
Below is a sample push:
{
"resend_by_sms": true,
"sms_info": {
"delay_trigger_time": 3600,
"trigger_condition": 1,
"sms_sign_name": "signe_name",
"sms_template_id": "123",
"sms_template_params": [
"param1",
"param2"
],
"sms_app_id": "appId"
},
"audience_type": "token_list",
"message": {
"title": " test loop",
"content": "test loop"
},
"token_list": ["025ae31e59b3**********a5866354b3","06dee08efed***********31ef23bba"],
"message_type": "notify",
"multi_pkg": true
}
After completing the push, you can view the SMS message records on the statistics page in the SMS console.
Before you can use the supplementary SMS push feature, you need to purchase an SMS package. For more information, see Billing Overview.
The default delivery rate limit is as follows:
Was this page helpful?