Glossary: Customer 360
Customer 360 is a unified view of a single user that merges every data source, onchain activity, product usage, web sessions, socials, and support history, into one complete profile.
What is Customer 360?
Customer 360 is a unified view of a single user that merges every data source, onchain activity, product usage, web sessions, socials, and support history, into one complete profile.
Customer 360 Explained
Imagine a doctor whose records are scattered: one file at the pharmacy, one at the lab, one at a previous clinic. No single person sees the whole patient.
Most crypto teams run their user data the same way. Wallet activity in one tool, web analytics in another, Discord and email lists somewhere else. Each shows a fragment.
Customer 360 merges the fragments into one profile per user: the wallet's onchain history, the sessions before it connected, the campaigns it came from, the socials and forms it verified. One record that tells the whole story.
What Customer 360 Means For
Audience | Use Case |
|---|---|
Growth and marketing teams | Target and personalize based on a user's complete history rather than one channel's fragment |
Product and support teams | See a user's full context, usage, value, history, when making product or support decisions |
Data teams | Consolidate fragmented sources into a single user-level model that every team queries |
Examples
A protocol's Customer 360 profile shows a wallet's first campaign touch, web sessions, transactions, net worth, and Discord handle in one view.
A support team resolves a VIP's issue faster because the profile shows their full deposit history and lifecycle stage.
A growth team builds a segment of high-net-worth wallets that engaged with a campaign but never transacted, using unified profile data.
A founder reviews revenue by acquisition channel using profiles that join marketing touchpoints to onchain fees.
Related reading
Explore User Profiles, Identity Resolution, User ID, and PII (Personally Identifiable Information).
FAQs
What data can feed a Customer 360 for a crypto app?
Potential sources include app events, campaign context, support records, wallet connections, and relevant onchain activity. Include only data with an appropriate basis and reliable linkage, and preserve whether an identifier is user-provided, observed, or inferred.
How is Customer 360 different from a wallet profile?
A wallet profile describes observed activity associated with an address. A Customer 360 view may combine app, support, and wallet records when there is a justified link. It should show evidence and confidence rather than assume all addresses belong to one person.
Why is Customer 360 harder in crypto apps than Web2?
There is no central account. Identity must be resolved across pseudonymous wallets, devices, and platforms before a unified profile is possible.
What is Customer 360 used for?
Segmentation, personalization, VIP identification, accurate retention and LTV measurement, and giving every team the same complete picture of each user.
What should teams evaluate in a unified customer data tool?
Review supported data sources, identity-link evidence, permissions and retention controls, correction workflows, exportability, and how uncertain matches are represented. No tool can guarantee a complete person-level view from public blockchain data.
The data platform onchain apps
Get actionable analytics and attribution for crypto and DeFi.
Stay up to date with weekly product updates and the latest industry insights.
Platform