Skip to main content
Clinton Fernandes (Deloitte) 님이 #Data Cloud에 질문했습니다

Hi everyone 👋    We’re implementing Salesforce Data Cloud with a mobile SDK data stream that provides both user-level (app engagement) and device-level data.    This creates two DMOs:  Contact Point App DMO – holds engagement data and includes SubscriberKey  Device DMO – holds device details like OS Name, OS Version, Model, etc.    Currently, only the Contact Point App DMO has SubscriberKey mapped.  To make OS info visible in segmentation, we added OS Name as a custom field in Contact Point App — which works but isn’t ideal for scalability.    We’re considering:  Mapping SubscriberKey to a custom field in Device DMO, and    Creating a relationship between Device.SubscriberKey__c and Individual.IndividualId,  so Device data remains normalized yet still available in segmentation.    Questions:    1. Is this the recommended scalable approach?  2. Could this custom relationship (SubscriberKey → IndividualId) cause identity or unification issues?  3. Or is it better to keep OS Name in Contact Point App for simplicity?    Appreciate any insights or best practices from those who’ve modeled similar mobile data setups 🙏    Thanks,  Clinton Fernandes    

 

@* Data 360 * 

답변 2개
  1. Khyati Mehta (InfinySkills) Forum Ambassador
    2025년 10월 26일 오전 10:37

    Hello Clinton, 

     

    Your proposed approach — mapping SubscriberKey to a custom field in the Device DMO and creating a relationship between Device.SubscriberKey__c and Individual.IndividualId — is generally a scalable and data-normalized solution. It allows the Device DMO to remain independent while still linking to individuals for segmentation and personalization use cases. However, you should carefully assess identity resolution implications: if multiple devices share the same SubscriberKey or if identity stitching is based primarily on other identifiers (like email or mobile ID), introducing a custom SubscriberKey relationship could create ambiguity or duplicate linkages in Identity Resolution or Unified Individual views. If your use case primarily involves segmentation by OS and device attributes without complex cross-device identity needs, maintaining OS Name in the Contact Point App DMO might be simpler and safer. Hope this answers your questions!

0/9000