⚠️ Important: The
_MobileAddressdata view is no longer officially supported by Salesforce Marketing Cloud. It has been replaced by the more comprehensive and accurate views:_SMSSubscriptionLogand_SMSMessageTracking. However, some legacy environments may still have access to this view for backward compatibility.
This blog documents the legacy _MobileAddress data view fields and outlines scenarios where it might still be referenced during audits or legacy system reviews.
What was the _MobileAddress Data View?
The _MobileAddress data view stored information about SMS subscribers, including contact metadata, address fields, status, carrier details, and channel preferences. It served as a foundational table in MobileConnect but has since been deprecated in favor of more specialized views.
Why It Was Replaced
- Lack of real-time delivery tracking.
- Missing opt-in/out lifecycle detail.
- Limited channel and engagement metadata.
Fields in _MobileAddress Data View (Deprecated)
| Field | Type | Description |
|---|---|---|
| _MobileNumber | Text(15) | Mobile number of the subscriber. |
| _ContactID | Text | Unique identifier for the contact. |
| _Status | Text | Subscriber status (e.g., Active, Held). |
| _Source | Text | How the contact was created (e.g., API, Import). |
| _SourceObjectId | Text(200) | Source system object reference. |
| _Priority | Text | Message priority setting. |
| _Channel | Text(20) | Communication channel type. Usually SMS. |
| _CarrierID | Text | Mobile carrier ID. |
| _CountryCode | Text(2) | Country code for mobile number. |
| _CreatedDate | Date | Record creation date. |
| _CreatedBy | Text | User or system who created the record. |
| _ModifiedDate | Date | Last update timestamp. |
| _ModifiedBy | Text | User or process that modified the record. |
| _City | Text(200) | Subscriber’s city. |
| _State | Text(200) | Subscriber’s state or province. |
| _ZipCode | Text(20) | Subscriber’s postal code. |
| _FirstName | Text(100) | First name of the subscriber. |
| _LastName | Text(100) | Last name of the subscriber. |
| _UTCOffset | Number | Time zone offset from UTC. |
| _IsHonorDST | Boolean | Whether Daylight Saving Time is honored. |
Use Case Summary (Legacy Reference Only)
While not recommended for new implementations, here are some legacy use cases:
- Contact Lookup by Mobile Number.
- Region-Based Segmentation using city, state, and zip.
- Carrier ID Filtering to manage deliverability.
- Legacy Integrations with external CRMs referencing
_MobileAddress.
✅ Recommended Alternative: Use
_SMSSubscriptionLogand_SMSMessageTrackingfor active systems, as they provide opt-in/out status, delivery tracking, and journey attribution.
Conclusion
The _MobileAddress data view served its purpose in early versions of SFMC MobileConnect but has now been superseded by more robust and real-time tracking views. Marketers and developers should transition their reporting and integrations to supported data views for accurate and up-to-date SMS analytics.