Single Customer View
Single Customer View (SCV) is a unified, consolidated profile that brings together everything an organization knows about a customer from every system and channel into one accessible record.
Also known as: 360-degree customer view, unified customer profile, customer 360
Single Customer View (SCV), sometimes called a 360-degree customer view, is a complete and consistent profile of a customer assembled from data scattered across many systems. It combines contact details, purchase history, web behavior, support interactions, marketing engagement, and product usage into one accessible record. It is the aspiration that drives many CDP, MDM, and data-platform investments, and it is also one of the most over-promised concepts in marketing technology.
What A Single Customer View Means
A Single Customer View covers the identity resolution that ties records across systems to the same person, the data integration that pulls in the relevant data from each source system, the conflict resolution that decides which source wins when sources disagree, the storage layer that holds the unified profile, and the access layer that exposes the profile to the systems and teams that need it. The scope includes both transactional data (purchases, support tickets, product usage) and behavioral data (web visits, email engagement, advertising exposure), unified at the level of identifiable individuals.
How A Single Customer View Works
In practice, building a Single Customer View requires connecting source systems, resolving identity so records about the same person are merged, and reconciling conflicts when systems disagree. The result lets marketing, sales, and service teams act on a shared, current understanding of each customer rather than working from partial fragments. The technical implementation varies — a packaged CDP, a composable approach built on the warehouse, an MDM platform, or a hybrid — but the activities are similar. Mature implementations also include consent and preference handling, retention enforcement, and access governance so the unified profile respects the same constraints as the source data.
Common Pitfalls and Misconceptions
The Single Customer View aspiration is common, but a perfect SCV is rare. Data is always slightly out of date, some sources resist integration, and privacy rules limit what can be combined. The practical goal is a view that is unified enough to support the decisions that matter, not literal omniscience. The most common SCV failure is treating it as an infrastructure project rather than as a use-case-driven program; teams build the unified data without a clear consumer, and the resulting platform becomes expensive shelfware. Teams also under-invest in the maintenance side of identity resolution, treating it as one-time work when it actually requires continuous tuning. Another trap is over-claiming completeness when the underlying data has significant gaps.
Single Customer View in Practice
The practical insight that helps most teams progress on Single Customer View is letting go of the aspiration to perfection. A view that captures the data needed for the decisions that matter, even with known gaps and known latency, is operationally valuable. A pursuit of complete real-time omniscience never ships. Mature programs articulate which use cases the view must support, build for those, and accept that some sources will not integrate cleanly and some data will be a day behind. The honest version is more useful than the theoretical ideal, and it actually gets deployed and used.
Frequently asked questions
-
How is a single customer view created?
It is created by integrating data from source systems, applying identity resolution to merge records about the same person, and reconciling conflicting values. Customer data platforms are commonly used to assemble and maintain it.
-
What is the difference between a single customer view and a CRM record?
A CRM record contains data managed within the CRM. A single customer view aggregates data from the CRM plus web analytics, marketing automation, support tools, and more, producing a fuller picture than any one system holds.
-
Why is a single customer view hard to achieve?
Data lives in many systems with different structures and identifiers, some systems are difficult to integrate, records conflict, and privacy rules restrict combining certain data. These obstacles make a complete, perfectly current view difficult in practice.
-
Is a single customer view the same for B2B and B2C?
The concept is the same, but B2B often extends it to a single account view, layering individual contacts under their organizations. B2B also tracks buying groups, making account-level consolidation as important as individual profiles.
-
Does a single customer view require a specific tool?
Not necessarily, though customer data platforms are purpose-built for it. Some organizations assemble a view through a data warehouse and reporting layer. The tooling matters less than the integration, identity resolution, and governance behind it.
-
What is a 360-degree customer view?
It is a synonym for single customer view, emphasizing the comprehensive scope across all touchpoints and systems. The phrase is more common in some industries and vendor pitches. The underlying concept is the same: a unified profile that consolidates everything known about a customer.
-
Does a single customer view require a CDP?
Not strictly. CDPs are purpose-built for the use case and are the most common path. Some organizations achieve similar outcomes through a data warehouse with strong identity resolution and reporting on top. The right tool depends on existing infrastructure and the latency requirements of the use case.