Hi,
I'm thinking of creating a new data graph to be used for personalization on content in the marketing cloud to make it easier for our users, because the current one contains unnecessary related objects.
I'm therefore wondering what is the best practice, to add the fields on the unified individual (so that they are available via the Primary Object) or to add the fields on the Individual on the related Object? Alternatively, is there an advantage to having the fields both as direct and via related?
For example, I'm thinking of Record Owner Name, Record Owner email, Last login, Last Order date etc. (Stored on Lead or contact in CRM)
Then I'm wondering if anyone has tried replacing the default data graph (from setup) and how it might affect current email etc.
Thanks in advance.
François Perret (Bamsoo) 
Forum Ambassador
Hi Patrick,
If you add Fields to the Individual DMO, they will be added to the Unified Individual DMO by the identity resolution process and you will be able to define what value will be used for the Identity Resolution (last modified, source priority, etc).
If you keep the fields on the related object, you will have to define what to display when used as Merge Fields. I'd say extend your Unified Individual model with Fields that are mandatory for the business and keep others in related objects.
To your last point, previous emails will keep being bound to the previous DG after you change the default.
Hope this helps 😎
#SharingIsLearning #AccountEngagementFrançois.
PS : In order other Trailblazers to be pointed directly the most helpful answer, please do not forget to click “Accept this answer” below it.
