Meraki Captive Portal Email Capture

Cisco Meraki is excellent networking hardware, and its cloud dashboard makes guest WiFi straightforward to stand up. What it is not is a marketing platform. If your goal is to capture customer emails from your guest WiFi and actually do something useful with them, you will quickly hit the edges of the native splash page. This tutorial-style guide covers exactly where those edges are, and how to get past them with an external captive portal.

What Meraki's native splash can and cannot do

Meraki gives you several splash options out of the box: click-through (accept terms and connect), sign-on with a RADIUS or directory backend, billing, and a few others. These are great for access control. They are not built for marketing.

The honest limits of the native splash for email-led marketing:

• It is designed to grant access, not to build and store a marketing email list you can export and campaign to.
• There is no built-in email automation: no welcome emails, no offers, no win-back sequences.
• There is no Google review automation.
• UK GDPR consent capture and retention records are left to you to design.
• Per-customer analytics like visit frequency are not the dashboard's job.

This is not a criticism of Meraki. It is networking kit doing networking well. The marketing layer simply lives somewhere else, which is exactly what an external portal is for.

How external captive portal email capture works

The flow keeps Meraki doing what it is good at and hands the splash experience to a dedicated portal:

1. A guest connects to your Meraki guest SSID.
2. Meraki redirects them to your external captive portal URL (the CaptiFi splash page).
3. The guest sees your branded page, enters their email, and ticks a marketing opt-in.
4. The portal records consent, stores the email, and grants access back through Meraki.
5. From there, automated welcome emails, review requests and campaigns run on their own.

Step by step in the Meraki dashboard

1. Create or pick your guest SSID. In the Meraki dashboard go to Wireless, then SSIDs, and select the network you want guests to use.
2. Set association to open. Under Access control, set the network to open so the captive portal can handle authentication.
3. Choose the splash page type. Set the splash page to the external captive portal option and enter your CaptiFi portal URL.
4. Configure the walled garden. Add the portal and any required domains to the walled garden so the splash page and its assets load before the guest is authorised.
5. Connect CaptiFi to Meraki. CaptiFi authorises clients through the Meraki API so guests get online the moment they submit the form. No RADIUS configuration required.
6. Test from a phone. Join the guest SSID, confirm you are redirected to your branded page, submit a test email, and check it appears in your dashboard.

For the full screen-by-screen walkthrough with the exact dashboard settings, see the dedicated Meraki setup guide. CaptiFi works across the Meraki MR access point range.

What an external portal adds

The result: every guest who connects becomes a subscriber, and the follow-ups (welcome email, review request, win-back) run automatically. For the marketing mechanics, see guest email marketing and automating Google reviews.

Keeping it UK GDPR compliant

Because the external portal owns the form, it is also the right place to handle 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 stored record of when and how consent was given. A defined retention period for inactive contacts keeps the list tidy. Our GDPR-compliant guest WiFi guide walks through the five essentials, and the GDPR compliance feature shows how CaptiFi handles them automatically.

If your hardware is not Meraki, the same external-portal approach works on UniFi, Omada and MikroTik. Otherwise, you can start a 30-day free trial and connect your existing Meraki network in minutes.