Why, What, and How: The Canonical Approach to Customer Intelligence
Understanding the Canonical Data Model implementation requires understanding the underlying business challenges it solves, the data structures it provides, and the technical mechanisms it employs.
WHY: Business Challenges Addressed
- Fragmented Customer View: Customer data lives in silos across products and channels. No single source of truth exists, forcing every team to maintain its own incomplete view of the customer.
- Disconnected Cross-Product Journeys: Customer actions in one product are not linked to reactions elsewhere. Behavioral stitching is missing, resulting in fuzzy cross-channel orchestration and missed revenue opportunities.
- Inconsistent Customer Identity: Multiple customer representations exist across products and channels. ID conflicts disrupt personalization accuracy, reporting consistency, and machine learning targeting.
- "Next Best Action" Becomes "Next Best Guess": Without unified customer context, decisioning systems cannot determine the right action at the right time for the right customer. Engagement becomes reactive rather than prescriptive.
WHAT: Canonical Model and Unica 360 Solutions
The Canonical Data Model provides standardized structures; CDM provides unified views:
- Canonical Entities: Pre-built templates for Party, Account, Product, Campaign, and Response that are extensible and subject-area agnostic.
- Customer 360: Customer 360 aggregates unified customer identity, demographics, risk & compliance indicators, consent preferences, verified contact details, financial holdings, behavioral transaction metrics, multi-product engagement, campaign interactions (7D/30D), and conversion performance into a single consolidated customer profile.
- Campaign 360: Campaign 360 derives key performance metrics using pre-aggregated 360 tables and simple, standardized formulas applied to campaign-level contact and activity data. It provides a comprehensive, curated set of measures across audience size, engagement, responses, conversions, and cost attribution, enabling consistent evaluation of campaign effectiveness, ROI, and cross-channel behaviour. For more information, refer MaxAI Canonical User Guide.
HOW: Technical Implementation Mechanisms
The Canonical approach achieves unified customer intelligence through three key mechanisms:
- Canonicalizing Data Across Products: The Metadata Model unifies data schemas across multiple source systems and products. RDV implements standard Hub, Link, and Satellite structures. Metadata-driven transformation ensures all data conforms to canonical definitions regardless of source.
- Stitching Customer Journeys End-to-End: Customer events across Email, SMS, App, Web, and other channels are linked through customer identity and journey tracking. The metadata-driven ETL process creates connected event timelines for improved decisioning (Next Best Touchpoint, Segment Treatment Optimization, re-engagement sequencing).
- Resolving Identity at Source-of-Truth Level: Persistent identity keys, identity graphs, and reconciliation rules unify customer profiles. The Metadata Model captures all identity resolution rules. RDV maintains identity lineage and conflict resolution. Unica 360 presents the authoritative customer identity to downstream applications.
Business Application Integration Architecture
The Canonical Data Model serves as the central hub for enterprise customer data, integrating seamlessly with downstream systems that leverage customer and campaign intelligence. The three-layer architecture—Landing Zone (LDZ), Raw Data Vault (RDV), and Unica 360—creates a unified backbone through which multiple downstream systems are powered.
Three primary downstream integrations provide differentiated business capabilities: