Meraki + CaptiveWiFi Integration

The simplest captive
portal setup available.

Cisco Meraki's external captive portal feature makes CaptiveWiFi the easiest integration we offer. Paste your portal URL into the Meraki dashboard. That's it. No RADIUS server, no API keys, no scripts.

Simplest integration we offer
1
Open Meraki dashboard
2
Set portal type to "Click-through" or "Sign-on"
3
Paste your CaptiveWiFi portal URL
Done. Live in under 10 minutes.
Why CaptiveWiFi + Meraki

Everything your Meraki network
was missing.

Meraki handles your network. CaptiveWiFi handles your guests. Together they turn every WiFi login into a verified customer record.

No RADIUS, no scripts, no complexity
Meraki's external captive portal feature is the simplest integration method in the industry. CaptiveWiFi uses it natively — one URL, zero infrastructure.
Guest identity at the point of connection
Every device that connects to your Meraki guest SSID is prompted to identify themselves. Name, email and marketing consent captured in seconds.
Fully branded portal
Your guest portal matches your brand exactly. Logo, colours, fonts, imagery. No Cisco branding. No generic splash page.
GDPR-compliant data capture
Every guest record includes a full consent audit trail. Opt-in, timestamp, IP address and the exact wording they agreed to. Built for UK and EU compliance.
Real-time visit intelligence
See who is in your venue right now. New guest or returning? First visit this week or tenth this month? CaptiveWiFi tells you instantly.
Automatic marketing triggers
Connect CaptiveWiFi to Klaviyo, Mailchimp or your CRM. First visit, return visit, lapsed guest — each triggers the right campaign automatically.
How it works

Three steps.
Under 10 minutes.

Meraki's external portal feature does all the heavy lifting. CaptiveWiFi just needs a URL.

1
Get your CaptiveWiFi portal URL
Sign up at captivewifi.com, create your venue and design your portal. You'll receive a unique portal URL for your venue.
2
Paste it into Meraki
In the Meraki dashboard, go to Wireless → Access Control → Splash Page. Set the type to "Click-through" or "Sign-on with my RADIUS server" and paste your CaptiveWiFi URL.
3
Go live
Save the settings. Connect a device to your guest SSID to test. Your branded portal loads, captures the guest, and grants access. Done.
Compatibility

Works with your
existing Meraki hardware.

No hardware replacement required. CaptiveWiFi works with all current Meraki wireless access points and MX security appliances.

Meraki MR series (all models)
Meraki MX Security Appliance
Meraki Dashboard (cloud managed)
Meraki Go
Cisco Catalyst (Meraki managed)
All firmware versions
FAQ

Common questions about
Meraki + CaptiveWiFi.

Why is Meraki the simplest integration?
Meraki has a built-in external captive portal feature that simply redirects guests to a URL of your choosing. CaptiveWiFi provides that URL. There's no RADIUS server to configure, no API authentication, no scripts to install. It's a single setting in the Meraki dashboard.
Do I need to change my existing Meraki setup?
No. You keep your existing Meraki configuration, SSIDs, VLANs and security policies. You only change the splash page setting on your guest SSID — everything else stays the same.
Does this work with Meraki's splash page feature?
Yes. CaptiveWiFi replaces Meraki's built-in splash page with your own fully branded experience. Meraki still handles all network-level access control — CaptiveWiFi handles the guest-facing portal, data capture and marketing integrations.
Is this GDPR compliant?
Yes. CaptiveWiFi is fully GDPR and UK GDPR compliant. Every guest record includes a consent timestamp, the exact consent wording displayed, IP address and opt-in status. A full DPIA is available on request.
Can I use this across multiple Meraki sites?
Yes. CaptiveWiFi is built for multi-site operators. Each venue gets its own portal, branding and data set. Group-level reporting lets you see performance across all locations from a single dashboard.
Other integrations

CaptiveWiFi connects to
your whole stack.