The problem
The client operated three distinct brands under one parent organization, each with its own customer base, its own compliance requirements, and its own marketing ops team. Customer data lived in separate systems, preference management was fragmented, and sending reputation had to be protected across every brand without cross-contamination. The parent organization wanted a single Marketing Cloud account that could host all three brands, share a common data model, and still let each brand run independently.
The work
Alloy12's founder led the Marketing Cloud solution architecture during a prior consulting engagement. The work started with discovery across all three business units, then moved into a blueprint that covered account structure, data model, integration architecture, and compliance controls.
The delivered solution included a parent business unit with two child business units, one per brand, each with its own sender authentication, dedicated sending domains, Reply Mail Management configuration, and branded login and preference center. A shared contact builder data model unified customer records across business units with a single unique record per person. Preference management was architected to support per-brand opt-down while respecting parent-level suppression, which is a non-trivial problem in Marketing Cloud.
Beyond the platform configuration, the engagement covered Marketing Cloud Connect to synchronize data from Sales Cloud to Marketing Cloud, Journey Builder integration with outbound API calls for physical mail and third-party systems, a duplicate management strategy using a custom "keyring" object and Apex to merge duplicate contacts, Google Analytics 360 connector configuration, Einstein Engagement Scoring activation, and SSO setup for both business units. Data migration included opt-out status preservation across the cutover.
IP warming plans were designed for each business unit to protect sending reputation during rollout. Email templates, reusable content blocks, and a folder structure that worked across enterprise sharing rounded out the implementation.
What changed
The three business units went from fragmented tools and manual data handoffs to one Marketing Cloud account with a unified customer view. Preference management stopped being a per-brand spreadsheet exercise. Journey Builder could trigger outbound API calls to external systems as part of customer lifecycle flows. The engineering team shipped dynamic sending capability, and the marketing teams got reporting and analytics in one place across all three brands.
Stack
The work combined Salesforce Marketing Cloud across multiple business units, Sales Cloud with Marketing Cloud Connect, Apex for custom duplicate management, SFTP integrations from administration systems, Google Analytics 360, Einstein Engagement Scoring, and SSO via SAML.
Why this matters for your business
Multi-brand organizations get told to buy one Marketing Cloud instance per brand and stitch them together later. That is expensive, operationally painful, and a nightmare for preference management. This engagement shows the opposite pattern. One account, shared data, brand-level isolation where it matters, shared infrastructure where it does not. Alloy12 has been through this architecture at enterprise scale and knows where the traps are.