First party data: the list nobody can take away

A restaurant takes most of its bookings through a popular booking platform. For years, it works well: the platform brings guests, the restaurant serves them. Then the platform raises its fees, changes how restaurants appear in its search and starts showing guests other venues nearby when they look at this one. The restaurant wants to email its regulars to tell them to book directly. It realises it does not have their email addresses. The platform does.

First party data is the information a venue collects directly from its own guests, with their knowledge: their names, contact details, visits, preferences and whether they want to hear from you. It is the list nobody can take away, because the venue gathered it itself, rather than renting access to it through someone else's platform.

This guide covers what first party data is, why it matters more as platforms change their terms, what to collect, how to build the list honestly with marketing consent and what it is worth when the day comes that you need it. Every venue and figure in it is an example.

First party data is information you collect directly from your guests, in your own systems: bookings made on your own booking page, orders taken on your own till, emails given at your own door, feedback sent to your own form. You know where it came from, the guest knows you have it, and it belongs to your relationship with them.

It differs from data held by others. A booking platform, a delivery app or a social network may know a great deal about your guests, but that knowledge is theirs, used on their terms, and you see only what they choose to share.

First party data matters more as more of a venue's guests arrive through platforms. Each platform sits between the venue and its guests, and each can change its terms: higher fees, different search rankings, rules on contacting guests, or a decision to promote competitors.

A venue with its own list of guests can speak to them directly whatever the platforms do. A venue without one depends entirely on platforms to bring its guests back, at whatever price the platforms set.

Booking platforms and marketplaces often keep the guest relationship for themselves. They may share a guest's name and booking details for the visit, but not their email address, or only with conditions. Some let guests choose whether to share their details with the venue.

Read the terms of every platform you use: what guest data you receive, what you may do with it and what happens to it if you leave. Our guide to booking platforms: what you rent and what you own covers the difference.

The cost of having no first party data shows at the worst moments. A platform raises its fees, and the venue cannot tell its regulars to book directly. A quiet week arrives, and the venue has no way to invite guests back. The venue moves or changes its name, and its guests cannot be told.

Each of those moments is common in the life of a restaurant. A venue with its own list handles them with an email; one without depends on luck, word of mouth and the platforms' goodwill.

The cost also shows over time. Every guest who books through a platform, without the venue learning who they are, is a guest the venue must pay to reach again.

The guest data worth collecting is the data that helps you serve and reach guests: their name, an email address or phone number, their visits, their allergies and preferences, and whether they have agreed to hear from you. That is enough for a venue to recognise a guest, look after them well and invite them back.

Collect what you will use, and nothing more. Our guide to guest data: what to collect and what to leave covers where the line is.

First party data comes from every point where a guest deals with you directly. Your own booking page and phone bookings. Walk-ins who give their name. Orders and payments on your till. Feedback forms. Sign-ups at the table, on your website or in your emails. Events and private bookings.

Each one is a chance to learn a little more about a guest, with their knowledge. Over time, those small pieces build a full picture.

Walk-ins and phone bookings are an easy source of first party data that many venues waste. A walk-in seated without a name leaves no record; one who gives a name and a phone number becomes a guest the venue can recognise next time.

Ask walk-ins for a name, and for a number if they are happy to give one, especially if they might wait for a table. Take phone bookings in the venue's own system rather than on paper, so every phone booking adds to the guest list.

Over a year, the walk-ins and phone bookings that are recorded add up to hundreds of guests a venue would otherwise never know.

The single biggest source of first party data is bookings taken directly: on your own booking page, linked from your website and your search listing, or by phone. Every direct booking gives you the guest's details in your own system.

Make direct booking easy: a clear booking link on your website, your search listing and your social profiles, and a booking page that takes a minute to complete. Each direct booking is a guest on your own list rather than someone else's.

Holding a guest's email address is not the same as being allowed to send them marketing. In most countries, you need the guest's consent to send them offers and news, and that consent must be freely given, specific and recorded.

