Clarification on Merge Policy for Account Profiles in AEP

Question

Could you please clarify whether merge policies (such as Dataset Precedence and Timestamp Ordered) are applicable to Account profiles in B2B implementations, similar to how they are applied for customer/person profiles in Adobe Experience Platform?Specifically, I would like to understand if merge policies control how data is prioritized or combined when multiple datasets contribute attributes to the same Account profile, just like they do for customer profiles.Any clarification or documentation reference would be greatly appreciated.

SG14_97 · Answer

Hi ​@leela2,From what i have observed it’s governed by default by the timestamp driven policy and further didn’t see any option to create a separate policy for xdm:account schema as of now.I think the ingestion and the updates to account profile is still governed by timestamp of ingestion. Also account being a custom class and kind of lookup data (although having some flexibility over traditional lookup schema models) i think those customizations are restricted.Regards,Sayantan

Sign up

Login with SSO

Login to the community

Login with SSO