Weekday vs weekend guests: segmenting restaurant email by when people visit
You will be able to split your restaurant email list into weekday regulars, weekend-only guests and mixed guests using consented guest WiFi visit data.
Part of the guide topicCustomer segmentation for venues: a practical guide
Video overview
Weekday vs weekend segmentation is splitting your email list by the days guests actually visit. Weekday regulars and weekend-only diners then receive different messages. Built from guest WiFi logins, each segment rests on CCPA/CPRA consent and real visit dates. You thank regulars and give weekend guests a reason to fill a quiet Tuesday.
What is weekday vs weekend segmentation?
Day-of-week segmentation groups guests by when they come in, not by age, zip code or stated preference. It is a behavioral segment, so it describes what a guest does, using recorded visits. The basic split has two sides. Weekday regulars visit mostly Monday through Thursday. Weekend-only guests appear only Friday through Sunday. Repeat guests who fit neither rule sit in a third group, mixed guests.
The calendar is not the point. The gap between your busiest and quietest nights is, along with the guests who could help close it.
Are weekday and weekend guests really different?
Often, yes. Weekday vs weekend restaurant customers can want quite different things from the same venue. A weekday lunch guest may work nearby, eat with coworkers and care about speed. A Saturday table is more often a planned occasion with friends, family or a partner. The menu is the same, but the reasons to visit are different.
That difference changes what an email should do. For a weekday regular, your venue is already a habit, so the job is to recognize and keep it. For a weekend-only guest, your venue is an occasion. The job is to suggest a second occasion on a night when you have empty tables.
Send both groups one message and it fits neither. A weekday offer sent to everyone pays regulars for visits they would have made anyway. A weekend event sent to everyone tells weekday regulars nothing new.
Why the split matters to revenue
Quiet nights carry most of the same fixed costs as busy ones: rent, taxes, energy and the core team. Each extra cover on a Tuesday uses space and staff you already pay for. Weekend tables are often full already. Email that pulls more guests into Saturday can end up competing with walk-ins for the same seats.
How do you build weekday and weekend segments from visit data?
You need two things for every contact: valid marketing consent and a dated record of each visit. A guest WiFi login supplies both. The guest opts in on your branded login page. Each later login at your venue adds a dated visit to the same profile, and nobody has to ask for an email address at the register.
Step 1: decide where your week splits
Start with Monday to Thursday as weekday and Friday to Sunday as weekend. Then check it against your own covers. In many venues, Friday evening trades like a Saturday, while Sunday lunch behaves like a segment of its own. Draw the line where your demand changes, not where the calendar does.
Step 2: choose a look-back window
A rolling 90-day window is a sensible starting point. It is long enough to show a pattern and short enough to reflect current habits. Seasonal venues, such as coastal restaurants, may need 180 days to see a full cycle.
Step 3: set the segment rules
Treat these rules as a first draft. Tune the numbers once you see how many guests land in each group.
- Weekday regular: three or more visits in the window, with at least 75% on weekdays.
- Weekend-only guest: two or more visits in the window, none of them on weekdays.
- Mixed guest: two or more visits that fit neither rule.
- Not yet classified: one visit so far. These guests belong in your welcome series, not a day segment.
Step 4: let the segments refresh themselves
Because the window rolls, guests move between segments as they visit. A weekend-only guest who answers a Tuesday invitation and returns becomes mixed. That movement is the result you want, and it is the first thing you measure. A static list exported once a quarter cannot show it.
{"kind":"flow","direction":"lr","caption":"How a guest WiFi login becomes a day-of-week segment","alt":"Flow showing a guest WiFi login with consent producing dated visits, which are classified by day and assigned to a weekday, weekend-only, or mixed and new segment.","nodes":[{"id":"a","label":"Guest WiFi login","sub":"Branded login page at the venue","tone":"brand"},{"id":"b","label":"Consent recorded","sub":"Marketing opt-in, per CCPA/CPRA","tone":"neutral"},{"id":"c","label":"Visit logged with date","sub":"Each later login adds a dated visit","tone":"neutral"},{"id":"d","label":"Visit day classified","sub":"Mon to Thu = weekday, Fri to Sun = weekend","tone":"neutral"},{"id":"e","label":"90-day rule applied","sub":"Counts visits by day in a rolling window","tone":"neutral"},{"id":"f","label":"Weekday regular","sub":"3+ visits, 75%+ on weekdays","tone":"success"},{"id":"g","label":"Weekend-only guest","sub":"2+ visits, none on weekdays","tone":"brand"},{"id":"h","label":"Mixed or new","sub":"Mixed pattern, or one visit so far","tone":"neutral"}],"edges":[{"from":"a","to":"b","label":"opt-in","style":"solid"},{"from":"b","to":"c","label":"same profile","style":"solid"},{"from":"c","to":"d","label":"visit date","style":"solid"},{"from":"d","to":"e","label":"day counts","style":"solid"},{"from":"e","to":"f","label":"mostly weekdays","style":"solid"},{"from":"e","to":"g","label":"weekends only","style":"solid"},{"from":"e","to":"h","label":"neither rule","style":"dashed"}]}
{"tone":"note","title":"Scope","text":"These segments only include guests who logged in to your guest WiFi and opted in to marketing. Read every result as a view of your connected guests, not of every cover."}
Which segmentation terms get confused?
Most mistakes in day-of-week segmentation come from treating two different ideas as one. The table separates the terms that get mixed up most often.
{"caption":"Day-of-week segmentation terms, and how they differ","asOf":"2026-06-10","columns":[{"key":"term","label":"Term"},{"key":"means","label":"What it means"},{"key":"isnot","label":"What it is not"},{"key":"use","label":"Use it for"}],"rows":[["Weekday regular","Repeat guest whose visits fall mostly Monday to Thursday","A loyalty scheme member","Thank-you and recognition emails"],["Weekend-only guest","Repeat guest who visits only Friday to Sunday","A lapsed guest","Quiet-night invitations"],["Mixed guest","Repeat guest who visits across both parts of the week","An unclassified contact","Your standard program"],["Off-peak","Slots with spare capacity, on any day","The same as weekday","Choosing which nights to promote"],["Visit day","The day the guest was in, from the WiFi login","Booking day or send day","Building the segment"],["Frequency","How often a guest visits in a window","Recency","Separating regulars from occasional guests"],["Recency","Time since the last visit","Frequency","Win-back timing"],["Segment","Rule-based group that updates as visits arrive","A static exported list","Campaigns that stay current"]],"footnote":"Day boundaries and thresholds are suggested defaults. Set them from your own trading pattern.","download":{"filename":"weekday-weekend-segment-terms.csv"}}
The costliest mix-up is weekday and off-peak. Weekday describes the calendar, while off-peak describes your capacity. A busy weekday lunch is not off-peak, and a 5pm Saturday slot may be. Build segments on visit day, then point offers at the slots where you have spare tables.
Where do weekday and weekend segments show up in practice?
The split looks different in each type of venue, which is why Step 1 matters.
- Downtown restaurant: weekday regulars come from nearby offices at lunch, and weekend guests come for dinner. Many weekend guests may not know you serve lunch.
- Neighborhood pub or bar: Sunday lunch often forms its own group. Midweek trivia or live music nights give weekend guests a ready reason to visit.
- Hotel restaurant: weekday diners may be business travelers on short stays, and weekend diners leisure guests. Each needs a different tone.
- Multi-site group: a downtown site and a retail park site rarely share the same quiet nights. Set the weekday line per site, not once for the entire group.
What should weekday regulars receive?
Recognition comes first. Thank them for being regulars, by name and by site. Offer things they cannot get elsewhere, such as an early look at a new menu or first reservation for a supper club. Time the send for the day before their usual visit, so the email meets the habit.
Hold back on discounts. The warning below explains why.
{"tone":"warning","title":"The discount trap","text":"A weekday discount sent to weekday regulars mostly pays for visits they would have made anyway. Keep offers for the weekend-only segment, and reward regulars with recognition instead of money off."}
What should weekend-only guests receive?
They need a reason to come in on a quiet night that a Saturday cannot offer. Midweek-only experiences tend to beat blanket money off: a Tuesday tasting menu, a Wednesday trivia night or a Thursday chef's table. Frame it as an occasion, because that is how these guests already treat your venue. Send early in the week, while they are still making plans. Keep one clear call to action, ideally a reservation link for that night.
For templates you can adapt, see these restaurant email marketing examples.
Can email move weekend guests to a quieter night?
Some of them, yes, though you will not know how many until you test it. Some weekend-only guests come on weekends by choice. For others, work, childcare or travel rules out a Tuesday. Email can reach the first group but will not change the second, so expect your results to hit a ceiling. Even so, each extra midweek visit fills a table that would otherwise sit empty.
How do you measure whether it worked?
Use a holdout group. Before each send, set aside about 10% of the segment and send them nothing. Then compare both groups' visits from WiFi logins over the same period.
- Weekend-only guests: the share who make a first weekday visit within 30 days, against the holdout.
- Weekday regulars: weekday visits per guest over 60 days, against the holdout. You want this to hold or rise.
- Weekend visits: check these did not fall. A guest who swaps Saturday for Tuesday frees a seat you can resell, and one who adds Tuesday is better still.
- Revenue per send: add this if you can match visits to POS data. If you cannot, use extra visits as the proxy.
The full method is in how to measure repeat visits to a restaurant.
{"kind":"flow","direction":"tb","caption":"What each day segment receives, and the measure that shows it worked","alt":"Flow from three day segments to the email each receives and the metric used to judge each one against a holdout group.","nodes":[{"id":"r","label":"Weekday regular","tone":"success"},{"id":"w","label":"Weekend-only guest","tone":"brand"},{"id":"m","label":"Mixed guest","tone":"neutral"},{"id":"r1","label":"Thank-you and recognition","sub":"Early menu preview, sent before their usual day","tone":"neutral"},{"id":"w1","label":"Reason to visit midweek","sub":"Midweek-only event or set menu, sent early in the week","tone":"neutral"},{"id":"m1","label":"Standard program","sub":"New menus, seasonal news and events","tone":"neutral"},{"id":"r2","label":"Measure: weekday visits held","sub":"Visits per guest vs holdout over 60 days","tone":"success"},{"id":"w2","label":"Measure: first weekday visit","sub":"Share visiting midweek vs holdout within 30 days","tone":"success"},{"id":"m2","label":"Measure: visit frequency","sub":"Visits per guest vs the previous window","tone":"success"}],"edges":[{"from":"r","to":"r1","label":"send","style":"solid"},{"from":"w","to":"w1","label":"send","style":"solid"},{"from":"m","to":"m1","label":"send","style":"solid"},{"from":"r1","to":"r2","label":"compare with holdout","style":"dashed"},{"from":"w1","to":"w2","label":"compare with holdout","style":"dashed"},{"from":"m1","to":"m2","label":"compare over time","style":"dashed"}]}
What are the limits of day-of-week segmentation?
The segments are only as good as the visits behind them. Plan for these edge cases before you report a result.
- Coverage: guests who never connect to WiFi do not appear in any segment.
- One login per table: in a party of four, often only one person signs in. The segment describes that guest, not the group.
- Thin data: one visit is not a pattern. Keep single-visit guests out of day segments until a second visit arrives.
- Calendar distortions: a Monday federal holiday trades like a Saturday, and December breaks most patterns. Treat federal holidays as weekend days, or exclude them.
- Staff devices: staff on the guest network look like your most loyal weekday regulars. Put them on separate Staff WiFi, or exclude their logins.
- Send fatigue: a day-segmented email should replace a general send, not add another one.
What CCPA/CPRA asks of you
Consent at login covers marketing, but you also need to be open about how you use visit data. Under CCPA/CPRA, consent must be freely given, specific, informed and unambiguous. Withdrawing it must be as easy as giving it. Your privacy notice should explain that visit history shapes the emails guests receive. A guest who objects to direct marketing must leave every segment, not just one.
How does day-of-week segmentation work in Purple Engage?
Purple Engage builds your list from guest WiFi logins as consented, first-party data. Each sign-in on your branded login page records the guest's opt-in. Each later login adds a dated visit to the same profile. The same data builds the segment and measures it, so there are no exports to stitch together.
That is the difference from Mailchimp, Klaviyo and HubSpot. They send campaigns, but they do not build the list. They also cannot see who came in on Tuesday unless someone feeds them that data.
In Purple Engage segmentation, you build day-of-week rules from the same visit history that drives your other segments. For the wider picture, read our practical guide to segmentation for venues and the WiFi marketing guide.
Purple is hardware-agnostic, so the login page runs on the WiFi you already own. Brands including Sweetgreen, Under Armour and Chase use Purple. Branded login pages see opt-in rates around 50% higher, according to Purple's own data.
{"items":[{"value":"80,000+","label":"live venues","note":"In 90 countries, Purple data"},{"value":"500 million","label":"logins a year","note":"Purple data"},{"value":"~50% higher","label":"opt-in rates on branded login pages","note":"Purple data"}]}
Where it bites first, and what to read next
Day-of-week segmentation bites in three places in a real deployment. The first is the opening month, when most guests have one visit and the segments look small. Run your welcome series and let visit history build. The second is your first quiet-night campaign, where the holdout shows whether the email moved anyone. The third is a multi-site property portfolio, where one weekday line for every location hides each location's real pattern. Before your first send, read how to measure repeat visits to a restaurant.
Frequently asked questions
How much does it cost to run weekday and weekend segments?
Day-of-week segments add no extra data-collection cost once guest WiFi is live, because they reuse visits you already capture. Your cost is the Purple plan itself. Purple offers three plans, Connect, Capture and Engage, and pricing depends on the plan and the number of venues. Ask Purple for a quote based on your locations. Then compare it with a separate email platform plus the effort of building a list by hand.
Will it work with the WiFi hardware we already have?
Yes. Purple is hardware-agnostic and runs as a cloud overlay on the access points you already own. Supported hardware includes Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You keep your network and add the branded login page on top. There is no rip and replace, so a venue can start capturing consented visits without new hardware.
Can we bring an existing email list into Purple Engage?
Yes, where the consent behind each contact is valid under CCPA/CPRA. Purple integrates with CRM and marketing platforms, so you keep the contacts you already have. Imported contacts carry no WiFi visit history, though. They only join a weekday or weekend segment after they log in at your venue and build a visit pattern. Until then, keep them in your general program.
Is segmenting guests by visit day CCPA/CPRA compliant?
Yes, when consent is captured properly and you are open about how you use visit data. Purple is CCPA/CPRA compliant and ISO 27001 certified, and captures opt-in at the WiFi login. Your privacy notice should explain that visit history shapes the emails guests receive. Unsubscribing must remove a guest from every segment. Treat day segments as part of the marketing purpose the guest agreed to, not a new purpose.
How is this different from segmenting in Mailchimp or Klaviyo?
The difference is where the visit data comes from. Mailchimp and Klaviyo segment on the data you give them, usually opens, clicks or online purchases, and neither builds the list. Purple Engage builds the list from guest WiFi logins and adds each visit to the same profile. You segment on when guests came in, then measure the next visit with the same data.
How long before the segments are useful?
Expect useful segments after one full look-back window, which is about 90 days with the default rules. Writing the rules is quick. The wait is for visit history to build. In the first weeks, most guests have one visit and sit in your welcome series. Venues with frequent repeat visits, such as weekday lunch spots, will see weekday regulars form sooner.
Does day-of-week segmentation work for bars, hotels and retail?
Yes. The method works anywhere guests return on a pattern and some days run quieter than others. Bars split midweek and weekend nights, and hotels split business and leisure stays. Retailers split weekday and weekend shoppers. Only the day boundaries change. Set them from each venue's own trading pattern, then apply the same rules, messages and holdout measurement.
