Analytics and Tracking

Zero-Party Data

Also called 0PD, declared data

Information a customer hands over deliberately — preferences, intentions, answers — rather than something inferred from behaviour.

Quick facts: Zero-Party Data

Category
Analytics and Tracking
Also called
0PD, declared data
Level
Beginner
Affects
Segmentation quality, email relevance, dependence on tracking
Where to see it
Preference centre, CRM custom fields, onboarding questions, post-purchase surveys
In this article4
  1. How zero-party data works
  2. Why zero-party data matters
  3. Where zero-party data goes wrong
  4. How to act on it

How zero-party data works

It arrives through a deliberate act. Someone answers a question in a preference centre, picks a category during sign-up, fills in a short survey after buying, tells a quiz what they are shopping for, or replies to an email saying which of two topics they want more of. The defining feature is that the person knows they are telling you and chose to.

That is what separates it from first-party data, which you observe on your own properties: pages viewed, products bought, emails opened. Observed data shows what someone did; stated data shows what they say they want. Both are useful, and they disagree more often than you would expect, which is itself informative.

Why zero-party data matters

As shared identifiers disappear from browsers and platforms, the data you were given directly is the part that survives, because it never depended on tracking anyone across the web. It also needs no modelling: a stated interest is what it says it is, with clean provenance and a permission trail attached.

For a smaller business it is usually the cheapest route to relevance. Platform audience data in a market like Nepal is thin and the segments are broad, so asking a customer one direct question will often beat any inference you could buy or build. And an answered question raises the odds that the next message is worth opening.

Where zero-party data goes wrong

The first failure is asking for things you have no plan to use. Every extra field costs completions, and every stored answer creates a retention duty, so a long form buys you less usable data than a short one.

The second is asking and then ignoring the answer. Somebody tells you they only want product updates, then receives the weekly promotional email anyway. That does more damage than never asking, because they know you know. Third, the answers often land in a form tool nobody connects to the CRM, so they exist but never reach a campaign. Fourth, stated preferences age: a person’s needs move on, and a two-year-old answer treated as current will misfire.

How to act on it

Pick one or two questions whose answers would genuinely change what you send, and drop the rest. Ask at a moment when answering pays the person back immediately — during onboarding, at a preference step, or straight after a purchase when the topic is already on their mind.

Write each answer into the customer record as a proper field rather than a note, so it can drive segmentation, and give people a preference centre where they can change it themselves. Re-ask occasionally rather than assuming the answer holds, and be honest in the question about what you will do with it, which raises both response and trust. Getting this into a working email marketing programme is where the effort pays off.

Do and do not

Do

  • Ask only questions that change what you send
  • Store each answer as a field, not a note
  • Let people update their preferences themselves

Do not

  • Collect answers you have no plan to use
  • Send the same campaign to someone who chose otherwise
  • Treat an old stated preference as still current

Questions people ask about this

How is zero-party data different from first-party data?

First-party data is what you observe on your own site, app or shop: pages visited, orders placed, emails opened. Zero-party data is what the person deliberately tells you: their preferences, budget range, role or reason for buying. One is behaviour you recorded, the other is a statement they chose to make, and the second usually carries clearer permission.

What is the easiest way to start collecting it?

Add one question to a step people already complete. A single choice at newsletter sign-up asking which topic they want, or one question on the order confirmation asking what prompted the purchase, is enough to begin. Store the answer as a field in your CRM, use it in the next send, and only add a second question once the first is genuinely being used.

Do I still need consent if the customer volunteered the information?

Yes, for how you use it. Volunteering an answer to one question is not blanket permission to market by any channel forever. Say what the answer will be used for at the point you ask, keep the marketing consent separate and recorded, and honour withdrawal. Collecting it openly makes the permission easier to obtain, not unnecessary.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.