Ask clearly, at the point of collection: a box the guest ticks to say they would like to hear from you, never one that is ticked for them. Record when and how they agreed. Our guide to marketing consent, collected so it holds up covers how to do it properly.

Many of a venue's best guests never book online: regulars who walk in, guests who come for lunch, people who visit once with friends. The room itself is a source of first party data, if you ask.

A card at the table, a code guests can scan, a server who asks whether a guest would like to hear about events: each can add a guest to your list, with their consent. Our guide to building an email list from the room you have covers how.

The best first party lists are built on consent that guests are glad to give. Guests share their details when they see a reason: news of events, a birthday treat, the new menu, a quiet word when a favourite dish returns. Make the offer clear, and make it worth it.

Never collect consent by trickery: pre-ticked boxes, consent hidden in terms and conditions or consent bundled with something the guest needed. A list built that way is full of guests who did not really agree, who will unsubscribe or complain, and who may not count as consenting at all.

A smaller list of guests who genuinely want to hear from you is worth far more than a large list of guests who never asked.

The value of first party data shows when you need it. A venue with a list of a few thousand guests who have agreed to hear from it can fill a quiet week, launch a new menu, announce an event or tell guests about a move, with one email.

It also changes the economics of platforms. A guest who books directly through your own email costs you nothing in platform fees; one who books through a marketplace may cost a fee every time.

First party data is only valuable if it is accurate. Duplicate profiles for the same guest, out-of-date email addresses and old preferences all reduce its value. Clean it regularly: merge duplicates, remove addresses that bounce and update preferences when guests tell you something has changed.

An accurate list of a thousand guests is worth more than an inaccurate list of five thousand.

Feedback forms and events are two more sources of first party data. A guest who leaves feedback, and agrees to be contacted, has told you how they feel about the venue and how to reach them. A guest who books an event, a tasting evening or a private party, has shown an interest worth remembering.

Record both against the guest's profile, with consent where it is needed. A guest who loved the wine tasting can be told about the next one; a guest whose feedback was critical can be welcomed back with care.

Every interaction that adds to the profile makes the next one more personal.

Holding guest data brings responsibilities. Keep it secure: limit who can see it, protect accounts with strong sign-ins and remove access when staff leave. Follow the data protection rules where you trade, such as the General Data Protection Regulation in the UK and the EU.

Guests trust you with their details. Losing that trust through a careless leak costs far more than any campaign could earn.

Owning your guest data means more than collecting it. It means being able to use it, keep it and take it with you if you change systems. Check what your booking system, till and email tool let you do with the data: can you see it all, use it for campaigns and get it out if you leave?

Our guide to owning your guest data when you switch systems covers the questions to ask.

First party data is powerful, but it has limits. It cannot bring in guests who have never heard of you; that is what platforms, search and word of mouth are for. It cannot replace good food and service. And it loses value quickly if it is not kept accurate.

Treat it as one part of how the venue finds and keeps guests, not as the whole. A venue that relies only on its own list may stop attracting new guests; one that relies only on platforms may lose the ones it has.

The strongest venues use both: platforms and search to be found, their own list to be remembered.

First party data is best used to look after guests and bring them back, not to bombard them. A short, relevant email to guests who have agreed to hear from you, a little more often than never and a lot less often than weekly, keeps the relationship warm.

Segment the list: regulars, lapsed guests, guests who come for celebrations. A message that fits each group is welcome; the same message to everyone is often ignored.

None of this means platforms are bad. Booking platforms and marketplaces bring guests a venue would never reach alone, especially new guests and visitors. Many venues use them well.

The point is balance. Use platforms to find new guests, and use your own systems to keep them. A guest who first found you on a platform and now books directly is the best outcome of all.

The best time to start building first party data was years ago; the second best time is now. Every direct booking, every walk-in who gives a name, every guest who agrees to hear from you adds to a list that will matter more each year.

