Engage
Analytics

Cost per return visit: what venue email costs to bring a guest back

You will be able to work out what each email-driven guest visit costs by dividing the full campaign cost by visits above a random holdout baseline. You can then set a break-even ceiling from gross profit per visit and compare venue email with paid social and discount sites.

11 min read2,714 words

Part of the guide topicEmail marketing ROI for venues: measuring the visits it brings

Video overview

Cost per return visit is what an email campaign costs, in platform, offer and staff time, divided by the extra visits it caused. Extra visits are measured against a randomly held-back group. If a £2,000 campaign brings 400 more visits than the holdout predicts, each return visit cost £5. You can compare that with paid social and discount sites.

What is cost per return visit?

Cost per return visit is a unit cost for venue email. The top of the fraction is everything the campaign cost you. The bottom is the number of visits that would not have happened without it. You find those visits by comparing emailed guests with a random holdout that received nothing.

It answers the question a finance director asks: what did we pay for each guest we brought back? It sits beneath the wider question of email marketing ROI for venues and has three properties that make it useful:

  • Causal. The holdout removes guests who would have returned anyway.
  • Fully loaded. Offer cost and staff time sit beside the platform bill.
  • Comparable. Paid social and discount sites can be measured the same way.
{"tone":"note","title":"Scope of this guide","text":"Cost per return visit covers one campaign over one measurement window. Lifetime value and loyalty returns build on it and are covered in the [loyalty programme ROI calculator](guide:loyalty-programme-roi-calculator-restaurant)."}

How do you calculate cost per return visit?

The calculation has two halves that you build separately and then divide. The cost side is accounting. The visit side is a small experiment. Write both formulas down before you send:

  • Cost per return visit = total campaign cost ÷ incremental visits
  • Incremental visits = visits by the emailed group − (holdout visit rate × size of the emailed group)
{"kind":"flow","direction":"lr","caption":"How one campaign becomes a single cost per return visit","alt":"Flow showing a consented guest list split at random into emailed and holdout groups, with visit counts and campaign costs combining into cost per return visit.","nodes":[{"id":"list","label":"Consented guest list","sub":"Guests who opted in to marketing at WiFi sign-in","tone":"brand"},{"id":"split","label":"Random split","sub":"For example 90% emailed, 10% held back","tone":"neutral"},{"id":"send","label":"Emailed group","sub":"Receives the email and the offer","tone":"brand"},{"id":"hold","label":"Holdout group","sub":"Receives nothing from this campaign","tone":"neutral"},{"id":"visits","label":"Visits in a fixed window","sub":"Counted the same way for both groups","tone":"neutral"},{"id":"lift","label":"Incremental visits","sub":"Emailed visits minus the holdout baseline","tone":"success"},{"id":"cost","label":"Total campaign cost","sub":"Platform share + offer cost + staff time","tone":"danger"},{"id":"cprv","label":"Cost per return visit","sub":"Total cost divided by incremental visits","tone":"brand"}],"edges":[{"from":"list","to":"split","label":"eligible guests"},{"from":"split","to":"send","label":"randomly assigned"},{"from":"split","to":"hold","label":"randomly assigned"},{"from":"send","to":"visits","label":"observed visits"},{"from":"hold","to":"visits","label":"baseline visit rate"},{"from":"visits","to":"lift","label":"difference between groups"},{"from":"lift","to":"cprv","label":"divide by"},{"from":"cost","to":"cprv","label":"divided"}]}

What goes into the cost side?

Count every pound the campaign used up, not just the email platform invoice. Four lines cover a typical venue campaign:

  • Platform share. Divide your monthly subscription across the campaigns and automations it supported that month. If you pay per contact, add contacts bought for this send.
  • Offer cost. Count every redemption, including those by guests who would have come anyway. That leak is real money.
  • Staff time. Count hours for planning, copy, design, approvals and briefing the floor team, at a loaded hourly rate.
  • Production extras. Add photography, agency fees or printed material made only for this campaign.

