26 October 2026
Article

Captive Portal Revenue Attribution Example

Zainab
Marketing and Success Strategist at Affinect

A restaurant can see 500 people connect to guest WiFi this month and still have no answer to the question that matters: did those identified guests spend more, come back, or respond to a campaign? A captive portal revenue attribution example makes that connection visible. It ties a consented guest login to visit behavior, marketing activity, and transaction data, so operators can see exactly what is driving revenue.

For hospitality businesses, attribution is not about giving WiFi credit for every sale. It is about building a defensible view of how guest identification and retention activity influence measurable commercial outcomes. That distinction matters when marketing budgets, technology investments, and operator time are under scrutiny.

The operating problem: foot traffic without a revenue trail

Most venues have no shortage of visitors. The gap is identity. A guest walks in, scans a QR code or joins WiFi, places an order, and leaves. Unless they use a loyalty account, make a reservation, or transact through a delivery platform, the venue may not know who they are or whether they return.

This creates a familiar reporting problem. A marketing manager can report email opens or WhatsApp clicks. An operations team can report covers, transactions, and average check. Neither team can reliably show whether identified guests return more often than anonymous guests, or whether a specific retention campaign produced incremental sales.

A branded captive portal changes the starting point. Every login becomes a contact, subject to the guest’s consent and the venue’s privacy policy. The platform can then attach behavioral signals such as location, login date, visit frequency, dwell time, preferred venue, and campaign engagement to a unified guest profile.

The commercial value appears when those profiles are matched to a reliable visit or transaction event.

A captive portal revenue attribution example for a restaurant group

Consider a casual dining group with six locations. The group launches branded guest WiFi across all sites and asks guests to sign in with a mobile number or email address. The portal presents clear consent options for marketing communications. Over 90 days, 18,000 guests log in and 11,200 provide valid marketing consent.

The group uses an identifier such as a hashed mobile number, email address, loyalty token, or POS-linked receipt reference to match consented profiles to transactions where available. It also records WiFi return visits, even when a POS match is unavailable. This produces two related measurements: verified transaction revenue and engagement-led return behavior.

After the first visit, the group creates a segment for guests who have visited once but not returned within 21 days. That segment receives a targeted weekday offer: a complimentary dessert with a minimum spend, valid for 14 days at the location they first visited.

Of 3,000 eligible guests, 1,050 receive the message successfully. Some contacts may be excluded because they opted out, supplied invalid details, or fall outside the campaign rules. Of the delivered audience, 210 guests return during the offer window and complete a matched transaction.

The numbers could look like this:

  • 210 matched returning guests generated $12,600 in sales.
  • Their average check was $60.
  • The same guests had generated $4,200 on their original visits during the measurement period.
  • The offer cost was $840 in redeemed desserts.
  • Campaign delivery and platform costs allocated to the campaign were $360.

The attributable repeat revenue is $12,600. The net revenue after direct redemption and campaign costs is $11,400. If the restaurant uses a 68% gross margin, the estimated gross profit contribution from those return transactions is $8,568 before campaign costs, or $7,368 after the $1,200 direct campaign cost.

That is useful, but it is not yet the whole attribution story. Some of those guests may have returned without receiving the message. Some may have seen the offer but visited for another reason. A commercially credible report should distinguish attributed revenue from proven incremental revenue.

How to make the result more credible

The simplest attribution rule is last-touch attribution: if a guest received or clicked a campaign and transacted within a defined window, credit the campaign. This is practical for daily reporting and can show which audience, location, or message is producing the strongest response.

However, last-touch attribution can overstate impact, especially for high-frequency guests. A regular customer may return regardless of a reminder. For a better estimate of incremental revenue, compare campaign recipients with a holdout group that did not receive the message.

In this example, the group holds back 10% of eligible guests. The campaign reaches 945 guests, while 105 similar guests receive no campaign. During the 14-day window, 20% of campaign recipients return, compared with 12% of the holdout group.

The eight-point difference is the estimated incremental lift. Applied to 945 recipients, that suggests roughly 76 incremental returning guests. At a $60 average check, estimated incremental revenue is approximately $4,560. This is a more conservative number than total attributed revenue, but it is often the number leadership should use when assessing campaign ROI.

Both metrics belong in the report:

  • Attributed revenue shows the sales associated with identified guests who were exposed to a campaign.
  • Incremental revenue estimates the sales that likely would not have happened without that campaign.

The first supports operational optimization. The second supports budget decisions.

The data points that make attribution work

A captive portal is only one part of the measurement design. Revenue attribution depends on a consistent identity strategy and clean event data. If the login record cannot be matched to a visit or transaction, the business can still measure return behavior, but it should not claim verified sales attribution.

At minimum, operators should capture a consented guest identifier, first and most recent visit date, venue location, campaign delivery status, campaign engagement, and a transaction or validated visit event. For groups with multiple locations, location IDs must be standardized. Otherwise, a guest who visits three branches may appear as three separate people.

The attribution window also needs to match the buying cycle. A lunch offer may justify a three-day or seven-day window. A premium restaurant, family entertainment venue, or mall-based concept may need 30 days or longer. There is no universal answer. The right window reflects typical visit frequency, offer expiry, and the time it takes for guests to make a return decision.

It is also wise to establish exclusion rules before launching a campaign. Employees, test accounts, duplicate profiles, refunded checks, and canceled orders can distort results. So can discount stacking. If a guest redeems three offers at once, the operator needs a clear rule for which campaign receives credit.

What leaders should see in the dashboard

A useful attribution dashboard does not stop at opens and clicks. It connects the marketing funnel to venue economics. For each campaign, operators should be able to see delivered audience, identified return visits, matched transactions, attributed revenue, offer redemptions, average check, return rate, and net revenue after promotion cost.

The most valuable view is often comparative. Which locations generate the highest consent rate? Do first-time guests who connect to WiFi return more often than those who do not? Does a WhatsApp reminder outperform email for lapsed guests? Are guests acquired at one branch visiting other branches later?

These answers help teams act with precision. If one location has strong portal logins but weak repeat visits, the issue may be the offer, service experience, menu fit, or follow-up timing. If a campaign drives return visits but average check falls sharply, the promotion may be attracting discount-led behavior rather than profitable loyalty.

Affinect is designed to bring these signals into one operating view: consented guest capture, profiles, segmentation, campaign delivery, visit behavior, and attributed revenue. This reduces the manual reconciliation that often leaves operators reporting activity instead of impact.

Attribution should guide the next action

The goal is not to produce a more attractive monthly report. The goal is to decide what to do next. When a venue can identify the guest segments, messages, locations, and offers tied to profitable return behavior, it can shift spend away from broad acquisition and toward retention programs that can be measured.

Start with one defined use case, such as converting first-time WiFi users into a second visit within 21 days. Set the attribution rules before launch, keep a small holdout group where possible, and review both revenue and margin. A clear captive portal revenue attribution model turns guest WiFi from a cost of service into a measurable growth channel.

Connect captive portal logins, campaigns, and attributed return revenue in one view with Affinect.

Explore the Affinect platform