Picture a member who earns points in the app on Monday. On Tuesday she calls support about a late order. On Wednesday she gets an email offer for the item she already returned. Each system did its job. None of them saw the whole person. A customer 360 closes that gap.
What is a customer 360?
A customer 360 is one unified view of every data point about a single customer. RudderStack defines it as a view of every available data point for one customer, drawn from every source and touchpoint in the customer lifecycle (RudderStack). The aim is a single source of truth for each customer. The 360 is a figure of speech for all sides of the customer.
The name has a second meaning. Salesforce sells a suite called Customer 360. Its page says the apps give a complete view of customers across all touchpoints (Salesforce). This entry uses the general meaning. It is the unified view itself, whichever tool builds it.
Firms want it because of how people buy. Lemon and Verhoef say customers now deal with firms through many touch points and channels. That requires firms to link their business functions (Lemon and Verhoef, 2016). Payne and Frow name two of five CRM processes: multichannel integration and information management (Payne and Frow, 2005). A customer 360 is the data behind both.
What data goes into a customer 360?
RudderStack lists common sources (RudderStack). They are websites, apps, CRM systems, e-commerce platforms, email tools, support systems, social media and offline sales. A CRM is typically one of many inputs. The table groups the data by type and gives a loyalty example of each.
| Data type | What it holds | Usual source | Loyalty example |
|---|---|---|---|
| Identity | Name, email, phone, member ID | Sign-up, login | Member number and linked email |
| Transactions | Purchases, returns, spend | Point of sale, e-commerce | A basket and the points it earned |
| Behavior | Visits, app opens, clicks | Web and app analytics | Date of the last redemption |
| Interactions | Calls, chats, cases | Support desk, contact center | An open complaint on an order |
| Preferences | Stated choices, consent | Forms, preference center | Email opt-in, favorite store |
| Relationships | Household, employer, linked accounts | Account data | A family pool of points |
| Derived | Segments and scores | Analytics models | Churn risk, value tier |
Derived data comes last because it depends on the rest. A score built on half a record is a half-informed score.
How do you build a customer 360?
Building one takes five steps. List every source that holds customer data. Pick the key that ties records together, such as a member ID. Match the records that belong to one person. Clean the result. Then keep it current and open to the teams that act on it.
The match step is identity resolution, and the whole project rests on it. RudderStack puts the test this way: can you identify a single customer across two or more data sources today? If not, identity resolution is the first gap to close (RudderStack).
Clean data is the next step. Reltio lists four fixes (Reltio). They are cleansing, removing duplicates, using one format and checking values. These keep customer data accurate, complete and consistent. Elastic adds that data should update all the time (Elastic). Then each profile shows the latest sales and contacts.
Starbucks shows the key at work (Starbucks Rewards Terms). It lets a member add multiple cards. It allows only one personal account per member. It also reserves the right to combine accounts that look like duplicates. Guest checkout earns no Stars. So the account is what links a purchase to a person.
Why do customer 360 projects fall short?
Elastic lists the usual causes (Elastic). They are mixed data formats, poor quality, cost, staff resistance and silos that persist. Three problems stand out.
Stale data comes first. A profile built from a nightly file is up to a day old when someone acts on it. Duplicates come second. Two records for one person split that person’s history, so each record looks like a weaker customer than the real one. Missing links come third. A profile has gaps wherever a purchase carries no identity, as with guest checkout.
Elastic advises a phased rollout with ongoing monitoring (Elastic). In practice that means one job first, such as recognition at the service desk. Widen the view once that job works.
What are the privacy limits of a customer 360?
Privacy law applies to a customer 360, since it is a profile of a person. GDPR covers any data about a person who can be identified (GDPR Article 4). A unified profile fits that.
GDPR also defines profiling. It means automated use of data to judge a person. The law lists likes, interests and movements as examples. A unified profile fits that too.
Two more rules shape the design. Article 5 says personal data must be adequate, relevant and limited to what the purpose needs. It calls this data minimization (GDPR Article 5). Article 15 gives a person the right to a copy of the data a company holds. It also covers why the company holds it. Where the data did not come from the person, it covers any available information on the source (GDPR Article 15).
So a customer 360 needs an answer to three questions. What do we hold on this person? Why do we hold it? Where did it come from? The public is wary. Pew Research Center surveyed 4,272 U.S. adults in June 2019. It found that 81% say the potential risks of company data collection about them outweigh the benefits. The same share say they have very little or no control over what companies collect (Pew Research Center). This describes the text of the law and one survey. It is not legal advice.
How do loyalty programs use a customer 360?
A loyalty program is a natural identity source. Our CDP guide says a program can be the identity spine when it is the main identity source, since members log in and identify at purchase. Every earn, redemption and service contact then lands on a known member.
Programs put that view to four uses. Staff recognize the member at any desk or counter. Offers reflect what the member already bought. Service sees the offer history. Retention teams spot a drop in activity early, and they can track it by cohort.
For illustration, a retailer holds 120,000 customer records across four systems: the point of sale, the app, the email list and the service desk. Matching on member ID, email and phone links them to 80,000 people. That is 1.5 records per person on average. Suppose every record has an email address. A campaign sent to every record then reaches each person 1.5 times on average. After matching, it reaches each person once. The same view lets marketing hold an upsell email for a member with an open complaint.
How GRAVTY handles customer 360
Our name for it is Member 360. Our Enterprise Growth Platform page says Member 360 pulls behaviors, influences and transactions into one view.
Our financial services page adds two more parts. One is household pooling. The other is the affiliation graph. Both capture the relationships around the member.
Our telecom page describes one identity per member, resolved across email, phone, card and app. App, web, store, contact center and partner checkout systems read from one real-time member graph.
Frequently asked questions
What does customer 360 mean?
Customer 360 means one unified view of a single customer, drawn from every source and touchpoint (RudderStack). Salesforce also uses the name for a product suite (Salesforce). The general meaning is the view, whichever tool builds it.
What data goes into a customer 360?
It holds who the customer is, what they bought and what they did. It also holds service history, preferences, household ties and scores. Sources include websites, apps, CRM systems and support desks, plus offline sales (RudderStack).
What is the difference between a customer 360 and a CRM?
A CRM is typically one input among many (RudderStack). It holds sales and support records. A customer 360 adds what people do on your site and in your app, plus marketing data.
Does GDPR allow a customer 360?
GDPR sets limits on a unified profile and does not ban one. Personal data must be limited to what is necessary for the purposes of processing (GDPR Article 5). A person has the right to a copy of the personal data held on them (GDPR Article 15). This is not legal advice.
How do loyalty programs build a customer 360?
They build it on the member ID. Members log in and identify at purchase, so the program already ties each purchase to a person. Starbucks, for example, lets a member add multiple cards to one personal account (Starbucks Rewards Terms). Matching and cleaning then merge the remaining records.