Leave out the food and drink the returning guest pays for. That belongs on the revenue side, where you compare it with gross profit later.

Pick one rule for offers and keep it. Use face value for money off the bill and cost of goods for a free item. Changing rules between campaigns makes the trend meaningless.

How do you count only the visits the email caused?

Count visits, not opens, clicks or redemptions. An open is not a visit. A redemption is a visit, but not necessarily one the email caused.

You need a visit signal that works identically for both groups. A guest WiFi login is one; a loyalty scan is another. Fix the measurement window before you send, and match it to your natural visit cycle. That might be two weeks for a café, four for casual dining and a season for a hotel.

Count every visit each group makes inside the window. Divide by group size to get a visit rate per guest.

Why does a held-back group matter?

Regulars come back whether or not you email them. Without a holdout, their visits look like the email's work and the metric flatters the campaign.

The holdout lives through everything the emailed group does: the same weather, bank holiday and new menu. The only difference is the email. So the gap between the two visit rates is the email's effect.

Three rules keep the holdout honest:

  1. Randomise. Never hold back your least engaged guests, because that inflates the lift.
  2. Freeze it. Fix the split before sending and leave it untouched afterwards.
  3. Size it. Random counts wobble by roughly the square root of the count. A holdout with 100 visits is uncertain by about 10%; one with 25 visits, by about 20%.

A worked example

These figures are illustrative, not a benchmark. A casual dining group emails 20,000 guests lapsed for 60 days, offering a free dessert. It randomly holds back 10%, or 2,000 guests.

Over 28 days the 18,000 emailed guests make 1,620 visits. The holdout makes 140, a 7% visit rate. Applied to 18,000 guests, that rate predicts 1,260 visits without any email. The email caused the other 360.

Line How it is worked out Amount
Platform share Monthly subscription split across the month's campaigns £300
Offer cost 1,100 desserts redeemed × £1.50 cost of goods £1,650
Staff time 8 hours × £35 loaded hourly rate £280
Total campaign cost Sum of the three lines £2,230
Incremental visits 1,620 observed − 1,260 baseline 360
Cost per return visit £2,230 ÷ 360 £6.19
Cost per redemption, for contrast £2,230 ÷ 1,100 £2.03
{"kind":"layers","direction":"tb","caption":"What sits inside the visits the emailed group made (worked example)","alt":"Layered diagram splitting 1,620 observed visits into 1,260 baseline visits, a subsidised share of those, and 360 incremental visits.","nodes":[{"id":"obs","label":"Observed visits: 1,620","sub":"Every visit by the 18,000 emailed guests in 28 days","tone":"neutral"},{"id":"base","label":"Baseline visits: 1,260","sub":"Holdout rate of 7% applied to 18,000 emailed guests","tone":"neutral"},{"id":"subs","label":"Subsidised baseline","sub":"Guests who would have come anyway but still took the dessert","tone":"danger"},{"id":"inc","label":"Incremental visits: 360","sub":"The only visits the email caused","tone":"success"}],"edges":[{"from":"obs","to":"base","label":"would have happened anyway"},{"from":"base","to":"subs","label":"part of it still redeems"},{"from":"obs","to":"inc","label":"caused by the email"}]}
{"tone":"warning","title":"The redemption trap","text":"Dividing by redemptions counts your regulars as wins. In the example, £2.03 per redemption understates the real £6.19 cost per return visit by about two-thirds."}

Cost per return visit vs cost per redemption, return rate and ROAS

Several venue metrics share words with cost per return visit but divide different things. The difference decides which one survives a budget meeting.

