Salesforce Marketing Cloud Data Views: SMSSendLog

Posted on by admin

The SMSSendLog in Salesforce Marketing Cloud (SFMC) captures detailed logging information for each SMS message sent using MobileConnect. It’s similar to the SendLog for Email Studio, allowing users to monitor delivery events, track triggered sends, and log send-time attributes for deeper campaign reporting.

This blog outlines the fields, use cases, and SQL examples associated with SMSSendLog to help marketing teams troubleshoot, optimize, and audit SMS performance.

What is the SMSSendLog?

SMSSendLog is a logging-enabled data extension that captures runtime data during SMS sends. It supports both manual and triggered sends, giving full visibility into delivery metadata.

🔧 Like the email SendLog, you must enable SMS Send Logging and configure the log data extension before data is captured.

Key Benefits of SMSSendLog

  • Full SMS Visibility: Capture IDs, batch info, and subscriber details.
  • Triggered Send Traceability: Track performance per automation.
  • Enhanced Reporting: Combine with tracking views to measure success.
  • SMS Audit Trail: Maintain send-time logs for compliance or debugging.

Fields in SMSSendLog

FieldTypeDescription
SMSJobIDText(36)Unique identifier for the SMS job. Used for matching to job metadata or analytics.
SMSTriggeredSendIDText(36)Unique ID for the triggered SMS send definition.
SMSBatchIDLongNumberBatch number associated with the SMS message. Helps segment and trace SMS sends.
SubIDLongNumberSubscriber ID associated with the message send. Used for joins across data views.

📝 Note: You can extend this log with additional fields like MobileNumber, MessageText, OptInStatus, CampaignID, etc., to capture full send context.

When and Why to Use SMSSendLog

When to Use?

  • When monitoring triggered or recurring SMS campaigns.
  • For auditing SMS sends and errors.
  • To analyze batch or journey-based SMS deliveries.
  • When you need to custom-report on SMS send performance.

Why Use It?

  • Track Send Time Variables: Understand what was sent, to whom, and when.
  • Enhanced Troubleshooting: Pinpoint issues with triggered or high-volume sends.
  • Personalization Validation: Verify values rendered via AMPscript or dynamic logic.
  • Build SMS Reports: Use JobID and SubscriberID to join tracking views like _SMSMessageTracking.

Sample SQL Queries

1. Count of SMS Sends by Job

SELECT SMSJobID, COUNT(*) AS TotalSends 
FROM SMSSendLog 
GROUP BY SMSJobID

2. Find Messages Sent via Specific Triggered Send

SELECT SMSTriggeredSendID, SubID 
FROM SMSSendLog 
WHERE SMSTriggeredSendID = 'abcd-1234-efgh-5678'

3. Join with _SMSMessageTracking to Get Delivery Info

SELECT s.SMSJobID, t.Mobile, t.MessageText, t.Delivered 
FROM SMSSendLog s 
JOIN _SMSMessageTracking t 
ON s.SubID = t.SubscriberID

4. Most Recent SMS Sends

SELECT SMSJobID, SMSTriggeredSendID, SMSBatchID, SubID 
FROM SMSSendLog 
ORDER BY SMSBatchID DESC

Conclusion

The SMSSendLog provides an in-depth look at SMS message activity in SFMC. Whether you’re troubleshooting sends, validating data, or generating campaign reports, this log serves as your single source of truth for send-time SMS events.

For a complete SMS campaign view, use SMSSendLog in conjunction with _SMSMessageTracking, _UndeliverableSms, and _SMSSubscriptionLog.

Related Posts