What Is Customer 360? A Governed Customer View Explained
Customer 360 is a governed view that connects selected customer records for defined decisions while preserving identity evidence, provenance, and correction.
Customer 360 is a governed view that connects selected customer records and interactions for a defined decision. It is not automatically one database, a complete picture of a person, or proof that every record belongs together.
Customer 360 at a glance
- Meaning: a connected, decision-ready view of relevant customer data.
- Why it matters: helps teams use consistent context while retaining source truth.
- Used by: data, CRM, service, marketing, sales, analytics, and governance teams.
- Commonly confused with: CDP, CRM, identity resolution, data warehouse, or “golden record.”
What Customer 360 means
The term is used broadly and by vendors. Salesforce describes its Customer 360 as connected products providing a view across touchpoints and interactions. That explains one vendor's product framing, not a universal architecture requirement. Review the source.
A precise Customer 360 scope names the supported decision, source systems, identities, field provenance, freshness, permission, conflicts, access, activation, correction, and deletion/update paths.
How it works
- Source records remain identifiable.
- Identity rules link, decline to link, or route uncertain matches.
- A selected profile/view exposes decision-relevant fields with provenance and freshness.
- Activation rules choose action, no action, clarification, or human handoff.
- Corrections and permission changes propagate and remain auditable.
Salesforce defines identity resolution as unifying records from multiple sources. It is one component of Customer 360, not proof of match quality. Review the source.
Five-minute decision card
Copy these fields into a document, spreadsheet, or CRM note: decision, records needed, identity evidence, source and freshness, who may view, allowed action, no-action rule, and correction path. Start with one decision, not every available field.
Example
A fictional equipment-rental company creates an asset-service view using verified account ID, rental contract, machine serial number, delivery location, and maintenance event. A site manager may view only assets assigned to that site; marketing permission is not copied from the contract. The view can route a maintenance-status question but cannot recommend a new rental. It is “360” only for this asset-service decision, not a complete person profile.
On the decision card, the company records: decision = answer maintenance-status questions; records = rental contract, assigned-site record, and maintenance event; identity = verified account ID + machine serial; source and freshness = active contract plus the latest maintenance event checked when the question arrives; viewer = site manager sees only assets assigned to that site; allowed action = route the question; no action = do not recommend another rental; correction = service owner updates the source record. “Activation” simply means using the governed view to choose that allowed action or no action.
Customer 360 vs related terms
| Concept | Meaning | Use when | Do not confuse with |
|---|---|---|---|
| Customer 360 | Governed connected view | Cross-source decision context | A product category only |
| CDP | Platform category for customer data | Architecture evaluation | Guaranteed 360 quality |
| Identity resolution | Process for linking records | Match decisions | Whole activation system |
When it matters in practice
Customer 360 matters when a decision crosses source systems, newer events must override older ones, or customers need corrections reflected consistently. A small decision-specific view may be safer than a universal profile.
Limitations and common mistakes
Common mistakes are calling a data lake “360,” hiding conflicting fields, using latest write rather than business event time, copying permission across purposes, merging weak identities, and measuring record count instead of valid decisions.
Related terms and next step
Design the contract with the customer-data guide, diagnose fragmentation with AI customer experience failure modes, and apply a bounded decision using the personalization use case.
Evidence and limitations
No complete profile, match accuracy, legal permission, architecture recommendation, integration, or Easy AI capability is claimed.