{"caption":"Venue email metrics that get confused with cost per return visit","asOf":"2026-06-10","columns":[{"key":"term","label":"Metric"},{"key":"divides","label":"What it divides"},{"key":"tells","label":"What it tells you"},{"key":"misleads","label":"Where it misleads"}],"rows":[["Cost per return visit","Full campaign cost ÷ visits above the holdout baseline","What each caused visit cost","Ignores spend per visit; pair it with gross profit"],["Cost per redemption","Campaign cost ÷ offers redeemed","How cheaply the offer was used","Counts guests who were coming anyway"],["Cost per send","Platform cost ÷ emails delivered","Efficiency of the platform","Says nothing about visits"],["Cost per acquisition","Spend ÷ new guests won","Price of a first visit","Mixes new and returning guests if not split"],["Return rate","Guests who came back ÷ guests in the group","How loyal a segment is","Without a holdout, cannot separate email from habit"],["Revenue per send","Attributed revenue ÷ emails sent","Yield per email","Credits habitual visits that followed the email"],["ROAS","Attributed revenue ÷ media spend","Return on paid media","Revenue, not profit; leaves out offer and staff cost"]],"footnote":"ROAS: return on ad spend. Attributed metrics credit any visit after the email; incremental metrics credit only visits above the holdout."}

The thread running through the table is attribution versus incrementality. Attributed metrics credit the email for any visit that followed it. Incremental metrics credit only visits above the holdout baseline. Only the second tells you what the email caused. Setting up consistent visit counts is covered in how to measure repeat visits to a restaurant.

Where does cost per return visit matter in practice?

You meet the metric wherever someone chooses between spending on email and spending somewhere else:

  • Win-back campaigns. Lapsed guests have a low baseline, so the holdout shows clearly whether the offer moved them.
  • Multi-site budget calls. Run one campaign across sites and compare cost per return visit site by site.
  • Platform renewals. It gives a finance director a pound figure, not an open rate.
  • Agency reporting. Ask agencies for incremental visits, not attributed revenue.

What is a good cost per return visit for a venue?

A good cost per return visit sits below the gross profit of the visit it buys. That is your break-even line, and it is specific to your venue.

Take average spend per visit and multiply by gross margin. A venue with £28 average spend and a 65% margin makes £18.20 per visit. The £6.19 example clears that line about three times over, before any later visits.

Treat break-even as a ceiling, not a target. A campaign at £4 that brings 20 visits may matter less than one at £7 that brings 500. Be wary of benchmarks that do not say whether a holdout was used.

How does it compare with paid social and discount sites?

The same formula works for every channel. What changes is which cost lines are large and how hard incremental visits are to prove.

{"caption":"Cost per return visit across three venue channels","asOf":"2026-06-10","columns":[{"key":"line","label":"Cost line"},{"key":"email","label":"Venue email","highlight":true},{"key":"social","label":"Paid social"},{"key":"deals","label":"Discount sites"}],"rows":[["Audience cost","Low once the list exists; built from WiFi logins","Paid every time through media spend","Paid through the site's share of each voucher"],["Offer cost","Set by you; can be a low-cost item","Optional, but often needed to drive a visit","The discount itself"],["Who you reach","Guests who visited and opted in","Mix of past guests and strangers","Deal browsers, many new to you"],["Proving incremental visits","Random holdout plus login-based visit counts","Lift studies; linking to in-venue visits is harder","Hard; return visits need separate measurement"]],"footnote":"Use the same window and the same definition of a visit before comparing channels."}

Two structural differences stand out. Paid social rents the audience each time, so cost rises with reach. Discount sites mostly buy a first visit, and whether that guest returns needs separate measurement. Venue email reaches people who already visited, through a list you own.

Where does cost per return visit break down?

The metric is simple, but the measurement has edges you should know before reporting it:

  • Guests who do not log in. Login-based counts miss some visits. Both groups are counted the same way, so the figure is conservative, not wrong.
  • Holdout contamination. A held-back guest may arrive with a friend who got the offer. That shrinks the measured lift.
  • Small lists. Single sites produce noisy baselines. Pool similar campaigns or lengthen the window.
  • Long visit cycles. Hotels may need 90 days or more. Label any earlier figure as interim.
  • Cross-site visits. An email from one site may send a guest to another. Count visits across the whole group.
  • Spend is invisible. A coffee and a three-course dinner both count as one visit. Add incremental gross profit where spend varies widely.
  • Hidden long-term costs. Frequent offers can teach guests to wait, and heavy sending raises unsubscribes. A long-running holdout across several months reveals both.

