Customer data glossary

Customer 360

By Art Kukharenko · Published · Updated

Browse learn glossary resources

Customer 360 is a comprehensive view of a customer that joins profile data, transactions, interactions and preferences from every channel into one place for analysis and service.

Part of the Learn hub and the customer data glossary.

What it means in practice

Customer 360 is an outcome more than a product: the ability to see a customer's whole relationship with the organisation. The "360" implies completeness, which is a goal rather than a state; most implementations cover some domains well and others only partly.

A typical data model groups information into domains: identity and verification, products and holdings, transactions, service interactions and complaints, digital behaviour, consent and preferences, and derived values such as scores and segments. It can be built in a customer data platform (CDP), on a warehouse with a semantic layer, or from CRM plus master data management. The data model and governance matter more than the tool.

Customer 360 and single customer view overlap. A useful distinction: the single customer view stresses completeness of identity and holdings, while customer 360 stresses breadth of context for service, risk and personalisation.

The risk is accumulation. The more attributes attach to one profile, the more harm a misuse or breach can do, and the harder purpose limitation becomes. Role-based access, field-level controls and data minimisation apply: a relationship manager, a call-centre agent and a marketer should see different slices of the same profile.

Example (retail banking): a bank's profile holds product holdings, app activity and complaint status. Marketing sees only an approved list of attributes, and an open complaint removes the customer from promotional journeys until it is resolved.

Where it matters

Frequently asked questions

Does customer 360 need real-time data?

Not necessarily. Service and risk use cases often need fresh data on key events, while analytics can accept a daily refresh. Define the freshness each use case needs rather than aiming for real time everywhere.

Is patient 360 the same thing in healthcare?

It is the equivalent view for patients, but the data is usually protected health information, which raises access, contract and logging requirements. See the patient 360 article for where engagement data should live relative to the EHR.

Can a customer 360 be built without a CDP?

Yes. Warehouse-based builds and CRM plus MDM combinations can deliver one. A customer data platform is one route, valued mainly for packaged identity, consent and activation features.

Back to the customer data glossary or the Learn hub.

Further reading

Published: · Updated:

Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.

Need help?

Ask the PrivyCDP Assistant