Overview
This guide explains how to configure a guest Wi-Fi marketing portal with email capture on Cisco Meraki using SocialSign.in Go. You have two options: automatic setup using the Meraki Setup Wizard, or manual configuration in the Meraki dashboard.
Automatic setup is recommended. The wizard applies the required Meraki settings, stores the authorized Meraki connection securely, and maps the selected Meraki organization, network, and SSID to the correct SocialSign.in location for ongoing Guest Experience Assurance.
What You'll Need
- Access to your Cisco Meraki dashboard
- A Meraki Dashboard API key with access to the organization and network you want to configure
- A SocialSign.in Go account (sign up here)
Option A: Automatic Setup (Recommended)
SocialSign.in Go includes a built-in Meraki Setup Wizard that configures your selected Meraki SSID in just a few clicks. The wizard is designed to reduce manual dashboard work and make sure the Meraki network is mapped correctly for ongoing monitoring and support.
How It Works
- From your SocialSign.in Go account, open the Meraki Setup Wizard for your location.
- Enter your Meraki API key. In Meraki, API keys are managed from your user profile. If API access is not available, an organization admin may need to enable API access under Organization → Settings.
- Select the Meraki organization and wireless network for the location.
- Choose whether to configure an existing active SSID or use an available Unconfigured SSID slot and give it a new guest network name.
- Review the selection and click Apply Configuration.
The wizard configures the selected SSID for SocialSign.in guest access, including the splash page mode, RADIUS authentication, walled garden access, custom splash page URL, captive portal behavior, and required guest access settings.
What the Wizard Configures
- Enables the selected SSID, when needed
- Sets association/authentication mode to open guest access
- Sets the splash page mode to Password-protected with custom RADIUS
- Adds the SocialSign.in RADIUS server and shared secret for the location
- Enables the walled garden and adds the required SocialSign.in domains
- Sets the custom hosted splash page URL for the location
- Blocks guest traffic until sign-on is complete
- Allows simultaneous logins from different devices
- Verifies that critical Meraki settings were applied successfully
Secure API Key Storage
After a successful setup, SocialSign.in stores the Meraki API key securely so the same authorized connection can be used for ongoing Guest Experience Assurance, configuration checks, reporting, and alerts. API keys are encrypted at rest. In the interface, saved Meraki connections may show only the last four characters of the key so your team can identify which connection is being used.
You can use an existing saved Meraki connection for future location setup, or replace the API key if your Meraki access changes.
Guest Experience Assurance
When the wizard completes, SocialSign.in saves the Meraki organization, network, SSID, location mapping, and expected configuration. This enables ongoing assurance checks that help identify whether the guest SSID is enabled, whether RADIUS and splash settings still match the expected setup, whether access points are online, and whether recent guest connection activity shows signs of an issue.
Option B: Manual Configuration
If you prefer to configure Meraki manually, follow the steps below. Your SocialSign.in account manager can provide the exact RADIUS details, splash page URL, and any deployment-specific values required for your location.
Step 1: Create or Select a Guest SSID
Navigate to Wireless → Configure → SSIDs and create or select the SSID for your guest network (for example, "Venue Name Guest Wi-Fi").
Pro tip: Adding a symbol to the beginning and end of the SSID name (for example, - Venue Guest WiFi - or #VenueGuestWiFi) may help it appear higher in the available networks list on guests' devices.
Step 2: Configure Access Control
Navigate to Wireless → Configure → Access Control and select your guest SSID from the dropdown. Apply the following settings:
- Association requirements: Open
- Splash page: Password-protected with custom RADIUS
- RADIUS server: Use the server host, port, and shared secret provided by SocialSign.in
- Captive portal strength: Block all access until sign-on is complete
- Walled garden: Enabled — add the SocialSign.in domains provided by your account manager so guests can reach the login page before authentication
Note: If Meraki shows an error that domains are not allowed to be whitelisted, contact Meraki support and ask them to enable domain whitelisting, or submit a case through Help → Cases.
Step 3: Configure the Splash Page
Navigate to Wireless → Configure → Splash Page and select your guest SSID. Set the custom splash page URL to the address provided by your SocialSign.in account manager.
Depending on your deployment, SocialSign.in may also need:
- AP tags
- MAC addresses for your wireless access points
- AP group names
Step 4: Activate & Test
We recommend keeping the SSID in Hidden mode under Wireless → Configure → SSID Availability until your SocialSign.in account manager confirms the experience is ready for deployment.
After configuration, test the guest flow from a phone or laptop by joining the SSID, confirming the SocialSign.in splash page loads, completing sign-on, and confirming internet access is granted.
What Happens Next?
Guests who connect to your Wi-Fi see a branded login page where they enter their email to get online. Their contact information flows directly into your CRM or marketing platform through SocialSign.in's 90+ integrations.
If your location was configured through the Meraki Setup Wizard, SocialSign.in can also monitor the mapped Meraki SSID for guest connection health and configuration drift.
Ready to get started? Sign up for SocialSign.in Go or contact us at support@socialsign.in.