Square POS and Guest WiFi: Capture Every Visitor

Square is one of the most popular point-of-sale systems for independent UK cafes, retailers and service businesses, because it is quick to set up and easy to run. It tells you exactly what sold, when, and for how much. What it cannot tell you is who most of your visitors actually are, or how to reach them again, because a card transaction only ever knows about the person who paid.

That is the gap this guide is about. Square POS gives you spend data. Guest WiFi gives you reach, an email address from every visitor who connects, not just the one who happened to tap a card. Put the two together and you can match visits to spend, see who your most valuable customers really are, and automatically ask happy visitors for a Google review after they leave. We will also be honest about how the Square connection works in practice, because it goes through Zapier rather than a deep native sync, and that distinction matters.

The gap Square POS alone cannot close

Square is excellent at the moment of payment. The problem is everything around it. A table of four orders lunch and one person pays; Square records one customer and one total, and the other three are invisible. A shopper browses for ten minutes, tries something on and leaves without buying; Square never knew they were there at all. A regular pays with contactless every week; Square sees a string of anonymous transactions with no name attached and no way to email them.

In other words, Square answers "what sold" but not "who is in my venue and how do I bring them back". For a business whose growth depends on repeat visits, that second question is the one that actually drives revenue, and it is the one Square alone cannot answer.

Capturing data from every visitor, not just payers

This is where guest WiFi changes the picture. A captive portal does not care whether someone paid. It captures an email from everyone who connects: the three companions who did not pay, the browser who left empty-handed, the regular who taps and goes. When a guest joins your free WiFi, a branded splash page captures their email with UK GDPR consent in about five seconds, and that contact is yours.

UK venues running this typically capture 40 to 60 percent of connecting guests as email subscribers, and across the CaptiFi platform venues build lists of 400 to 1,200 emails per month. That is a dramatically wider net than payment data alone: instead of one contact per transaction, you reach a large share of everyone who walked in. This is the core idea behind turning anonymous footfall into a usable database, which our guide to anonymous foot traffic covers in depth.

The two data sources are complementary rather than competing. WiFi gives you reach across every visitor. Square gives you revenue attribution on the ones who paid. Neither is complete on its own; together they describe both who came in and what your business actually earned.

Matching visits to spend

Once you have an email from a visitor and a transaction from Square, you can start to join them up. When a customer pays with a card and that same person has connected to your WiFi with their email, you can associate the spend with the contact. Over repeat visits this lets you:

• Identify your high-value customers by total or average spend, so you can treat your best regulars accordingly.
• Segment your email list by spend band, so a premium offer goes to your big spenders and a value offer goes to occasional visitors.
• Spot lapsed high-spenders who have stopped coming and target them with a win-back before they are gone for good.

It is worth being realistic about the matching. It works cleanly when the same person both pays and connects to WiFi with a consistent email. It will not perfectly attribute every visit, because the payer and the WiFi user are not always the same person and not everyone connects. But even partial spend attribution across your most frequent customers is far more than Square or WiFi could tell you alone, and it is enough to target your marketing where the revenue actually is.

How the Square connection actually works

Here is the honest part, because it shapes what you can expect. CaptiFi connects to Square through Zapier, not through a deep two-way native integration. Square publishes transaction events, Zapier listens for them, and those events can flow into your CaptiFi contact data so that spend information sits alongside the email you captured on WiFi.

What that means in practice:

• It is genuinely flexible. Zapier sits between thousands of apps, so the same connection can branch transactions out to a CRM, a spreadsheet or an email tool at the same time.
• It is not instantaneous or perfectly granular. A Zapier-based link passes the data Square exposes through its events, on Zapier's schedule, rather than offering the millisecond, line-item depth of a purpose-built native sync.
• It does require setting up the Zap. You connect both accounts in Zapier once and define what should happen when a Square sale occurs. After that it runs on its own.

We flag this plainly because some platforms imply a deeper Square integration than they really have. For most independent cafes and retailers, a Zapier connection is more than enough to match visits to spend and trigger follow-ups, and it avoids tying you to a single rigid pipeline. If you want the specifics of the connection, see the Square POS integration page and our general Zapier integration details. (If you run a restaurant on a different till, a deeper native option may exist; our Toast POS integration is one example.)

Automating post-visit reviews

The combination really pays off with reviews. Because you captured an email from every visitor, not just the payer, you can ask far more people for a Google review than payment data alone would ever reach. CaptiFi sends a review request a few hours after the visit, when the experience is fresh and the guest is no longer at the counter, with a one-tap link.

This converts much better than a QR code by the till or a member of staff remembering to ask, and across CaptiFi venues automating it typically lifts review volume by around 3 to 5 times the manual rate. For a Square-based cafe or shop, that means a steady flow of fresh reviews from the wide audience your WiFi captured, which feeds local-pack visibility and brings new customers through the door. The full mechanics are in our guide to automating Google reviews with guest WiFi.

This works across venue types. The same approach drives repeat visits for cafes and reduces churn in physical retail, where capturing the browsers who never reach the till is exactly the point.

UK consent done properly

Capturing visitor emails and joining them to spend is lawful when set up correctly. Nothing here is legal advice, but it reflects the standard approach for public WiFi in the UK, with the ICO as the regulator. The splash page keeps getting onto the WiFi separate from agreeing to marketing, uses an unticked marketing checkbox so the visitor actively opts in, links to a plain-English privacy notice and records consent. PECR then requires a one-click unsubscribe in every marketing email, and you should hold contacts only for a defined retention period. A managed portal handles all of this automatically. Our GDPR-compliant guest WiFi guide has the full checklist.

Getting started

If you run Square and offer free WiFi with a password on the wall, you already have both halves of the puzzle, you are just not connecting them. Joining them up is quick:

1. Start a 30-day free CaptiFi trial, no card required.
2. The free plug-and-play device ships out, or connect your existing access points.
3. Brand your splash page so every visitor, not just payers, is captured with consent.
4. Set up the Square-to-CaptiFi Zap once, so transactions flow into your contact data.
5. Post-visit review requests and spend-based segments run on autopilot from $69/mo.

Square tells you what sold. Add guest WiFi and you finally know who came in, how to reach them, and which of them are worth the most, all from one captured email.