How does Purple Engage measure cost per return visit?

Cost per return visit needs two things: a list of guests who have visited, and a visit signal for each of them. Purple Engage gets both from one place, the guest WiFi login.

The list builds itself

When a guest signs in to your WiFi, the branded login page offers marketing as a conscious-choice opt-in. It sits apart from accepting the WiFi terms, reflecting the consent conditions in GDPR Article 7. For UK venues, PECR regulation 22 governs the emails that follow.

Opt-in rates run around 50% higher on branded login pages, according to Purple data. Mailchimp-style platforms send campaigns, but they do not build the list. You still need a way to collect consented, first-party addresses in the venue.

The same login measures the visit

Each later login is a visit, recorded against the same consented guest. Emailed and held-back guests are measured from the same login data, with no till receipts to match. Purple Engage measurement uses those visits for segments, such as guests lapsed for 60 days, and for comparison.

{"items":[{"value":"80,000+","label":"live venues","note":"Purple data"},{"value":"90","label":"countries","note":"Purple data"},{"value":"500 million","label":"logins a year","note":"Purple data"},{"value":"~50%","label":"higher opt-in on branded login pages","note":"Purple data"}]}

Venues running Purple include Harrods, Pizza Express and McDonald's.

Where the metric bites

In a real deployment, cost per return visit bites at budget time. Expect your first holdout campaign to change the conversation. The incremental figure will be higher than the redemption figure, because the holdout removes the regulars. Next, read the WiFi marketing guide to see how the consented list grows before you measure it.

Frequently asked questions

What is a good cost per return visit for a restaurant?

A good cost per return visit is anything below the gross profit of one visit. Multiply average spend by gross margin to find your line; £28 at 65% gives £18.20. Below that, the campaign pays back on the first visit alone. Then compare campaigns with each other using the same holdout method, rather than with published benchmarks.

Is holding back guests from an email compliant with GDPR?

Yes. Not sending a marketing email needs no lawful basis; sending one does. The emailed group must have consented under GDPR, or qualify for the soft opt-in under PECR regulation 22 in the UK. Explain visit measurement in your privacy notice. Your data protection lead should confirm the wording before your first measured campaign.

Does Purple Engage work with the WiFi hardware we already have?

Yes. Purple is hardware-agnostic and runs as a cloud overlay, so you keep your access points. It works with Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. The login page, consent capture and visit data all sit in Purple, so the holdout comparison needs no new hardware.

How should I include the email platform subscription in the cost?

Allocate it, never ignore it. Divide the monthly fee across every campaign and automation it supported that month. Add any contacts you paid for specifically for the campaign. Contact-based pricing changes this sum as a list grows, as the Mailchimp pricing guide explains. Use the same rule every month.

How does this compare with what Mailchimp, Klaviyo or HubSpot report?

They report different things. Their headline reporting covers opens, clicks and attributed revenue, which credit the email for visits that would have happened anyway. None of them sees an in-venue visit unless you feed one in. Purple Engage records visits from the guest WiFi login, so cost per return visit uses the data that built the list.

Can we switch email platforms without losing our measurement history?

Yes, if you treat the switch as a new baseline. Keep old reports for reference, but never compare attributed figures with incremental visit figures. Run your first three Purple Engage campaigns with a holdout and the same cost rules. Those results become your benchmark while the consented list grows from WiFi logins.

How much effort does the first measured campaign take?

Little more than a normal campaign. The extra work comes before the send: agree the cost rules, choose the window, split the segment at random and record the split. After the window closes, the calculation is two subtractions and a division. Most of the effort is discipline, so write the plan down first.