Start with the simplest steps: a clear booking link on your website and search listing, names for walk-ins, an opt-in at booking and a way for guests in the room to sign up. Then keep the list accurate and use it kindly.

In a year, the list will be one of the venue's most valuable assets, and one nobody can take away.

Your own website is one of the best places to build first party data, because guests who visit it already know your name. Make the booking link the most obvious thing on every page, and make sure it leads to your own booking page rather than a platform's.

Add a simple way for visitors to sign up for news, with a clear reason to do so: events, seasonal menus, a birthday treat. Keep the form short, with just a name and an email address, and ask for consent clearly.

A website that sends visitors to a platform to book gives that platform the guest. One that keeps them on your own booking page keeps the guest for you.

In a group of venues, first party data can be shared across the group, so a guest who visits one venue can be recognised at another. That is valuable, but it needs care: guests should know which business holds their data, and consent should cover what the group will do with it.

Decide as a group how guest records are kept, who can see them and how marketing is sent, so guests receive one sensible message rather than several from each venue. A guest who hears from four venues in a week may unsubscribe from all of them.

Handled well, a group's shared list becomes one of its strongest assets: a picture of its guests across every venue.

Measure the list each month: how many guests are on it, how many agreed to hear from you, how many new ones joined and where they came from. Look at how many bookings came directly rather than through platforms, and whether that share is growing.

Look at the quality too: how many emails bounce, how many guests open what you send and how many unsubscribe. A list that grows but whose guests stop reading is not getting more valuable.

These few numbers, tracked over a year, show whether the venue is building a list nobody can take away, or simply collecting addresses.

Guests share their details more willingly when they understand why. A short line at the point of asking helps: "We'll only use your email to confirm your booking and, if you'd like, to tell you about our events." Honesty about the purpose builds trust, and trust builds the list.

Never collect more than you say you will use, and never use details for something the guest was not told about. A guest who feels misled will not share again.

An invented bistro takes most of its bookings through a marketplace. When the marketplace raises its fees, the bistro realises it cannot contact most of its regulars directly.

The bistro adds a clear booking link to its website and search listing, asks guests at the table whether they would like to hear about events, with a simple opt-in, and makes sure every direct booking adds the guest to its own records. It sends a short monthly email to guests who have agreed to hear from it.

Over a year, the share of bookings made directly rises steadily. The bistro still uses the marketplace for new guests, but its regulars now book directly, and the next fee rise worries it far less.

In servearound, guest records build themselves from the venue's own bookings, orders and checks: every booking taken on the venue's own booking page, by phone or by the team, and every walk-in given a name, adds to the guest's profile, with their visits, spend, allergies, preferences and feedback. Guests who book online give their name, phone and email, confirm their email with a six-digit code and can choose to receive marketing emails and newsletters.

Guests can be brought in from a spreadsheet, using servearound's template, and imported guests are not signed up to marketing emails. Guests cannot be exported from servearound today, which is worth knowing before you plan around it. See Guest CRM and pricing.

Information a venue collects directly from its own guests, in its own systems, with their knowledge.

It lets a venue reach its guests directly, whatever the platforms it uses decide to do.

Names, contact details, visits, allergies, preferences and marketing consent, and nothing you will not use.

Only for marketing if they have agreed. Ask clearly and record the consent.

Direct bookings, walk-ins who give their name, the till, feedback forms and sign-ups in the room.

No. They bring new guests. Use them to find guests and your own systems to keep them.

Keep it accurate, merge duplicates, remove dead addresses and keep it secure.

Being able to see, use and keep your guest data, including taking it with you if you change systems.

First party data is the guest list nobody can take away: information you collect directly from your own guests, in your own systems, with their knowledge. It matters more as platforms change their terms, because it lets you reach your guests directly whatever the platforms do.

Collect what you will use, mostly through direct bookings and the room itself, ask for marketing consent clearly and record it, keep the data accurate and secure, check that you can use it and take it with you, use platforms to find new guests and your own list to keep them.