When you build an event-triggered program using SMS, you will select universal behaviors in the program settings. They refer to the action your contact needs to take to enter the program and the path they are going to follow, depending on your program's scenario. Each event has its code and characteristics you will find in the sections below. SMS event types include:
- Interacted with an SMS program
- Been sent a message from SMS program
- Interacted with a multi-step program
- Received delivery status
- Clicked link in SMS
Interacted with an SMS program
Event type code: 54
This event is triggered for messages sent from a contact's mobile device, also known as mobile originated (MO) messages. This event is not triggered with multi-step SMS programs.
Note: Tags are only supported for organizations set up to send SMS via the Exchange sender mechanism. The Tags attribute is listed under several of the universal behaviors on this page.
Event 54 is published each time a list of SMS contacts is imported through the UI or the API. You can choose not to publish event 54 by clearing the Publish 'Interacted with an SMS program' event when importing SMS contacts check box in the Mobile settings.
Universal behavior attribute | Exchange attribute | Data type | Valid values |
Mobile Number | mobileNumber | Short text |
|
Campaign Name | campaignName | Short text |
|
Program Id | smsProgramId | Short text |
|
Program Name | smsProgramName | Short text |
|
Program Type | smsProgramType | Short text |
|
Country | locationCountry | Short text |
|
Code | code | Short text |
|
Message Body | messageBody | Short text |
|
Message Type | messageType | Short text |
|
Carrier Network | carrierNetwork | Short text |
|
Source | source | Short text |
|
Tags | tags | Long Text |
|
Set Consent | setConsent | Short text |
|
Been sent a message from SMS program (smsSent)
Event type code: 55
This event is triggered for messages sent to a contact's mobile device, also known as mobile terminated (MT) messages. This event is not triggered with multi-step SMS programs.
Universal behavior attribute | Exchange attribute | Data type | Valid values |
Mobile Number | mobileNumber | Short text | {Mobile Number} |
Campaign Name | campaignName | Short text | {Campaign Name} |
Program Id | smsProgramId | Short text | {Program Id} |
Program Name | smsProgramName | Short text | {Program Name} |
Program Type | smsProgramType | Short text |
|
Country | locationCountry | Short text |
|
Code | code | Short text | {Short / Long Code} |
Message Body | messageBody | Short text |
|
Message Type | messageType | Short text |
|
Carrier Network | carrierNetwork | Short text | {Carrier Network} |
Source | source | Short text | {null} |
Tags | tags | Long text |
|
Interacted with a multi-step program
Event type code: 61
This event is triggered when an incoming SMS is received initially to start the multi-step program. Once a given multi-step program starts, for each incoming SMS, a new UB #61 will not be triggered.
Attribute | Data type | Valid values |
Mobile Number | Short text | {Mobile Number} |
Campaign Name | Short text | {Campaign Name} |
Program Name | Short text | {Program Name} |
Program Type | Short text | Multi-Step |
Country | Short text |
|
Code | Short text | {Short / Long Code} |
Step Name | Short text | {Name of the inbound or outbound step} |
Message Body | Short text | {Message Body} |
Message Type | Short text |
|
Received delivery status
This event is triggered for every MT message, except for those sent with a multi-step SMS program. When a message leaves the SMS gateway, Delivery status changes to Sent. When received from the carrier, Delivery status updates to Delivered or Failed. Not all carriers provide delivery status; if not provided, the status remains as Sent.
Attribute | Data type | Valid values |
Mobile Number | Short text | {Mobile Number} |
Campaign Name | Short text | {Campaign Name} |
Program Name | Short text | {Program Name} |
Program Id | Numeric | {Id of the Program} |
Program Type | Short text |
|
Country | Short text |
|
Code | Short text | {Short / Long Code} |
Message Body | Short text |
|
Message Type | Short text |
|
Carrier Network | Short text | {Carrier Network} |
Tags | Long text |
|
Source | Short text | {Source parameter Value from Batch SMS Send API} Example Value: {mailingId=34,reportId=234,recipientId=234,jobId=433} |
Delivery Status | Short text |
|
Status Code | Short text | {Failed Status Code} Only populated when delivery Status is 'Failed'. For example:
|
Clicked link in SMS
This event is triggered when a contact clicks a link in an SMS message. This event is only available with SMS link tracking enabled.
Attribute | Data type | Valid values |
Mobile Number | Short text | {Mobile Number} |
Program Name | Short text | {SMS Program Name} |
Program Id | Numeric | {Id of the SMS Program} |
Link Name | Short text | {Link Name} |
Link URL | Short text | Unpersonalized long url Example: http://golfsmith.com/carbonfiber/?fname=%%fname%% |
Source | Short text | {mailingId=34,reportId=234,recipientId=234,jobId=433} |
Message Name | Short text | {SMS message name} |
Global opt-out
This behavior gets triggered when the contact interacts with one of the default opt-out keywords assigned to the organization. In the new SMS experience, this event gets triggered when the contact interacts with the global stop campaign.