Zero-Party Data

Zero-party data is the information a customer hands you on purpose. Their shoe size. The fact that they cook without dairy. A note saying to leave the parcel with the neighbour on the left. Nobody guessed it and nobody followed them around to work it out. They typed it in because they wanted a better result.

It is different from watching what people do. Tracking guesses. It sees that someone looked at three pairs of boots and decides they like boots. Maybe they were buying a gift. A short question answered in the customer's own words beats a month of guessing, and it does not need a single tracking cookie.

You collect zero-party data by asking at the right moment and giving something back. A size question during checkout, so the next order fits. A box for delivery notes, so the driver stops ringing the wrong bell. A tick asking whether the customer wants messages about sale days only. Each answer has to change something the customer can see, or they stop answering. That is the whole trade.

Given freely does not mean stored carelessly. Ask for one thing at a time and say what it is for in the same sentence. Keep the record of who agreed and when. Let people see what you hold and delete it in one click. And guard it, because a list of home addresses and family sizes is worth more to a thief than a card number that expires. Linkysoft treats that list as the part of a shop that needs the most protection work, not the least.

Here is the part shops get wrong. They gather the answers and then never use them, so the customer who said they are allergic to nuts still gets the nut offer. Trust breaks the moment that happens, and it does not come back. Answers are only useful if they reach the systems that write the emails and pick the products, which is where a small recommendation system earns its keep. Storek keeps these answers on the customer record, and Linkysoft starts every project by asking which questions the shop will actually act on. Ask fewer. Use all of them.