MikroTik Hotspot Email Capture

MikroTik is the network engineer's favourite. RouterOS is powerful, cheap and endlessly configurable, which is exactly why it turns up in so many pubs, cafes and small hotels where a local engineer did the install. RouterOS also ships with a capable built-in hotspot. What it does not ship with is a marketing system. If you want to capture customer emails from your MikroTik guest WiFi and turn them into repeat visits, this walkthrough shows you how.

What the RouterOS hotspot does

The RouterOS hotspot intercepts unauthenticated clients and presents a login page (the familiar login.html served from the router's hotspot directory). You can edit those HTML files, set up user profiles, apply bandwidth limits, and authenticate against local users or a RADIUS server. For controlling access, it is genuinely flexible.

But for email-led marketing, the honest limits are clear:

• The stock hotspot is built to authenticate and grant access, not to build a marketing list you can export and campaign to.
• There is no email automation: editing login.html to collect an address does not send a welcome email, an offer or a review request.
• There is no Google review automation and no per-customer analytics.
• UK GDPR consent capture and retention records are entirely on you to build into the page and a backend.

You can hand-roll a form into login.html that posts an email somewhere, but you are then building and maintaining a backend, an email platform integration and a consent store yourself. That is a project, not a setting.

Why route to an external portal

The cleaner approach keeps RouterOS doing the part it is good at (intercepting and authorising clients) and hands the splash experience to a dedicated external captive portal. The hotspot redirects guests to the portal URL, the portal handles the branded page, email capture, consent and follow-ups, then authorises the client back through MikroTik. You skip the custom backend entirely.

RouterOS hotspot walkthrough

1. Run the hotspot setup. In WinBox or WebFig, go to IP, then Hotspot, and run the Hotspot Setup wizard against your guest bridge or interface. This creates the hotspot server, address pool and walled-garden basics.
2. Point the login page at the external portal. Configure the hotspot so unauthenticated guests are redirected to your CaptiFi portal URL rather than the stock login.html.
3. Set the walled garden. Add the portal domain and any required asset domains to IP, Hotspot, Walled Garden, so the branded splash and its resources load before the guest is authorised.
4. Connect CaptiFi to RouterOS. CaptiFi authorises clients through the RouterOS API once they submit the form, so guests get online immediately. No separate RADIUS server required.
5. Test from a phone. Join the guest network, confirm the redirect to your branded page, submit a test email, and check it lands in your dashboard.

For the full screen-by-screen RouterOS configuration with the exact settings, see the dedicated MikroTik setup guide. CaptiFi works across the RouterOS range including hAP, hEX and CCR devices.

What the external portal adds

Once it is live, every guest who connects becomes a subscriber and the follow-ups run automatically. For the marketing side, see guest email marketing and automating Google reviews.

Getting UK GDPR right

Because the external portal owns the form, it is the right place to do consent properly: a marketing opt-in kept separate from getting onto the WiFi, an unticked box so the guest actively opts in, a linked privacy notice, and a record of when and how consent was given, plus a defined retention period for inactive contacts. Our GDPR-compliant guest WiFi guide covers the five essentials, and the GDPR compliance feature shows how CaptiFi handles them automatically.

Not on MikroTik? The same external-portal approach works on UniFi, Omada and Meraki. Otherwise, start a 30-day free trial and connect your RouterOS hotspot in minutes.