UniFi Guest WiFi Marketing: Complete Setup Guide
Key Takeaways: Ubiquiti UniFi is the most-installed AP platform among MyWiFi resellers due to zero per-AP licensing costs and a massive reseller install base. The integration connects through the UniFi Network Controller (v5+) using the REST API and built-in Hotspot Manager. Setup takes 10 to 15 minutes per site. UniFi supports both self-hosted and cloud controller deployments. Every MyWiFi feature — social login, WhatsApp OTP, marketing automation, white-label portals — works at full parity with UniFi hardware.
Ubiquiti UniFi owns the SMB WiFi market. The hardware is affordable, the controller software is free, and there are no recurring per-AP license fees. For WiFi marketing resellers, this means lower deployment costs per venue and higher margins on your managed service. When your client already has UniFi APs installed — and many do — you are connecting to existing infrastructure rather than proposing a hardware swap.
This guide covers the complete UniFi guest WiFi marketing setup: controller configuration, guest network creation, captive portal redirect to MyWiFi, REST API integration, multi-site management, and the operational patterns that keep deployments stable across dozens or hundreds of venues.
Why UniFi dominates the reseller install base
UniFi carries the "Most Installed" badge on the MyWiFi hardware compatibility page. The economics explain why:
- •No per-AP licensing. A UniFi U6 Pro costs roughly $150 hardware-only. There is no annual license fee. Compare this to Cisco Meraki, where per-AP licensing adds $150 to $300/year.
- •Free controller software. The UniFi Network Controller (now called UniFi Network Application) runs on any Linux server, Docker container, Raspberry Pi, or Ubiquiti's own Cloud Key hardware. Cloud hosting via
unifi.ui.comis also free. - •Massive channel. UniFi is stocked at every IT distributor. Your clients' local IT company has probably deployed it before. This reduces the "what hardware do I need?" conversation to "you probably already have it."
The tradeoff: UniFi lacks the enterprise management features of Meraki or Aruba (no CMX-style presence analytics, no built-in RADIUS server for external auth). MyWiFi bridges this gap by adding the marketing and analytics layer that UniFi hardware does not provide natively.
Prerequisites
- •UniFi Network Controller v5.0 or later, running and accessible. Self-hosted, Cloud Key, Dream Machine, or
unifi.ui.comcloud all work. - •Controller admin credentials with site-level access
- •Guest network SSID already broadcasting (or you will create one in this guide)
- •MyWiFi account with a location created for the venue
- •Network access between the UniFi Controller and MyWiFi's servers (outbound HTTPS on port 443)
Step 1: Create the guest network in UniFi Controller
Open the UniFi Network Controller. Navigate to Settings → WiFi (or Settings → Wireless Networks in older controller versions).
Click Create New WiFi Network and configure:
- •Name (SSID): Your client's guest network name. Keep it recognizable — "FreeWiFi-[VenueName]" or the client's brand name.
- •Security: Set to Open for a captive portal deployment. Guests will authenticate through the MyWiFi splash page, not through a WiFi password.
- •Network: Assign to a dedicated guest VLAN if your client's network supports VLANs. If not, the default network works but is less secure.
- •Advanced → Guest Policy: Enable the Guest Policy toggle. This is the key setting — it tells the controller to treat this SSID as a hotspot network that requires portal authentication before granting internet access.
Save the network. The SSID will begin broadcasting on all adopted APs in the site.
Step 2: Configure the Hotspot Manager
The UniFi Hotspot Manager is the controller's built-in captive portal system. For MyWiFi integration, you configure the Hotspot Manager to redirect guests to your MyWiFi portal URL instead of using UniFi's built-in splash page.
Navigate to Settings → Guest Control (older versions) or Settings → Hotspot Manager (UniFi Network 7+).
Configure:
- •Guest portal: Enable the guest portal
- •Landing page: Select External portal (not the built-in UniFi portal)
- •External portal URL: Enter your MyWiFi portal URL for this location
The portal URL format:
https://portal.mywifi.io/location/{location-id}
Or with a custom white-label domain:
https://wifi.youragency.com/location/{location-id}
- •Redirect using hostname: Enable this if available. It ensures the redirect works correctly across different client device types.
- •Enable HTTPS redirection: Disable this. HTTPS redirect interception causes certificate warnings on modern browsers and breaks the captive portal flow on iOS and Android. The controller should redirect HTTP requests only; the MyWiFi portal itself serves over HTTPS.
Step 3: Pre-authorization access (walled garden)
Guests need to reach the MyWiFi portal and social login providers before they are authorized. In UniFi, this is configured as pre-authorization access rules.
Navigate to Settings → Guest Control → Pre-Authorization Access (or Hotspot Manager → Pre-Auth Access).
Add these hostnames:
*.mywifi.io
*.mywifinetworks.com
*.facebook.com
*.google.com
*.googleapis.com
*.gstatic.com
*.apple.com
*.whatsapp.com
*.cloudfront.net
Add your custom portal domain if applicable. Each entry allows unauthenticated guests to reach that domain before completing the captive portal login. Without these entries, guests see a broken login page or cannot authenticate with social providers.
Step 4: REST API integration for automated provisioning
MyWiFi connects to the UniFi Controller via its REST API for automated guest authorization and session management. This is what allows MyWiFi to tell the controller "this guest has authenticated — grant internet access" without manual intervention.
In your MyWiFi dashboard:
- •Navigate to Location → Hardware Settings
- •Select Ubiquiti UniFi as the hardware type
- •Enter the controller URL (e.g.,
https://192.168.1.1:8443for self-hosted, orhttps://unifi.ui.comfor cloud) - •Enter the admin username and password for the controller
- •Select the correct site (UniFi controllers can manage multiple sites)
- •Save and test the connection
MyWiFi uses the UniFi API to:
- •Authorize guests: After a guest completes the captive portal login, MyWiFi sends an authorization command to the controller via the API. The guest is granted internet access immediately.
- •Set session parameters: Upload/download limits, session duration, and idle timeout are passed through the API. These map to the bandwidth and time settings in your MyWiFi portal configuration.
- •Disconnect guests: If a session expires or is manually terminated in MyWiFi, a deauthorization command is sent to the controller.
Self-hosted controller notes: If the controller runs on a local network behind NAT, MyWiFi needs to reach it over the internet. Options: port-forward the controller's API port (8443), use a reverse proxy with a public domain, or deploy the controller on a cloud VPS with a public IP. The Cloud Key Gen2 and Dream Machine Pro support remote access through Ubiquiti's cloud relay, which simplifies this.
Step 5: Guest network isolation
Isolate the guest SSID from your client's internal network. This is a security requirement and a best practice for any guest WiFi deployment.
In UniFi Controller:
- •Client isolation: Under the guest network settings, enable Client Device Isolation. This prevents guests from seeing or communicating with other guest devices on the same network.
- •VLAN segmentation: If your client's infrastructure supports VLANs, assign the guest SSID to a dedicated VLAN (e.g., VLAN 200). Configure firewall rules on the router or USG to block traffic from the guest VLAN to the corporate VLAN.
- •Content filtering: UniFi's Traffic Management can block specific categories of traffic on the guest network. This is optional but useful for family-friendly venues.
Bandwidth limits: Set per-client bandwidth limits in the guest network configuration. A reasonable default is 5 Mbps down / 2 Mbps up. These can also be set per-user through MyWiFi's portal settings, which override the controller defaults when using the REST API integration.
Step 6: Multi-site management for resellers
If you manage UniFi deployments across multiple client venues, the multi-site architecture matters.
Option 1: Single controller, multiple sites. The UniFi Controller supports multiple "sites" within one instance. Each site is an independent network with its own APs, settings, and admin access. You run one controller and create a site per client venue. This is the most common reseller pattern.
- •Pros: Single management interface, lower infrastructure cost
- •Cons: All sites share the controller's uptime. If the controller goes down, all sites lose guest portal functionality.
Option 2: Cloud controller (unifi.ui.com). Ubiquiti's cloud-hosted controller eliminates the self-hosted infrastructure. Sites are managed through the web console. This is the simplest option for resellers who do not want to maintain server infrastructure.
- •Pros: No server maintenance, accessible from anywhere, automatic updates
- •Cons: Feature parity with self-hosted is not always 100%. Some advanced settings may not be available in the cloud version.
Option 3: Per-venue controllers. Each client venue has its own Cloud Key or Dream Machine with an embedded controller. You manage each independently.
- •Pros: Complete isolation between clients. One client's controller issue does not affect others.
- •Cons: More devices to manage. Higher hardware cost per venue.
In MyWiFi, each venue is a separate location regardless of which controller architecture you use. The MyWiFi white-label dashboard gives each client access only to their own venues.
Step 7: Testing the complete flow
Test every path before going live:
- •Connect to the guest SSID from a mobile device. You should be redirected to the MyWiFi captive portal within 2 to 5 seconds.
- •Complete a login using each enabled method (social login, email, WhatsApp, etc.).
- •Verify internet access is granted immediately after login.
- •Check the MyWiFi dashboard for the new guest record. It should appear within 60 seconds.
- •Test session timeout: Disconnect from WiFi, wait for the session to expire, and reconnect. The portal should appear again (or the "Welcome Back" instant reconnect should trigger for returning guests).
- •Test from multiple device types: iOS, Android, and a laptop. Apple's Captive Network Assistant (CNA) and Android's captive portal detection each handle redirects differently.
Common issues:
- •No redirect to portal: Guest Policy is not enabled on the SSID, or the Hotspot Manager external portal URL is incorrect.
- •Portal loads but login fails: Pre-authorization access is missing social provider domains.
- •Login succeeds but no internet: REST API credentials are incorrect or the controller is unreachable from MyWiFi's servers. Check the controller URL and credentials in MyWiFi's hardware settings.
- •iOS shows a mini browser instead of full Safari: This is Apple's CNA. It is expected behavior. The MyWiFi portal is optimized for the CNA viewport. After login, guests can close the CNA and browse normally.
UniFi hardware recommendations by venue type
Not all UniFi APs are equal. Match the hardware to the venue:
- •U6 Pro / U6+: Standard indoor AP. Covers 1,500 to 2,000 sq ft. Suitable for restaurants, retail stores, small offices, cafes. This is the default recommendation for most reseller deployments.
- •U6 Enterprise: High-density indoor AP with 6 GHz support (WiFi 6E). Conference centers, coworking spaces, hotel lobbies with 50+ concurrent guests.
- •U6 Mesh / U6 Extender: Outdoor or hard-to-wire areas. Patios, beer gardens, parking areas. Mesh backhaul when Ethernet is not available.
- •U6 Long-Range: Extended coverage for large open areas. Warehouses, dealership lots, event spaces.
For resellers building a hardware bundle, the U6 Pro at its price point delivers the best value for single-AP venue deployments. Your pricing model can include hardware as a one-time cost or fold it into the monthly service fee.
Comparing UniFi to enterprise alternatives
UniFi wins on cost but loses on built-in analytics and enterprise management. Here is where it sits relative to other supported hardware:
| Feature | UniFi | Meraki | Aruba |
|---|---|---|---|
| Per-AP license | None | $150-300/yr | Varies |
| Cloud management | Free | Included (required) | Aruba Central ($) |
| Presence analytics | No native | CMX Scanning API | ClearPass |
| REST API | Yes | Yes | Yes |
| MyWiFi feature parity | Full | Full | Full |
For resellers comparing hardware options across their client portfolio, visit the full hardware compatibility page for specifications on all 20+ supported vendors.
FAQ
Does MyWiFi work with UniFi Network Application v8 (the latest)?
Yes. MyWiFi supports UniFi Network Controller v5 and above, including the latest v8 releases. The REST API endpoints remain compatible across versions. If Ubiquiti makes breaking API changes in a future release, MyWiFi's integration team updates the connector.
Can I use UniFi's built-in guest portal instead of MyWiFi?
UniFi has a basic built-in splash page, but it does not support social login, marketing automation, data capture, analytics, or white-labeling. MyWiFi replaces the UniFi portal with a full-featured captive portal while using UniFi's Hotspot Manager for the redirect mechanism.
Do I need a Cloud Key, or can I use a self-hosted controller?
Either works. Self-hosted controllers (Docker, Linux VM, bare metal) and Cloud Key / Dream Machine embedded controllers are all supported. The key requirement is that MyWiFi can reach the controller API endpoint over HTTPS. For self-hosted controllers behind NAT, you need to expose the API port or use a reverse proxy.
How many concurrent guests can a UniFi AP handle?
Ubiquiti rates the U6 Pro for up to 300 concurrent clients. Practical performance for guest WiFi with captive portal typically caps at 50 to 80 concurrent active sessions per AP before throughput degrades. High-density venues should deploy multiple APs rather than overloading a single unit.
What about MAC randomization breaking analytics?
Modern iOS and Android devices use randomized MAC addresses per SSID. This means presence detection based on MAC alone is unreliable. MyWiFi addresses this by tying analytics to authenticated session data (the portal login) rather than raw MAC addresses. Once a guest logs in, their identity is tracked across visits regardless of MAC changes.
Can I manage UniFi and Meraki venues from the same MyWiFi account?
Yes. MyWiFi is hardware-agnostic at the account level. Each location is configured with its own hardware type. You can have 10 UniFi venues and 5 Meraki venues under a single reseller account, each with the correct hardware integration. Your clients see their venues in the white-label dashboard without knowing which hardware runs underneath.
Next steps
- •Configure your first UniFi venue — Follow the steps above and test the captive portal flow end-to-end
- •Explore portal optimization — Read the captive portal best practices guide to push opt-in rates above 60%
- •Compare hardware options — See the full hardware compatibility page for all 20+ supported vendors
- •Build your pricing model — Visit MyWiFi pricing to align your reseller tier with your deployment scale
- •Book a demo — Schedule a live demo to see UniFi integration in action
UniFi's zero-licensing economics combined with MyWiFi's marketing and analytics platform give resellers the lowest cost-per-venue deployment in the industry. The hardware is everywhere, the integration is proven, and every feature — from real-time analytics to automated guest segmentation — works at full parity. Connect your first venue, prove the ROI, and scale from there.