When customer interactions arrive from several channels, marketers need a usable customer profile—not another isolated dataset. A customer data platform (CDP) integrates first-party data sources into a persistent, unified customer profile and makes that profile available to marketing destinations such as email and advertising platforms. In a monolithic CDP, the platform hosts the profile itself and brings collection, management, and activation together. section 4.3.3
A monolithic CDP is worth considering when:
- Web or mobile interactions need to inform campaigns quickly, and the organization wants built-in event collection, identity resolution, and destination integrations. section 4.3 section 4.3.3
- Marketing cannot rely on an existing marketing data lakehouse or a data engineering team to prepare a customer profile for activation. section 4.3 section 4.3.3
The architectural choice is where customer data lives. A monolithic CDP hosts a unified profile; a composable CDP activates data already held in the organization’s warehouse or lakehouse. Hosting offers a more prescribed starting point, but loading and transforming data to fit a predetermined profile can lengthen implementation and limit flexibility. Business logic and first-party data built into the platform may also be hard to move later, even though its destination integrations make changing downstream tools easier. section 4.2 section 4.4.1 section 4.4.11
Mobile charging network
A charging-network marketing team wants to react to mobile events, such as a customer nearing a station, across SMS, push notifications, email, and paid media. Its data engineers serve the product team rather than marketing. A monolithic CDP focused on capturing, unifying, and activating mobile events is a plausible fit, provided software engineering can support implementation. section 4.3.3
Evaluate the platform against the campaigns that matter most, not a checklist of every possible feature. Confirm the implementation support available, the channels that must work reliably, and what happens to customer data and audience logic if the platform is replaced. Consent also belongs in the design: unified profiles should reflect the data customers agreed to share. section 4.4 section 4.4.1 section 4.4.11 section 2.3.2
Table 4.1 Marketing technology ecosystem comparison: benefits and trade-offs
| Marketing technology |
Best for |
Key benefits |
Trade-offs |
| Composable CDPs |
Data-mature companies needing scalability and tight integration between analytics and marketing |
Data unification, extensibility, cloud-based, direct connection to marketing data lakehouse |
Requires strong data infrastructure and expertise |
| Marketing clouds and engagement platforms |
Large organizations needing an all-in-one solution with consultant support |
Simplifies the tech stack, certified consultant support, ease of implementation |
Higher cost, limitations in marketing destinations |
| Monolithic CDPs |
Web and mobile-first companies with lower data maturity needing built-in real-time capabilities |
Unified customer profile, preset identity resolution, many destination integrations |
Difficult to implement, less flexibility |
| In-house builds |
Organizations with highly bespoke needs or minimal data integration requirements |
Fully customizable, control over data infrastructure |
High development and maintenance effort |
Compare monolithic CDPs with composable CDPs, marketing clouds, and in-house builds by suitable use case, benefits, and trade-offs. section 4.3
