Salesforce Marketing Cloud Data Views: _MobileLineOrphanContactView (GroupConnect – LINE Channel)

Posted on by admin

The _MobileLineOrphanContactView data view in Salesforce Marketing Cloud (SFMC) for GroupConnect helps identify orphaned LINE contact records. These orphans occur when multiple ContactKeys are associated with a single LINE UID, often during contact imports. SFMC retains one ContactKey as the primary, and the others become orphaned.

This blog provides a breakdown of all fields in this data view, use cases, SQL examples, and best practices for managing orphaned LINE contacts.

What is the _MobileLineOrphanContactView Data View?

This view allows you to audit and resolve ContactKey conflicts for LINE subscribers. It tracks orphaned records left behind when multiple ContactKeys are linked to the same LINE UID (AddressID).

⚠️ Why This Matters: Orphaned contacts may lead to broken targeting, duplicate records, and inconsistent personalization. Identifying and cleaning these helps maintain a clean subscriber base.

Key Benefits

  • Identify Import Conflicts: Detect records created due to duplicate LINE UIDs.
  • Improve Data Integrity: Resolve duplicates for consistent messaging.
  • Contact Reconciliation: Re-map or clean orphaned ContactKeys.

Fields in _MobileLineOrphanContactView

FieldTypeDescription
ContactIDNumberSystem-generated SFMC Contact ID linked to the LINE UID.
ContactKeyTextThe ContactKey (user-defined or auto-generated) associated with the orphaned record.
AddressIDTextLINE UID that caused duplication. Shared across multiple ContactKeys.
CreatedDateDateTimestamp (CST) of when the orphaned contact record was created.

When and Why to Use _MobileLineOrphanContactView

When to Use?

  • After importing LINE contact data.
  • When experiencing duplicate or unexpected ContactKeys.
  • During routine data hygiene processes.
  • Before running journey or send-based personalization for LINE.

Why Use It?

  • Prevent Journey Errors: Avoid sending messages to incorrect ContactKeys.
  • Data Consolidation: Help merge or archive unused keys.
  • Channel Accuracy: Ensure only one ContactKey is associated with each LINE UID.

Sample SQL Queries

1. List All Orphaned LINE Contacts

SELECT ContactKey, AddressID, CreatedDate 
FROM _MobileLineOrphanContactView

2. Count of Orphans per LINE UID

SELECT AddressID, COUNT(*) AS OrphanCount 
FROM _MobileLineOrphanContactView 
GROUP BY AddressID 
HAVING COUNT(*) > 1

3. Recently Created Orphan Records

SELECT ContactKey, AddressID, CreatedDate 
FROM _MobileLineOrphanContactView 
WHERE CreatedDate >= DATEADD(day, -30, GETDATE())

4. Orphans to Review by ContactKey

SELECT ContactKey, AddressID 
FROM _MobileLineOrphanContactView 
ORDER BY ContactKey

Best Practices for Managing Orphaned Contacts

  • Avoid importing multiple records with the same LINE UID and different ContactKeys.
  • Use a consistent ContactKey mapping strategy across imports.
  • Schedule regular queries on this view to monitor orphan growth.
  • Suppress orphaned ContactKeys from journeys or reassign them if necessary.

Conclusion

The _MobileLineOrphanContactView data view is critical for maintaining the integrity of your LINE contact data in SFMC. By tracking and resolving orphaned ContactKeys, you’ll ensure smoother campaign execution, better personalization, and fewer data conflicts across the LINE channel.

Pair this view with _MobileLineAddressContactSubscriptionView for a full view of your LINE contact lifecycle.

Related Posts