What is zero-party data?

Zero-party data is information a prospect or customer intentionally and proactively shares with you, such as their goals, timeline, budget range, current tools or biggest problem. It differs from first-party data (behavior you observe, like page visits), second-party data (another company’s first-party data shared with you) and third-party data (bought or inferred from outside sources).

TL;DR

Declared, not inferred: the buyer told you directly.
High signal: it reflects what the buyer says they want, not what a model guesses.
Common sources: form questions, assessments and calculators, onboarding surveys, discovery calls, reply content.
Only valuable if it is stored in a field that routing, scoring and messaging can use.

Why it matters for a B2B pipeline

Enrichment can tell you a company has 200 employees and uses HubSpot. It cannot tell you that the head of sales wants to replace an outbound agency before Q3. That second fact decides routing, priority and the first message. Zero-party data is also durable in a world of shrinking third-party tracking: cookie restrictions and privacy rules do not affect information someone typed into your form. For B2B, the most valuable zero-party fields are usually timeline, current solution and the problem in their own words.

Example

A GTM assessment asks five questions: team size, current outbound tools, monthly meetings booked, biggest bottleneck (from a list), and when they want to fix it. A submission saying “two SDRs, booking under ten meetings a month, bottleneck is list quality, want it fixed this quarter” is routed straight to a senior rep with that context attached. The first call opens on list quality, not a generic discovery script, and a “next year” answer goes to nurture instead of an AE calendar.

How to collect and use it

Ask only what changes an action. If an answer will not change routing, scoring or messaging, drop the question.
Give something back: a score, benchmark, recommendation or instant booking in exchange for answers.
Use picklists for anything you will segment on, and one free-text field for the problem in their words.
Map every answer to a CRM property before launching the form.
Feed it into lead scoring and routing, alongside enrichment and intent data.
Capture it from conversations too: call notes and reply text can be written back to structured fields automatically.

Common mistakes

Collecting answers that sit in a form tool and never reach the CRM.
Asking for data you could enrich, which lowers form conversion.
Long forms on first touch.
Treating declared timeline as permanent instead of re-asking later.

Zero-party data