Data CloudAdvancedb2baccount-hierarchyunification
Implement hierarchy preferences for B2B account vs contact unification
Real World Scenario
B2B SaaS sells to enterprises; marketing engages contacts but sales owns accounts. Unified profile merges contacts across unrelated companies sharing email domain.
Expected Answer
• Do not match on email domain alone for B2B — require account Id or verified workplace email
• Separate person and account unified objects with relationship graph
• Role-based attributes: buyer vs influencer on same account
• Exclude free email domains from account association rules
• Manual review queue for domain collision edge cases
• Sales CRM account Id as authoritative key for B2B match
• Test conglomerate with shared services email patterns
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Do not match on email domain alone for B2B — require account Id or verified workplace email Also consider: Separate person and account unified objects with relationship graph In practice: Role-based attributes: buyer vs influencer on same account Optimize for scale and operational observability.
Architect Perspective
B2B identity is graph not flat B2C — domain matching is a classic over-merge trap.