WiFi Marketing at Scale: Managing Multi-Location Data Without Losing Local Context

Why Single-Venue Architecture Breaks at Scale

A single venue has one login page, one list and one set of campaigns. Every guest on the list is a guest of that venue, so every email is relevant to everyone on it.

Add a second and third site and that stops being true. A guest of your city centre site may never have been to the one by the station. A new chef or a refurbishment at one site is noise to everyone else. Send everything to everyone and people start ignoring you, or unsubscribe from all your venues at once.

With more sites, more questions pile up: guests who use several venues, franchise versus company owned sites, different menus and prices, regional campaigns, and reporting that has to work for both the group and each manager. None of these exist at one venue, and each needs a decision.

The Three Architecture Models

Model 1: Location-Isolated Lists Each venue runs as its own island: its own guest WiFi setup and its own email audience. Nothing is shared.

Best for: franchise networks where each franchisee owns their guest relationships, and groups whose venues are different brands.

Limitations: you cannot see when one guest uses two venues. Group reporting means adding up spreadsheets by hand. A group wide announcement has to be sent once per venue. If you use Mailchimp with one audience per venue, note that Mailchimp bills on the total contacts across all your audiences, so a guest who sits in two audiences counts twice (Mailchimp, Requirements and best practices for audiences).

Model 2: Single Brand List with Location Tags Every guest from every venue goes into one audience, tagged with each venue where they have logged in. Local campaigns go to a segment of one venue's tag. Group campaigns go to everyone.

This is the model Mailchimp itself recommends: one audience, organised with tags, groups or segments (same Mailchimp article). It is also how the VoqadoWiFi Mailchimp sync works on Growth and above: each guest it syncs is added to your audience with the tag wifi-guest plus a location tag (location: followed by the venue name) for the venue where they logged in. A guest who logs in at two venues ends up with both location tags. The sync only adds guests who ticked the separate, unticked marketing box on the login page, so every WiFi contact it adds is a guest who agreed to marketing.

Best for: branded chains with a central marketing person or team.

Limitations: someone has to decide which venue "owns" a guest who uses several. Tags must be kept tidy: if a venue is renamed, new logins get a tag with the new name while earlier guests keep the old one, so update saved segments to include both. And if your venues sit in different countries or states, the consent and privacy rules can differ between them (see the compliance note below).

Model 3: Federated Architecture Each venue keeps a local list for local campaigns, and a central master list holds every guest from every venue with location tags. Local managers work their own list; the group sends from the master.

It answers both needs, but at a cost. In Mailchimp, local lists plus a master list means separate audiences, so guests are counted (and billed) more than once, and Mailchimp only checks for duplicates within an audience, not across audiences (Mailchimp, About duplicate contacts). Consent also has to stay in step: a guest who unsubscribes from the master list is still subscribed on the local one unless you handle it.

Our view: unless franchisees genuinely own their data, Model 2 with good segments gives local managers what they need with one place to manage consent. Use Model 3 only when ownership forces it.

Cross-Location Visitor Tracking

In Models 2 and 3, the email address is the key that matches a guest across venues. A guest who logs in at Venue A and later at Venue B is one record with two venues.

In VoqadoWiFi, the guest list export includes a "Venues visited" column and a "Favourite venue" column, plus visit counts and first and last visit dates. Filter the export for guests with two or more venues and you have your cross site list.

Treat that group as a segment worth testing rather than an assumed VIP tier. They have shown they will choose you in more than one place, which is a good reason to tell them about a new site or a group wide event first. Measure whether they respond better than single site guests with a holdout test before you build your plans around them.

Watch the frequency. A guest tagged at two venues can receive both venues' local emails plus every group email. Decide a group wide limit on how many emails one guest gets in a month, and check segments against it before each send. (VoqadoWiFi's own post visit messages, which are switching on venue by venue as email goes live, are capped at 1 per guest per venue every 7 days and 4 every 30 days, with quiet hours from 21:00 to 09:00 venue local time by default.)

Brand-Level vs Location-Level KPIs

At scale, you need both.

Brand-level KPIs: total opted in guests across all venues, the share of guests who opt in across the group, email performance for group sends, revenue you can attribute (measured with promo codes or holdout groups), and list growth by region.

Location-level KPIs: each venue's opt in share, list growth, click rate on local emails, campaign revenue where measured, and how many guests return.

Compare each venue to the group's middle value, not to an industry figure. A venue well below the rest of your group on opt in share usually has a fixable cause: the network name does not mention the venue, there is no table card, staff give out a password instead of pointing at the login page, or the login page wording differs from the other sites.

Compliance note. This is general information, not legal advice. Rules on marketing consent depend on where the guest and the venue are. In the UK, for example, marketing emails to individuals generally need their consent, with a narrow exception for existing customers (ICO, Electronic mail marketing). California has its own privacy law and its own regulator, the California Privacy Protection Agency. If your venues span jurisdictions, get advice for each one and record which rules each venue's login page follows.

Illustrative example: how a 15-location restaurant group could run it

This is an illustrative example, not a customer story, and it makes no claims about results.

A casual dining group with 15 sites uses Model 2. Every site asks for marketing consent as a separate, unticked choice, and one Mailchimp audience holds the group's guests, tagged by venue. Group sends go only to guests who agreed to marketing. A central marketing team of two owns the audience, the login page template used at every site, the email templates and consent records.

Each site manager asks for one or two local emails a month (a new menu, a quiz night) using a group template, and the central team sends them to that venue's tag. The central team also sends a few group emails a month to everyone, checking the monthly limit per guest before each send. Once a month, the team reviews each venue's opt in share against the group's middle value and visits the sites at the bottom.

On VoqadoWiFi, a group of this size would be on the Enterprise plan, which is priced on request; Growth covers up to 3 locations (pricing). All of it runs only on TP-Link Omada or Ubiquiti UniFi networks.

If you are moving a group to this model, start by listing every venue's current audience and how its consent was collected. Merge only lists where the consent wording supports the emails you plan to send.