Key takeaways
- Zero-party data usually means information a person deliberately shares about preferences or intentions.
- It is a useful industry distinction within direct data collection, not a universal legal category.
- A stated preference has a context and can change; preserve both.
Overview
The term highlights the difference between what someone tells you and what you infer from their behavior. It is not a separate legal category or a guarantee that the information remains current. Store the exact question, response context and date when those details affect interpretation. People should be able to update preferences when their needs change.
How it works
Ask a clear, relevant question with an understandable purpose.
Store the stated response separately from behavioral inferences.
Use and refresh the preference within the scope communicated to the person.
Distinguish a stated answer from inferred behavior
A user choosing “send me product updates monthly” has stated a preference. A system inferring that preference from page visits has not. The distinction is useful because an explicit answer can reduce guesswork, but the answer still refers to a particular question, set of options and moment in time. Store that context rather than reducing it to an unexplained label.
The term is used in marketing practice and can overlap with first-party data because the organization receives the answer directly. It does not create a separate technical storage format or determine legal obligations by itself. Keep collection, purpose and permission decisions grounded in the actual interaction rather than the category name.
| Interaction | What is stated | What remains unknown |
|---|---|---|
| Preference center | Chosen topic or frequency | Interest in unrelated messages |
| Onboarding questionnaire | Reported role or intended use | Whether the person has purchasing authority |
| Product selection quiz | Answers to the presented choices | Preferences the question did not ask about |
Ask questions that improve the immediate experience
A short onboarding question can route a user to relevant examples or set a preferred workflow. Explain the benefit and avoid collecting details that do not change the experience. Long questionnaires can produce skipped answers or low-quality responses, especially when users cannot see why the information is needed.
Keep “not sure” and optional answers where they reflect real uncertainty. Forcing a person to choose a role or intention that does not fit can create false precision in segmentation. If the application later infers additional attributes from the answers, label those as inferences rather than pretending the person explicitly supplied them.
Let people revise the answer
Preferences and intentions change. Make important choices accessible for review and update, and ensure connected destinations receive the latest state. An old onboarding answer should not permanently override a later preference-center selection. Record effective dates and precedence rules so scheduled syncs do not restore superseded values.
In an illustrative onboarding flow, a user selects “research accounts” and later switches to “maintain CRM data.” The application can update recommended workflows without rewriting the history of what the user originally chose. Evaluate whether the questions improve setup completion or relevance, and review the collection notice and applicable requirements for any additional use.
What this looks like in practice
A buyer selects “CRM data cleanup” as their main interest during onboarding. The team treats it as a stated preference, while keeping a later inference about sales readiness in a different field.
Examples explain the concept; they are not reported customer results.What to check
Check response clarity, optionality, recency and whether the information changes a useful experience. Avoid collecting personal details that do not support the stated purpose.
Common mistake
Calling an inferred interest zero-party data, or treating a preference answer as blanket permission for unrelated marketing.
Zero-party data vs. First-party data
First-party data includes information from direct interactions broadly. Zero-party data is commonly used to emphasize the subset that people deliberately state rather than behavior the organization observes.
Read the First-party data definition →Questions answered
What is Zero-party data?
Zero-party data is a marketing term for information a person intentionally and proactively shares with an organization, such as stated preferences, interests or purchase requirements.
Is a preference the same as consent?
No. A product preference and permission for a particular marketing activity answer different questions. Store and honor them separately.
Can stated preferences become outdated?
Yes. Give people a way to update them and retain timestamps. A response from last year may not describe today’s priorities.
Is zero-party data always more accurate?
It is direct evidence of the answer given, but the person may misunderstand the question, choose an approximate option or change their mind later. Treat it as a dated statement in context. Do not assume that a self-reported role or purchase intention is independently verified.
Does a stated preference equal consent for every channel?
No. A preference and permission for a particular use are different questions. The meaning depends on what was asked, explained and agreed, together with applicable requirements. Keep channel choices and their context explicit instead of expanding one answer into a general authorization.
References and further reading
Primary documentation and source material for this topic. Sources checked September 14, 2026; provider requirements can change.
- Direct marketing guidance ↗UK Information Commissioner’s Office
UK-specific guidance updated April 2026; requirements vary by jurisdiction and channel.
- Data minimisation ↗UK Information Commissioner’s Office
UK-specific guidance. The ICO flags this page as under review following legislative changes.
Continue reading on the blog
Explore all articles and guides →Put the concept to work.
Explore the relevant AstroFabric workflow and see how the pieces connect.
Help keep this guide useful. Suggest a correction or browse the full glossary.