The complete guide for eCommerce
Zero-party data: the complete guide for eCommerce (2026)
Preference information your shoppers volunteer at the moment they're most engaged. The most accurate and most privacy-compliant signal a retailer can act on, and the structural replacement for cookie-based targeting in 2026.
Used by 20,000+ ecommerce brands · 4.9 ★ on Shopify · Built for Shopify certified
Definition
Zero-party data is information a customer intentionally and proactively shares with a brand: preferences, intents, goals, and how they want to be recognised. Unlike first-party data (observed behaviour) or third-party data (purchased from intermediaries), zero-party data is given freely in exchange for value, which makes it the most accurate and the most privacy-compliant signal a retailer can act on.
If you sell online in 2026, your customer-data stack determines what you can personalise, who you can reach, and what you can prove to a privacy regulator. The single most strategic upgrade you can make to that stack this year is to start collecting zero-party data.
This guide covers what zero-party data is, how it compares to first-party, second-party, and third-party data, why it matters more in 2026 than it did in 2022, the six proven methods for collecting it, and the channels where it produces measurable lift.
The term zero-party data was coined by Forrester analyst Fatemeh Khatibloo in 2018 to describe a category of customer signal that didn't fit cleanly under "first-party" (observed) or "third-party" (purchased). Eight years later the distinction is no longer academic: cookie deprecation, the EU AI Act, and the rise of agentic shopping have made declared preference data a structural moat. Brands that already have a zero-party pipeline in production are compounding an advantage that brands relying on inferred third-party signals can no longer access.
This page is the canonical RevenueHunt reference on zero-party data. For the wider category that contains it, see first-party data. For the format that produces it most efficiently, see ecommerce quiz. For the strategic context, see the retention pillar this activates. For the platform that turns it into revenue, see RevenueHunt's product recommendation quiz.
Zero-party vs first-party vs second-party vs third-party data
The four data types differ on three axes: who collected it, how it was obtained, and how reliable it is. Marketers conflate them constantly, and the conflation has cost.
Fig. 01 Zero-party is what the customer told you, first-party is what you watched them do, second-party is what a partner shared, third-party is what someone else inferred about them. They are not interchangeable.
| Data type | Who collected it | How it's obtained | Example | Accuracy |
|---|---|---|---|---|
| Zero-party | You | Customer volunteers it in exchange for value | "My skin is sensitive. I'm shopping for a gift." | Highest |
| First-party | You | Observed: site analytics, purchase history, CRM, email engagement | "Visited 3 product pages, bought vitamin C serum 6 months ago" | High |
| Second-party | A partner brand | Shared from a partner's first-party set via a direct agreement | A co-marketing partner shares its newsletter list with you | Variable |
| Third-party | An intermediary you don't own | Aggregated, inferred, or purchased from data brokers, ad networks, look-alike audiences | "Females 25-34 likely interested in skincare" from an ad network | Lowest |
The other important distinction is the relationship between zero-party and first-party data. Zero-party is a subset of the broader first-party umbrella in some industry frameworks: you own both, you collected both, both live on your infrastructure. The reason marketers separate them is intent: first-party data is observed, zero-party data is declared. Observed data is excellent for retargeting, replenishment, and propensity modelling. Declared data is excellent for personalisation, segmentation, and consent. You want both. The gap most stores have is zero-party data. For the broader first-party-data picture, see our companion guide.
Why zero-party data matters in 2026
Four shifts have moved zero-party data from a "nice to have" to a structural advantage.
01
Third-party cookies are finally biting
Safari and Firefox killed third-party cookies years ago. Chrome's rollout means cross-site behavioural targeting now reaches a fraction of audiences it used to. Look-alike audiences built on cookie graphs degrade weekly. The only durable replacement is data you own, and the highest-resolution version of that is zero-party.
02
AI personalisation needs structured inputs
Generative recommendation, dynamic email content, and on-site AI assistants are only as good as the signals feeding them. A model that knows a shopper's stated skin type, primary concern, and budget produces dramatically better recommendations than one inferring those from clickstreams. Zero-party data is the cleanest training signal a model can get: explicit, structured, and labelled at the source.
03
Privacy regulation has hardened
GDPR, CCPA, CPRA, Quebec's Law 25, the EU AI Act, and a growing list of state-level US laws share a common pattern: consent must be specific, withdrawable, and demonstrable. Zero-party data is collected with active consent by definition. The customer chose to share it; you can show when, what for, and with what value exchange. Inferred third-party data fails almost every one of those tests.
04
Acquisition costs keep rising
With Meta and Google CPMs trending up and attribution windows shrinking, paid acquisition only works if you lift customer LTV. Personalisation is the lever. Personalisation that doesn't feel intrusive requires data the customer knowingly gave you. The math is structural: lift email RPR, repeat-purchase rate, or AOV by even 10% through better targeting, and you can outbid competitors for the same impression while keeping margin intact.
The combined effect: brands that have a working zero-party data pipeline by mid-2026 will compound an advantage that brands relying on inferred third-party signals can no longer access. The store next door cannot copy your customers' declared preferences. They have to earn them, one quiz answer at a time, just like you did.
Why this guide exists
Zero-party data has been a buzzword since 2018. Most pages defining it stop at the definition and a brief why-it-matters. This guide goes further: it covers the four data types in a single comparison, gives you six collection methods ordered by leverage, names the four activation channels where the lift actually shows up in revenue, lists the tools we see in real stacks, and catalogues the four mistakes that cause programs to underperform. By the end, you should be able to draft a zero-party plan for your store and execute the first ninety days against it.
How to collect zero-party data
Six methods consistently work. Ordered by leverage per minute of customer attention: the higher up the list, the more structured preference data you collect for each second of engagement.
Product recommendation quizzes
Highest yield per minute of customer attention.
Three to seven diagnostic questions, a personalised result page, and the customer walks away with a recommendation while you walk away with a structured profile. Completion rates regularly exceed 40% on well-designed quizzes; every completion produces multiple preference attributes (skin type, concern, age range, budget, shopping-for, lifestyle) that map directly to email and ad platforms.
Preference centres
Retention layer on top of a quiz.
A dedicated page or modal where existing subscribers can update what they want to hear about and how often. The data (channel preference, content topics, frequency, product categories) flows directly into your ESP. Lower conversion than quizzes for first-time visitors because the value exchange is weaker.
Loyalty and account programs
Zero-party machines when designed well.
Every points-earning interaction (review a product, share your birthday, complete your profile, take a survey) is a structured data point in exchange for redeemable value. The data is excellent but the cost-per-attribute is higher than a one-time quiz.
Post-purchase surveys
Most under-used zero-party tool in DTC.
A two-question post-purchase survey ("How did you hear about us? What problem are you trying to solve?") attaches answers directly to the order record. The customer has just received value (the order) and is in a brief window of high goodwill. Completion rates of 30-50% are common.
Smart forms and progressive profiling
Long-tail enrichment after acquisition.
Collect one or two pieces of preference data each time a customer interacts, not in one giant form. A shopper who books a virtual consultation, downloads a buying guide, or registers for a webinar contributes one new attribute per touchpoint.
Interactive content
Data as a side effect of helping decide.
Calculators, configurators, "build your routine" tools, and visual finders all collect zero-party data as a side effect of helping a shopper decide. The shopper inputs their bra size, room dimensions, or fitness goal to get a personalised output; you keep the input.
Where to activate zero-party data
Collection without activation is just file storage. The four highest-leverage activation channels:
Email and SMS
Fastest payback.
Synced as custom properties in Klaviyo, Omnisend, or Mailchimp. Zero-party attributes power segmented welcome series, replenishment reminders, win-back flows, and dynamic content blocks inside otherwise generic campaigns.
Paid ads
Enriched custom audiences and look-alikes.
A list of 8,000 customers tagged as "sensitive skin, anti-aging concern, 35-44" is dramatically more valuable as both a remarketing audience and a look-alike seed than a list of 80,000 untagged subscribers. The campaign-level gains compound through the ad platform's optimisation model.
On-site personalisation
Drive collection ordering, hero swaps, PDP logic.
Store a quiz attribute in a cookie or local-storage key and let your theme or a personalisation app read it on subsequent visits. Drives collection ordering, hero swaps, product recommendation feeds, and hide/show logic on PDPs.
Customer service and post-purchase
Surface answers inside tickets and emails.
Surface quiz answers inside Shopify Orders, Gorgias tickets, and post-purchase emails so the human or automated message references what the customer already told you.
The pattern across all four channels: a structured custom property created by a quiz answer feeds a segment, a personalised flow, or a dynamic content block. The mechanism is mundane. The leverage is enormous.
Common mistakes to avoid
Four patterns we see repeatedly when zero-party programs underperform. Each one is recoverable, but easier to prevent than retrofit.
Mistake 01
Treating it as a one-off campaign
Zero-party data is a stack-level capability, not a one-quarter project. The lift comes from feeding answers into every downstream system (ESP, ad platform, helpdesk, on-site) and refreshing the data on a cadence. A quiz launched once and never wired into Klaviyo loses most of its value.
Mistake 02
Asking for too much in one form
A 20-question quiz with no clear payoff feels like a tax. Three to seven questions with a relevant recommendation at the end converts at 5-10x the rate. If you need more attributes, layer them across progressive profiling and post-purchase surveys instead.
Mistake 03
Collecting answers without consent linkage
Capturing a preference is not the same as having permission to use it across channels. Make the consent ask explicit (email opt-in, marketing-purpose declaration) inside the same flow, and store the consent timestamp alongside the attribute so a regulator audit is trivial.
Mistake 04
Ignoring the activation half
Stores routinely launch the collection mechanism and then leave the data sitting in a custom property nobody segments on. Wire each attribute to at least one segment, one flow, and one ad-platform audience the same week you ship the quiz.
Tools for collecting zero-party data
The market splits into three categories. Pick based on which collection method you're prioritising first.
| Category | Best for | Notable options |
|---|---|---|
| Product recommendation quizzes | Structured preference capture, on-site conversion, ESP enrichment | RevenueHunt: Recommender Quiz for Shopify (native Shopify + Klaviyo), Octane AI, Typeform (generic) |
| Forms, popups, surveys | Email capture, simple preference centres, post-purchase surveys | Klaviyo forms, Privy, KnoCommerce (post-purchase) |
| Customer data platforms (CDP) | Unifying zero-party data with first-party behavioural and transactional data at scale | Klaviyo Data Platform, Segment, Rudderstack, BlueConic |
Disclosure: RevenueHunt is our own product. We've listed it because it's the category we know best: a Shopify-native quiz builder with one-click Klaviyo, Omnisend, Mailchimp, Meta, Google Ads, and Shopify Orders integrations. The list above is not exhaustive; we've named the tools we see in client stacks most often.
Frequently asked questions
What is zero-party data?
Zero-party data is information a customer intentionally and proactively shares with a brand: preferences, intents, goals, and how they want to be recognised. It is given freely in exchange for value (a recommendation, a discount, a personalised experience) and is the most accurate and privacy-compliant signal a retailer can act on.
What is the difference between zero-party and first-party data?
Both are collected and owned by the brand. The difference is intent: first-party data is observed (pages visited, products purchased, emails opened); zero-party data is declared (the customer explicitly tells you their skin type, budget, or primary concern). First-party data is excellent for retargeting and propensity models. Zero-party data is excellent for personalisation, segmentation, and consent.
How do you collect zero-party data?
Six methods consistently work: product recommendation quizzes, preference centres, loyalty and account programs, post-purchase surveys, smart forms with progressive profiling, and interactive content (calculators, configurators, finders). Product recommendation quizzes typically produce the highest yield per minute of customer attention because they wrap the data ask inside a clear value exchange.
What are examples of zero-party data?
Skin type, primary skincare concern, age range, budget, shopping-for-self-or-gift, dietary restrictions, fitness goal, preferred communication channel and frequency, sizes, room dimensions, lifestyle category, scent preferences. Anything a customer states explicitly through a quiz, survey, preference centre, or account profile.
Is zero-party data the same as first-party data?
Some industry frameworks treat zero-party as a subset of first-party (you own both, collected on your infrastructure). Most marketers separate them because zero-party is declared and first-party is observed. They behave differently in activation: zero-party powers explicit personalisation; first-party powers behavioural retargeting and propensity modelling.
Why does zero-party data matter in 2026?
Four shifts have made it strategic rather than optional: third-party cookie deprecation, AI personalisation needing structured inputs, hardened privacy regulation (GDPR, CCPA, CPRA, Law 25, EU AI Act), and rising acquisition costs that make personalised retention the only durable margin lever.
Is collecting zero-party data GDPR-compliant?
Zero-party data is the most GDPR-friendly category by definition: it is collected with the customer's active, specific consent in exchange for a stated value. To stay compliant you still need a clear privacy notice, a defined retention period, a documented purpose for processing, and an easy way for the customer to withdraw consent or request deletion.
How do I activate zero-party data in Klaviyo?
Map each quiz or survey answer to a Klaviyo custom property via a native integration (no Zapier). Use those properties to build conditional splits in welcome and replenishment flows, drive dynamic content blocks in campaigns, and construct segments that were previously impossible (sensitive skin, gift buyers, specific budget tiers). The full mapping chain is covered in our Klaviyo zero-party data guide.
How long does it take to launch a zero-party data quiz?
Using an industry-specific template and a no-code quiz builder, most Shopify stores launch a working quiz with a native Klaviyo connection in under an hour. Data starts flowing into customer profiles the same day.
How is zero-party data different from third-party data?
Third-party data is purchased or aggregated by an intermediary you don't own and is typically inferred (e.g. 'likely interested in skincare'). Zero-party data is given to you directly by the customer and is explicit. Third-party data is degrading rapidly as cookies are deprecated and privacy regulation tightens; zero-party data is the structural replacement.
Start collecting zero-party data this week.
Install RevenueHunt in under five minutes, pick a template, and have the first quiz answers flowing into Klaviyo, Shopify Orders, and your ad platforms the same day. Free plan covers the first thousand completions.
For the broader picture, see first-party data and the ecommerce quiz guide.