SMS send system events and webhooks now include rendered SMS messages

January 24, 2025

We've updated SMS send system events and system webhooks to include a new field with the rendered version of each SMS message body. This change makes it easier to view the actual content that was sent to each user, to support your quality, compliance, and debugging efforts.

Here's what you can expect in your SMS send events moving forward:

• renderedSmsMessage - The final personalized version of the message that was sent to the user, with all merge parameters and Handlebars replaced by their actual values, the opt-out instructions that were included (when applicable), and unique shortlinks. This field is new in this release.

  Example:

  {    "renderedSMSMessage": "Hello, John! Click here to view our latest offers: https://itbl.co/-KT~2NMwZ Msg&data rates may apply. Text 'STOP' to opt-out."}

  You can find the renderedSMSMessage field in the SMS send system webhook payload and system event.

• smsMessage - The message template that was used to send the message, including merge parameters, Handlebar expressions, and raw URLs before adding UTM parameters and link shortening.

  (This field is unchanged in this release, and noted here for clarity.)

  Example:

  {  "smsMessage": "Hello, {{user.firstName}}! Click here to view our latest offers: {{offerUrl}}"}

  You can find the smsMessage field in the following system events and system webhook payloads:

  • SMS bounce
  • SMS click
  • SMS received (Note that for this event, the smsMessage contains the message that was received from the user, and is not a template version.)
  • SMS send