Managing Multiple Locations: One Dashboard, Many Portals

Scaling From One Venue to Many

Running WiFi marketing across multiple locations introduces complexity: each venue has its own branding requirements, its own guest base, and its own campaign calendar. VoqadoWiFi's multi-location architecture is designed to give you centralised control without forcing a one-size-fits-all approach. You can manage 2 locations or 200 from the same dashboard.

Step 1: Create Separate Location Profiles

In the VoqadoWiFi dashboard, go to Locations → + New Location for each venue. Each location has its own: Location ID, Portal URL slug, Omada integration credentials, branding configuration, guest database, and analytics reporting. Avoid the temptation to run multiple venues under one location — it mixes guest databases irreparably and makes analytics meaningless. If you acquired an existing venue that has been collecting contacts under a single location, contact support to request a database split before adding the new site.

Step 2: Configure Location-Specific SSIDs

Each VoqadoWiFi location maps to one or more SSIDs in your Omada controller. In Omada, you can have multiple SSIDs on the same hardware pointing to different portal URLs — useful if you want a separate SSID for staff (bypassing the portal) and guests (full portal experience). In VoqadoWiFi, go to Location Settings → SSIDs and list all SSIDs associated with this location. This ensures accurate attribution — a login on "CafeMainStreet_Guest" is correctly attributed to the Main Street location, not confused with a different site.

Step 3: Clone Portal Config Between Locations

If your venues share branding (same logo, same colour scheme), you don't need to rebuild portal configuration from scratch. In Portal Builder, open your primary location's portal, click Actions → Clone to Location. Select the destination locations (multi-select is supported). The clone copies: logo, colours, form fields, consent text, post-login redirect, and offer settings. It does not copy Omada credentials (these are location-specific). After cloning, go into each new location and update the Privacy Policy link if it includes a venue-specific address, and adjust the welcome headline if it references the venue name explicitly.

Step 4: Run Location-Filtered Campaigns

Every campaign in VoqadoWiFi can be scoped to one or more locations. In Campaigns → + New Campaign → Audience, always add a Location filter first: Location is [Venue Name]. This ensures guests from Location A never receive emails about Location B. If you want to run a chain-wide promotion (e.g., a seasonal offer across all venues), create one campaign per location rather than one campaign with no location filter — this gives you per-location analytics and allows you to customise the body copy slightly per venue.

Step 5: Compare Performance Across Sites in Analytics

Go to Analytics → Multi-Location View (available on Growth and Enterprise plans). The comparison dashboard shows, side by side for each location: 30-day new guest count, 30-day return rate, email open rate, and revenue attribution. Sort by any column to identify your top and bottom performers. A location with high footfall but low email capture rate likely has a portal conversion problem (poor design, friction in the form). A location with high capture rate but low return rate has a retention problem (weak follow-up campaigns or in-venue experience issues).

Step 6: Set Up Per-Location Redirect URLs

Each location can have a different post-login redirect URL. Go to Location Settings → Post-Login Redirect. Set this to a page relevant to the specific venue: the venue's own website, a location-specific menu, an upcoming events page, or a Google Maps listing for directions. Do not redirect all locations to your main homepage — it's a missed opportunity to serve location-relevant content to a guest who is physically at that venue right now.

Step 7: Franchise Model — Per-Franchisee Data Access

If you operate a franchise model where individual franchisees should only see data for their own location, use VoqadoWiFi's Team Access Controls (Settings → Team → + Invite Team Member). When inviting a team member, set their Location Access to a specific subset of locations. A franchisee invited with access to only "Location: Manchester" can view analytics, run campaigns, and manage the portal for that location only. They cannot see guest data from other locations. The franchise owner (account admin) retains full access across all locations.

Step 8: Centralised Campaigns with Location Variables

For chain-wide campaigns where you want to send from a single campaign build but include location-specific content, use VoqadoWiFi's Dynamic Content Blocks. In the email editor, add a Dynamic Block with the variable '{{guest.location.name}}' to personalise content by location. Example: "Visit us at {{guest.location.address}} for our [promotion]." This inserts the guest's home location address automatically. Available location variables include: '{{guest.location.name}}', '{{guest.location.address}}', '{{guest.location.phone}}', '{{guest.location.website}}'.

Step 9: Manage Seasonal Portal Variants

Each location supports up to 5 saved portal variants. Use this to pre-build seasonal portals (Christmas, summer, Valentine's Day) and switch between them with one click. Go to Portal Builder → [Location] → Saved Variants → + New Variant. Build your seasonal version. When ready to launch, go to Saved Variants → [Seasonal Variant] → Set as Live. When the season ends, revert to your standard variant. This keeps your portal feeling fresh year-round without rebuilding from scratch each time.

Step 10: API Access for Enterprise Integration

On the Enterprise plan, VoqadoWiFi exposes a REST API for programmatic access to guest data, campaign management, and analytics. Generate your API key in Settings → Developer → API Keys → + New Key. Set scopes: 'guests:read', 'campaigns:write', 'analytics:read'. The API documentation is at docs.voqadowifi.com/api. Common enterprise use cases: syncing guest data to your POS or EPOS system, triggering campaigns from a reservation system event, pulling analytics data into a BI tool like Tableau or Power BI, or building a custom dashboard for your head office team.

Step 11: Monthly Multi-Location Review Workflow

Establish a monthly cadence: on the first Monday of each month, open the Multi-Location View in Analytics. Review each location's return rate vs the prior month. Flag any location that has declined by more than 5 percentage points. For flagged locations, drill into their guest data to identify whether the issue is acquisition (fewer new logins), retention (lower return rate), or list health (high unsubscribe rate). Assign action owners per location — a franchise model where each operator is responsible for their own location's metrics creates accountability and drives consistent improvement across the portfolio.