What Is Customer 360? A Practical Guide
Customer 360 is a unified view of a customer’s interactions and behavior across channels, connecting information from separate systems for analysis, segmentation, and customer interactions (AWS Customer 360 architecture).
Salesforce also uses Customer 360 as the name of its suite of connected applications for sales, service, marketing, commerce, and other functions (Salesforce Customer 360 guide).
What does a Customer 360 view contain?
A unified customer profile brings together selected attributes from source systems according to rules for choosing, matching, and merging their records (Microsoft data-unification overview).
Documented types of customer information include:
| Information | What it contains |
|---|---|
| Identity identifiers | Customer IDs, email addresses, device IDs, and other identifiers used to connect activity to a profile (Twilio Segment identity resolution). |
| Contact details | Names, email addresses, telephone numbers, and records of customer interactions (Salesforce CRM guide). |
| Transaction and service history | Purchase history, order status, and previous service interactions (Salesforce CRM guide). |
| Behavioral data | Events associated with a customer, together with profile attributes known as traits (Twilio Segment Profile API). |
| Audience membership | The audiences associated with a profile, available to downstream applications through supported interfaces (Twilio Segment Profile API). |
The subject of the profile matters: Segment supports individual user profiles and account-level data, including relationships between users and accounts (Twilio Segment identity graph).
How Customer 360 relates to CRM, CDPs, and warehouses
CRM systems, customer data platforms, and data warehouses have different customer-data functions (CDP Institute definitions).
| System | Its role in customer data |
|---|---|
| Customer relationship management system, or CRM | Manages customer and prospect relationships, contact information, sales opportunities, and service interactions (Salesforce CRM guide). |
| Customer data platform, or CDP | Software that maintains unified customer profiles over time and makes that database available to other systems (CDP Institute definitions). |
| Data warehouse | Collects data from business systems and organizes it for analysis; modern cloud warehouses can also form part of a customer-data architecture (CDP Institute definitions). |
Customer-profile functionality can also be distributed across several systems: warehouse-native architectures use separate components to provide CDP functions around an external warehouse (CDP Institute explanation of warehouse-native architectures).
How to build a unified customer profile
- Select and map profile data. Choose tables containing customer attributes and map their columns to descriptive types. Microsoft distinguishes these profile tables from one-to-many activity data such as purchases (Source-data selection).
- Remove duplicates within sources. Define rules that identify repeated customer rows and select the representative record (Deduplication).
- Match customers across sources. Specify the conditions that link customer records between tables (Matching conditions).
- Choose the resulting fields. Decide which columns to keep separate, combine, or exclude from the unified profile (Unified customer columns).
Identity resolution links identifiers and customer activity; Segment’s configurable rules determine which identifiers and sources create associations and can enforce uniqueness on selected identifiers (Twilio Segment identity-resolution rules).
For selecting field values after matching, Microsoft supports merge policies based on source importance, the most recent value, or the least recent value (Microsoft merge policies). Related fields can also be combined as a group so that one policy selects the group together (Microsoft field-group policies).
To deliver profiles to applications, Segment’s Profile API provides programmatic access to user-level and account-level identifiers, traits, events, and audiences, and supports embedding customer context in sales and support tools (Twilio Segment Profile API).
What is Customer 360 used for?
Salesforce describes the following Customer 360 uses (Salesforce Customer 360 guide).
| Function | Use of connected customer information |
|---|---|
| Sales | Understand customer needs and tailor sales conversations (Salesforce Customer 360). |
| Customer service | Resolve issues with the context of the customer’s interactions (Salesforce Customer 360). |
| Marketing | Segment audiences and personalize campaigns (Salesforce Customer 360). |
| Product development | Identify customer pain points and requested features (Salesforce Customer 360). |
Customer information can reach different applications: Segment documents profile access for third-party support tools, marketing platforms, and sales systems (Twilio Segment Profile API workflows).
Does Customer 360 require real-time data?
A Customer 360 architecture can include both batch and streaming data: AWS describes batch ingestion alongside real-time event ingestion and treats latency requirements as part of the processing design (AWS batch and streaming architecture).
The same architecture separates collection, unification, analytics, activation, and governance, distinguishing the work of bringing sources together from making the resulting information available for customer interactions (AWS Customer 360 design).
How to maintain a trustworthy customer view
In Microsoft Customer Insights, updates to source data or matching rules can merge previously separate profiles or split an existing profile, affecting customer IDs (Microsoft profile and ID behavior).
Data lineage records where information originated, how it was transformed, and where it moved, helping trace errors through the data pipeline (IBM data-lineage guidance). Data governance adds ownership, business definitions, rules, and policies for managing that information (IBM explanation of governance and lineage).
For Customer 360, this translates into practical maintenance checks: document the source and transformation of profile fields, identify who maintains them, and trace corrections through downstream uses. These checks follow the lineage and ownership practices described in IBM’s data-lineage guidance.
Privacy, access, and consent
Where the GDPR applies, personal-data processing must have a defined purpose, and the information processed must be relevant and limited to what that purpose requires (European Commission GDPR principles). The guidance also covers accuracy, retention limits, and access restricted to people who need the data (European Commission GDPR principles).
For a unified customer view covered by the GDPR, privacy safeguards belong in the processing design, with limited access and only necessary personal data processed by default (European Commission guidance on data protection by design and by default).
Segment’s Profile API does not return a user’s consent preferences in profile responses, so retrieving a profile does not, by itself, retrieve those preferences (Twilio Segment Profile API limitation).