Zero-party data is one of the few marketing terms where the concept is more useful than the category. The distinction it draws — between what a customer told you and what you worked out about them — genuinely changes how you design a personalisation programme. The standalone software market implied by the phrase barely appears in these interviews: a single buyer is in market for zero-party data collection as a category, and the handful who use the phrase at all are describing something they already do with tools they bought for other reasons.
What is zero-party data?
Zero-party data is information a customer deliberately and proactively gives you about themselves — preferences, intentions, a birthday, a skin type, who they are shopping for and why.
The defining feature is intentional disclosure: the customer knows they are providing the information and expects the business to use it. It arrives through things people answer on purpose — onboarding quizzes, preference centres, post-purchase surveys, profile fields.
What is the difference between zero-party and first-party data?
First-party data is data you collect directly through your own customer relationship; zero-party data is the subset a customer intentionally and explicitly provides. They are not two separate buckets — the second sits inside the first.
In practice the useful distinction is between what the customer told you and what you observed or inferred from their behaviour: pages viewed and items bought on one side, a stated preference for email over SMS or an answer that they are buying a gift on the other.
The practical difference is what each can and cannot establish. Observed data is typically more abundant and inferential: a customer who browsed three pairs of running shoes probably wants running shoes, but you are guessing about why. Volunteered data is scarce, asks the customer for effort, and states an intention no behavioural signal can establish on its own — that the shoes are a gift, and for someone with a different shoe size.
That asymmetry is the whole reason the term exists. It is not that volunteered data is better in general — people misremember, change their minds, and answer strategically — it is that a small amount of it answers questions a large amount of behavioural data cannot.
What are the four types of customer data?
These labels are not perfectly parallel. First-, second- and third-party describe the relationship between the collector and the data source. Zero-party describes how intentionally the customer supplied the information — which is why it overlaps first-party rather than sitting beside it.
| Type | Where it comes from | Example | What it costs to get |
|---|---|---|---|
| Zero-party | Volunteered by the customer, knowingly. | A quiz answer saying they are shopping for a gift. | Customer effort, and friction at the moment you ask. |
| First-party | Collected directly by you through your own customer relationship. | Pages viewed, purchases made, or profile information provided directly. | Instrumentation, governance and storage. |
| Second-party | Another organisation's first-party data, accessed through a direct partnership. | A retailer making purchase signals available to a brand it stocks. | A commercial agreement, often under controlled collaboration arrangements. |
| Third-party | Collected or aggregated by an outside organisation with no direct relationship to your customer. | A purchased audience segment. | Money, and diminishing reliability as tracking degrades. |
The useful axis running through them is proximity to an explicit customer statement — which is not the same as quality. Volunteered data answers questions behavioural data cannot; observed data is sometimes the better indicator of what people actually do. It is a distinction worth holding, not a ranking: a preference a partner collected explicitly can sit closer to the customer's own words than behaviour you inferred yourself. Second-party data is the label most often misunderstood: it is not a category you buy, it is someone else's first-party data reached through a partnership, which is why it usually arrives alongside a conversation about controlled data collaboration.
Do buyers actually use the term zero-party data?
Rarely. Only a handful of interviews in this corpus use the phrase, and one buyer is in market for zero-party data collection as a software category.
That is a striking gap for a term with this much vendor marketing behind it, and it is worth being precise about what it does and does not mean. It does not mean buyers are not collecting volunteered data — they are, constantly, through quizzes and preference centres and post-purchase surveys. It means they do not call it zero-party data, and they do not shop for a product under that name.
The categories where this work actually appears in buying activity are the ordinary ones: feedback and surveys, customisable quizzes, consent management. The practice appears far more often than the label, which is the reverse of how most emerging-category vocabulary behaves.
How do buyers collect zero-party data?
Through preference capture, quizzes and product finders, post-purchase surveys and profile fields — usually running on email, survey, review or quiz tools they already own rather than a dedicated zero-party data platform. Nobody in these interviews describes buying one.
On-site capture
Pop-ups and preference fields that ask a question during signup, when the customer is already providing information.
Quizzes and product finders
Onboarding or product-recommendation quizzes that collect stated needs and return a recommendation in the same interaction.
Post-purchase surveys
Questions asked after the transaction is complete, often used for attribution — how did you hear about us — as well as feedback and preference capture. The same collection mechanism either way.
The tools running this in these buyers' stacks are the ones they bought for email, reviews, surveys and quizzes: Klaviyo, Okendo, KnoCommerce, Fairing, Digioh, Zigpoll, Typeform. None of them is sold primarily as a zero-party data product, and buyers do not describe them that way.
Is zero-party data an alternative to a CDP?
Not generally. A CDP unifies and activates customer data across sources; zero-party data describes information customers intentionally provide. One buyer in these interviews deliberately chose a narrower zero-party strategy instead of implementing a CDP, but that was a scope decision rather than a like-for-like substitution.
The reasoning is worth reading closely, because it inverts the usual maturity story.
A mid-size apparel brand decided against a customer data platform after finding them difficult to leverage effectively in past experience. Instead it collects preferences directly from customers through site pop-ups — birthdays, first-purchase details — and houses the result in its email platform. The stated rule is to personalise communication only with data the customer provided themselves.
That is a deliberate scope reduction rather than a substitution. A CDP and a preference centre do not do the same job; what the brand did was deliberately narrow the personalisation problem, and therefore need less infrastructure to solve it. Whether that trade is right depends entirely on whether the personalisation you are giving up was working — and this buyer's position is that in their case it was not. It is one account, not a pattern, but it is the clearest articulation of the trade in the corpus.
Want this read against your own stack?
Get my read →Should you invest in collecting zero-party data?
Only where you would act on the answer. Every question asks the customer for additional effort and can add friction, so the test is whether a different answer would change what you send, show or recommend.
The obvious failure mode is a quiz whose results nothing downstream consumes. The data gets collected, stored in the tool that collected it, and never reaches the email flow or the product page where it would have made a difference. That is worse than not asking, because the customer told you something and then watched you ignore it.
Three practical principles follow from the patterns in these interviews. Ask few questions, because each one has a cost. Ask at moments the customer already expects an interaction — signup, a product finder, after delivery. And use the answer visibly downstream, so the next interaction reflects what was said.
The framing that survives the evidence is this. Zero-party data is a useful distinction and a poor shopping list. The question is not which tool to buy for it — it is which single question you would ask if you could only ask one, and what you would do differently with the answer.
Common questions
What is zero-party data?
Zero-party data is information a customer deliberately and proactively gives you about themselves — preferences, intentions, birthdays, skin type, what they are shopping for and why. The defining feature is intent: the customer knows they are telling you, and they expect you to use it. It is collected through things people answer on purpose, such as onboarding quizzes, preference centres, post-purchase surveys and profile fields, rather than observed from what they do.
What is the difference between zero-party and first-party data?
First-party data is data a company collects directly through its own customer relationship; zero-party data is the subset a customer intentionally and explicitly provides, so the second sits inside the first rather than beside it. In practice the useful distinction is between what the customer told you and what you observed or inferred from their behaviour — pages viewed and items purchased on one side, a stated preference or an answer that they are shopping for someone else on the other. Observed data is typically more plentiful; volunteered data is scarcer, asks the customer for additional effort, and states an intention no behavioural signal can establish on its own.
Is zero-party data a type of first-party data?
Zero-party data is commonly treated as a distinct label for information customers intentionally provide, but it also arrives through a company's own first-party relationship with the customer. The useful distinction is not primarily who collected it: it is whether the customer explicitly stated the information or the company observed or inferred it from behaviour. A preference entered into a profile is zero-party; a product view recorded on the same site is observed first-party data.
What are the four types of customer data?
Zero-party data is information a customer intentionally provides. First-party data is data a company collects directly through its own customer relationship, and can include both observed behaviour and customer-provided information. Second-party data is another organisation's first-party data accessed through a direct partnership. Third-party data is collected or aggregated by an outside organisation with no direct relationship to your customer. The useful axis running through them is proximity to an explicit customer statement, which is not the same as quality: volunteered data answers questions behavioural data cannot, while observed data is sometimes the better indicator of what people actually do. The labels are also not perfectly parallel — first-, second- and third-party describe the relationship between the collector and the source, while zero-party describes how intentionally the customer supplied the information.
Do buyers actually use the term zero-party data?
Rarely. In this corpus only a handful of interviews use the phrase at all, and just one buyer is in market for zero-party data collection as a software category. The distinction it describes is real and useful, but as a purchasing category it barely exists: buyers describe collecting volunteered data constantly while almost never calling it that. Treat the term as useful vocabulary for a design decision, not as a market you need to shop.
How do buyers collect zero-party data?
With tools they already own. In these interviews the collection happens through on-site pop-ups and preference capture, onboarding and product-finder quizzes, and post-purchase surveys — running on email platforms, quiz and survey apps and review tools rather than a dedicated product. The names that appear in these stacks include Klaviyo, Okendo, KnoCommerce, Fairing, Digioh, Zigpoll and Typeform. Nobody in these interviews describes buying a zero-party data platform.
Is zero-party data an alternative to a CDP?
Not generally. A CDP unifies and activates customer data across sources; zero-party data describes information customers intentionally provide. One buyer in these interviews deliberately chose the narrower path: a mid-size apparel brand decided against a CDP after finding them hard to leverage in past experience, and instead collects preferences directly from customers through site pop-ups, housing the result in its email platform. Its stated rule is to personalise communication only with data the customer provided themselves. That is a deliberate scope reduction rather than a substitution — it makes personalisation simpler and narrower, and it works because the brand chose to want less.
Should you invest in collecting zero-party data?
Only where you would act on the answer. Every zero-party question asks the customer for additional effort and can add friction at the point you ask, so the test is whether a different answer would change what you send, show or recommend. Three principles follow from these interviews: ask few questions, ask at moments the customer already expects an interaction, and use the answer visibly downstream. The failure mode is a quiz whose results nothing downstream consumes.
Get this research made for your stack
Whether collecting more volunteered data is worth the friction depends on your category, your repeat rate, and what you would actually do differently with the answers. Do a 15-minute interview and get the version of this that applies to you: what peers collect, where they ask, and what they do with it.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.