Explore Data Views in Salesforce Marketing Cloud

Salesforce Marketing Cloud Data Views

Data Views in Salesforce Marketing Cloud are integrated tables that provide essential data on subscribers, campaigns, and both email and SMS communications. These data sets are invaluable for analyzing your marketing performance. Although some tables are officially unsupported or deprecated, they can still hold useful information in specific contexts.

Overview of the Main Data Views

Below is an overview of the main tables, including information on their functions and usage:

_Journey
Stores information about your journeys to provide detailed context.
_Sent
Includes send data (date, domain, triggered send, etc.).
_Open
Stores email open information, including date and domain.
_Click
Contains data related to email clicks (links, URLs, etc.).
_Bounce
Provides information about bounces in your email sends.
_JourneyActivity
Contains information on journey activities, useful for tying email data back to journeys.
_AutomationInstance
Provides historical data on automation runs.
_AutomationActivityInstance
Provides historical data on activities within Automations in Automation Studio.
_MobileAddress
Unsupported table but useful for MobileConnect demographic data.
_MobileSubscription
Unsupported table that might still hold data, but its use is discouraged.
_SubscriberSMS
Legacy table, no longer updated. Used before MobileConnect. Not recommended.
_SMSSubscriptionLog
Stores detailed information on SMS subscription status for each phone number.
_SMSMessageTracking
Tracks the history of SMS messages sent through MobileConnect.
_UndeliverableSMS
Provides details on failed SMS deliveries, for example in cases where the device is off-network.

Relationships Between the Data Views

The Data Views interact with each other to provide a complete picture. Below is an example of typical relationships:

Diagram of relationships between Data Views

Example: _Subscribers is linked to _Sent, _Open, and _Click through SubscriberKey, and can be connected to SMS data.

Simplify Your SQL Queries with QAiry

Writing SQL queries can be complex, but the AI tool QAiry simplifies this process. Ask a question in natural language, and QAiry automatically generates the corresponding SQL query.

“Which customers clicked on the Welcome email?”

Discover how QAiry works through this video demonstration:

Optimize Your Campaigns

Combine the power of Data Views with the artificial intelligence of QAiry to fully harness Salesforce Marketing Cloud. Personalize your campaigns, analyze performance, and boost your ROI.

_SMSMessageTracking

Main fields:

MobileMessageTrackingID: Unique ID for tracking info.
EID: Enterprise ID number.
MID: Member ID.
Mobile: The mobile number for the subscriber.
MessageID: Mobile message ID.
KeywordID: Unique identifier for the keyword.
CodeID: Unique identifier for the SMS code.
ConversationID: Not used (legacy).
ConversationStateID: Correlates MO and MT messages as a conversation.
CampaignID: The SMS campaign tied to the record.
Sent: 1 = true, 0 = false.
Delivered: 1 = true, 0 = false.
Undelivered: 1 = true, 0 = false.
Outbound: 1 = true, 0 = false.
Inbound: 1 = true, 0 = false.
CreateDateTime: The date/time the tracking record was created.
ModifiedDateTime: CST date/time the record was modified.
ActionDateTime: The actual date/time of a delivery or non-delivery event.
MessageText: The text of the message.
IsTest: 1 = true, 0 = false.
MobileMessageRecurrenceID: Recurrence schedule ID for the message.
ResponseToMobileMessageTrackingID: The tracking ID of the response to the message.
IsValid: 1 = true, 0 = false.
InvalidationCode: Invalidation code for the message.
SendID: The send ID number for the SMS send.
SendSplitID: If the message was split, the ID of the split.
SendSegmentID: The ID of the segment tied to the message.
SendJobID: The job ID for the SMS send.
SendGroupID: The group ID for the SMS send.
SendPersonID: The sendperson ID for the SMS send.
SubscriberID: The subscriber ID (unique for each subscriber record).
SubscriberKey: The subscriber key for the affected subscriber.
SMSStandardStatusCodeId: SFMC delivery status code.
Description: Detailed description of the status code.
Name: The name of your message.
ShortCode: The short or long code used to send your message.
SharedKeyword: The keyword used in your message.
Ordinal: Represents parts in a multi-part message, starting at 0.
FromName: From Name (max 11 chars).
JBActivityID: Unique ID for the journey activity the message was deployed from.
JBDefinitionID: Unique ID for the journey the message was deployed from.
SMSJobID: Unique ID for each SMS job triggered in MobileConnect.
SMSBatchID: Identifies a batch associated with an SMS send.