mPulse SMS
Overview
The table below describes channel-specific fields for mPulse SMS channels.
Field | Description |
---|---|
API Service URL | This mandatory text property defaults to the value "https://ms-api.mpulsemobile.com/". It can be a maximum of 500 characters in length, and represents the API service URL used to connect to the mPulse service. |
Username | This mandatory text property accepts a maximum of 100 characters. It allows you specify a username to be used to connect to the mPulse service. |
Password | This mandatory, password-masked text field accepts a maximum of 100 characters. It allows you specify a password to accompany the supplied username. |
Account ID | This mandatory text property accepts a maximum of 100 characters. It represents the account ID that will be used to connect to the mPulse service. |
Audience list ID | This combo box field is accompanied by an Add button, which allows you to specify one or more audience list IDs. Each can be a maximum of 100 characters in length, and represents an Audience list ID in the context of which all uploaded contacts will be grouped together. Specification of an audience list ID is mandatory. |
Event name | This mandatory text property accepts a maximum of 100 characters. It represents the event name that will be used to send mPulse SMS messages. |
Content attribute | This mandatory text property accepts a maximum of 50 characters. It represents the custom attribute name that will be used to render SMS content for each subscriber. |
Mobile phone | The mobile phone number used to test connectivity to the mPulse service. |
Max list upload batch size | The maximum number of message recipients that can be uploaded to an mPulse audience list in a single batch For each, properties such as Phone Number, Customer Key, First Name and Last Name are uploaded. The property defaults to 50. |
Max event upload batch size | The maximum size of a batch of personalized subscriber content that can be uploaded to mPulse. The property defaults to 2000. |
Enable asynchronous list upload | If this checkbox is checked, the action of uploading subscribers to an mPulse audience list will be carried out in asynchronous mode. |
Enable asynchronous event upload | If this checkbox is checked, the action of uploading personalized subscriber content will be carried out in asynchronous mode. |
Max send threshold | This numeric property defaults to 10, and accepts a range of values from 1 to 10. It represents the maximum number of concurrent send operations that can be executed for a batch of email campaigns. |
Ignore HTTP 400 error | If this checkbox is checked, any HTTP 400 errors received from mPulse when uploading member lists will be ignored. |
Request timeout | A time period, in seconds, for which RPI will wait to connect to the mPulse service before timing out. The property defaults to 120. |
Callback Service section
The table below describes fields in the Callback Service section.
Field | Description |
---|---|
Callback service URL | URL of service used to process incoming SMS events. |
Event upload content queue path | Path of the queue to which event upload content will be sent. |
Member list import timeout | The period, in minutes, for which the member list import will wait to complete. |