A customer fills out your onboarding survey. They tell you they care about email deliverability, they use HubSpot, and they manage a team of three. That is the most valuable data you will collect from this customer all year. And it will stay in Typeform forever, because nothing connects Typeform to the tools where your team actually works.
This is the zero party data problem. Not collection. Activation. If you want to understand what is zero party data and why it matters, start here: the data itself is easy to get. The hard part is getting it out of the tool that captured it. (For how zero-party data fits into the broader data-type landscape, see our first-party data strategy guide.)
What zero-party data is and why Forrester coined the term
Forrester Research introduced the term "zero-party data" in 2020 to describe a category that the existing taxonomy missed. First-party data covers what you observe from customer behavior: page views, purchases, email clicks. But it doesn't cover what customers proactively tell you about themselves. That gap needed a name.
Zero party data is information customers intentionally and voluntarily share with you. Survey responses. Preference center selections. Onboarding flow answers. Communication channel choices. Feature interest ratings. Support ticket context that the customer typed into a text field, not something you inferred from their behavior.
The "zero" refers to the number of intermediaries between you and the data source. There are zero steps, zero brokers, zero inferences. The customer told you directly.
This distinction matters because the accuracy difference is significant. First-party data tells you a customer visited your pricing page. Zero-party data tells you they're evaluating your product for their sales team of 12 people. First-party data tells you a customer opened three support tickets. Zero-party data tells you they prefer email communication over live chat. One is observed. The other is stated. Both are valuable, but stated preferences drive personalization that behavioral data alone cannot.
Zero-party data vs. first-party data: what customers say versus what they do
The terms "zero-party" and "first-party" cause confusion because they overlap in one important way: both are owned by you, collected through your channels, and covered by your consent framework. The difference is how the data originates.
Data type | How it's collected | Example | Accuracy for preferences |
|---|---|---|---|
Zero-party | Customer states it directly | "I prefer weekly email digests" | Highest |
First-party | You observe their behavior | They open 4 of 5 daily emails | High, but requires inference |
Zero party data vs first party data is not a competition. They complement each other. A customer who says they prefer product updates over promotional content (zero-party) but consistently clicks promotional emails (first-party) tells you something neither data type reveals alone: their stated preference doesn't match their actual behavior. That gap is a signal. It means your promotional content is compelling enough to override their preference, or that they haven't updated their preference center in months.
The practical difference for small teams: first-party data is collected automatically by every tool you use. Zero-party data requires you to ask. That makes it scarcer, more intentional, and harder to replace if you lose it.
For a complete breakdown of all four data types and how they relate, see our first-party data strategy guide.
How to collect zero-party data without new tools
Every competitor article on this topic pushes the same pitch: buy a quiz platform, build interactive experiences, add gamification to your website. The implicit message is that zero party data collection requires new tools.
It doesn't. You are already collecting it. Here are six zero party data examples that exist in your stack right now:
Onboarding flows. When a new user signs up and you ask their role, team size, primary use case, and which tools they use, those responses are zero-party data. Most SaaS products collect 3-8 data points during onboarding that never leave the product database.
Feedback and NPS surveys. Post-interaction surveys, NPS scores, and CSAT ratings are zero-party data. The customer chose to respond. The response tells you something that behavioral data cannot: how they feel. These responses live in your survey tool or support platform.
Preference centers. Email frequency preferences, content topic selections, and communication channel choices. These are explicit statements of customer intent. They live in your email marketing platform.
Support conversations. When a customer tells your support team "we're migrating from Salesforce to HubSpot" or "we need this resolved before our board meeting on Thursday," that context is zero-party data. It lives in your help desk.
In-app surveys and feature requests. Product feedback forms, feature upvote boards, and in-app prompts that ask "what brought you here today?" generate zero-party data that typically stays inside your product analytics or feedback tool.
Account profile fields. Company size, industry, job title, and other fields the customer fills out in their account settings. These are self-reported data points that live in your product database or CRM.
The collection is not the bottleneck. The bottleneck is that each tool stores zero-party data locally, and none of it flows to the places where your team makes decisions.
Where zero-party data lives in your stack and how it gets trapped
Here is a concrete zero party data example of how fragmentation plays out. A B2B SaaS company with 2,000 customers has zero-party data scattered across five tools:
Tool | Zero-party data it holds | Who needs it |
|---|---|---|
Product database | Onboarding answers, role, team size, use case | Sales, support, marketing |
Typeform | Post-trial survey responses, feature priorities | Product, sales |
Intercom | Support preferences, migration context, pain points | Sales, marketing |
Mailchimp | Email frequency preferences, topic interests | Marketing, product |
HubSpot | Self-reported company size, industry, budget range | Sales, marketing, support |
Every team needs data that lives in a tool they don't use. The marketing team wants to send targeted emails based on onboarding answers, but those answers are in the product database. The sales team wants to know which features a prospect cares about, but that data is in Typeform. The support team wants to know a customer's communication preferences, but those are in Mailchimp.
The result is predictable: data stays where it was collected. Marketing sends generic emails because they can't segment by onboarding data. Sales asks prospects questions the product already answered. Support agents miss context that would change how they handle a ticket.
Enterprise teams solve this by routing everything through a data warehouse or CDP. That requires a data engineer, SQL models, and months of implementation. For a team of 15 or 50 people, the answer is simpler: connect the tools directly so that zero-party data flows from collection points to activation points automatically.
Activating zero-party data: sync preferences from your CRM to your email platform
Activation is where zero party data creates business value. The pattern is straightforward: collect once, sync everywhere, act on it in every tool.
Scenario 1: Onboarding answers drive email content. A customer tells you during signup that they care about "CRM data quality" and their team size is "5-20 people." Sync those two fields from your product database to your email tool. Now your marketing platform can segment by use case and team size without building a manual list. The customer receives content about keeping CRM data clean instead of generic product updates.
Scenario 2: Support preferences inform sales outreach. A customer tells your support team they're evaluating alternatives to their current data tool. That context, captured in a support ticket field, syncs to the CRM. The account owner sees it before their next check-in and can proactively address the evaluation instead of being blindsided.
Scenario 3: Survey responses update CRM records. A post-purchase NPS survey reveals that a customer scored you a 9/10 and mentioned they'd recommend your product for "billing automation." Sync the NPS score and the verbatim response to the CRM. Sales knows this account is a strong referral candidate, and the specific use case helps them match the referral to similar prospects.
The common thread: zero-party data has a shelf life. An onboarding answer from six months ago is less valuable than one from last week. But even stale zero-party data is more valuable than no data, which is what most teams have in their activation tools today.
Oneprofile connects your collection tools to your activation tools directly. Authenticate Typeform, Intercom, HubSpot, Mailchimp, your product database. Map the zero-party fields that matter: onboarding answers, survey scores, communication preferences, feature interests. Set a 15-minute sync schedule. Now every tool has the context that used to be locked inside one tool. No warehouse, no CDP, no data engineer. Your customers already told you what they want. We help that information reach the tools where you act on it.
What is zero party data?
Zero party data is information customers voluntarily share with you: survey responses, preference center selections, onboarding answers, and support preferences. Unlike first-party data, which is observed from behavior, zero-party data is explicitly stated.
What is the difference between zero-party and first-party data?
Zero-party data is what customers tell you directly. First-party data is what you observe from their behavior. A survey response is zero-party. A purchase history is first-party. Both are high-quality, consent-based, and owned by you.
How do you collect zero party data?
Through tools you already use: onboarding flows, feedback forms, preference centers, support conversations, and in-app surveys. You don't need a quiz platform or interactive content tool to collect it.
Why does zero party data get stuck in silos?
Each tool stores the data it collects locally. Typeform holds survey responses. Intercom holds support preferences. Your onboarding flow holds feature interests. Without sync, none of that data reaches your CRM or email tool.
Do I need a CDP to activate zero party data?
No. Direct tool-to-tool sync moves zero-party data from collection tools to activation tools without a CDP, warehouse, or SDK. Most teams under 200 people don't need centralized infrastructure to use their own data.