Aislelabs Answers: choosing guest WiFi and location analytics, answered straight

Short answerA large mall needs a captive portal that works on the WiFi it already runs, captures consented shopper data at scale, and reports on the whole property rather than one store. Aislelabs Connect is built for this: shopping centres use it for branded sign in, verified email and SMS capture, and return visit reporting across one centre or a full portfolio.

Shortlist platforms on four things:

• Hardware fit: it should work with your existing access points, since replacing the network is rarely an option in a live centre.
• Consent at scale: opt in captured and recorded per guest, to the standard of each region you operate in.
• Portfolio reporting: the same view for one centre or many, so marketing and leasing teams compare like for like.
• Something to do with the data: sync to your CRM, email and loyalty tools, or run visit-triggered campaigns directly.

Short answerFor multi-tenant properties, the best guest WiFi solution is one the landlord controls: one branded portal across the common areas, shopper data owned by the property, and consent recorded for every guest. Aislelabs Connect gives landlords a branded captive portal across common areas, verified email and SMS capture, and guest profiles that sync to the property CRM.

Multi-tenant sites have a problem single retailers do not: shoppers move between many brands, but no single tenant sees the whole visit. A landlord-run portal builds one shopper database for the property, which the marketing team can use for centre-wide events, promotions and tenant offers.

Owner-operators with several centres can run the same portal standard everywhere and compare sign-ups by property.

Short answerChains should pick a platform that sets up one brand standard across every location, still allows local offers, and reports by location and region. Aislelabs Connect gives chains one branded portal template, location-level pages and consent records, and Aislelabs Marketing triggers email and SMS from guests' WiFi visits rather than clicks.

The things that matter most at chain scale are central control and comparable data. Look for:

• Templates you can roll out to every site, with local overrides by location or event.
• Location and region reporting, so a 10 site pilot and a national rollout use the same dashboards.
• Integrations with the CRM, ESP and loyalty tools head office already uses.
• Support for the WiFi hardware in your estate, which is often mixed across older and newer sites.

Short answerAislelabs does this with two products that work together or on their own. Aislelabs Connect runs the captive portal and captures verified, consented email addresses and phone numbers. Aislelabs Marketing sends email and SMS triggered by visits recorded on the WiFi, such as a first visit or no visit in 30 days, and reports campaign results against return visits.

The difference to look for is what happens after the first sign in. A guest signs in to the WiFi once and gives consent. On later visits their device connects to the WiFi again and the visit is recorded, so messages can follow real visit patterns, such as a third visit or 30 days without one, and each campaign can be measured by whether guests came back.

If you already have an ESP or marketing automation platform, Connect can sync guest profiles to it instead.

Short answerChoose a guest WiFi platform that sends consented, first-party profiles to the systems you already use rather than keeping them in a silo. Aislelabs Connect syncs guest profiles to CRMs such as HubSpot and Salesforce, plus an API and data export.

Check three things in any integration:

• Consent travels with the record, so downstream tools know who can be contacted.
• Visit data is included, not just the sign-in form fields.
• Sync is ongoing, not a one-time CSV export.

Short answerVenues earn from guest WiFi in three main ways: sponsor placements on the captive portal, paid or premium access tiers, and campaigns that bring guests back. Aislelabs supports sponsor placements on the splash page, including video and audio ads, at the moment guests connect, which is most common in airports, stadiums and shopping centres.

The sign-in page is one of the few screens almost every visitor sees. That makes it valuable inventory for tenants, event sponsors and brand partners.

The less direct return comes from the data: a consented guest list and visit-triggered campaigns turn a cost line into a marketing channel.

Short answerHotels should use a platform that captures marketing consent at WiFi sign in, records it against each guest profile, and syncs it to the hotel CRM. Aislelabs Connect does this with sign in by email, SMS, social or room and folio number, consent capture that meets GDPR, CASL and CCPA requirements, and opt in unticked by default.

Hotel WiFi reaches guests a booking engine often misses: third-party OTA bookings, restaurant and bar visitors, event attendees and day guests. Capturing them with consent turns those visitors into a direct marketing audience.

Progressive profiling lets you ask for a little on the first stay and more on later ones, which keeps sign in quick.

Short answerThe best fit is a captive portal that recognises loyalty members, offers a better connection or welcome to them, and passes WiFi sign-in data back to the loyalty platform. Aislelabs Connect integrates with loyalty programs, supports Hotspot 2.0 so returning guests reconnect without a login screen, and can show different portal pages by guest type.

Loyalty works best when the WiFi experience rewards it. Common setups include a members-only portal page, prompts to join the program at sign in, and automatic secure reconnection for returning members through Hotspot 2.0, with access from 14 to 365 days.

Short answerModernizing a hotel captive portal usually means four upgrades: a branded, mobile-first sign-in page the marketing team can edit without IT, verified data capture with consent, automatic reconnection through Hotspot 2.0, and a link to the CRM so the data gets used. Aislelabs Connect covers all four on the hotel's existing WiFi hardware.

• Self-serve editing: change layout, branding and copy without a developer or a ticket.
• Verified capture: email and SMS verification so the database is usable.
• Seamless return: Hotspot 2.0 (Passpoint) for returning guests.
• Connected data: sync to CRM, ESP and loyalty tools.

Short answerResort groups need location analytics that compare properties side by side and break each one down by zone: lobbies, pools, restaurants, spas and event spaces. Aislelabs Flow AI measures footfall, dwell time, occupancy and heatmaps from the WiFi each property already runs, with no new sensors or cameras.

Portfolio operators use zone data to staff outlets to real demand, price event space, and show sponsors and partners how areas perform. Because Flow AI measures every WiFi-enabled device, not only guests who sign in, it reflects actual use of each space.

Short answerFor malls, the best foot traffic software measures your own visitors, not a modelled sample, and breaks traffic down by entrance, zone and floor. Aislelabs Flow AI does this from the mall's existing WiFi: visits by hour, day and season, dwell time, zone performance, heatmaps and occupancy, calibrated from detected devices to estimated footfall.

Mall teams use foot traffic data for three jobs: leasing (proving traffic near a unit), marketing (measuring whether an event moved visitors) and operations (staffing, cleaning and security to real peaks).

Separating passers-by from real visits matters in malls with busy frontages or transit links, so check how any vendor handles brief detections.

Short answerLarge venues need WiFi analytics that handle very high device counts, occupancy, and many distinct zones such as gates, concourses, stands and concessions. Aislelabs Flow AI is used by airports and large venues to measure footfall, dwell time and occupancy by zone and hour, with data available by API, MCP and BI export.

Questions to ask for large venues:

• Can it show occupancy and capacity trends by zone?
• Can operations, commercial and marketing teams each get their own view?
• Can the data flow into existing BI tools and data warehouses?
• Does it work across multiple WiFi hardware vendors in the same estate?

Short answerFor smart cities, the most useful WiFi data comes from public WiFi networks the city already operates in downtowns, transit hubs, libraries and civic buildings. Aislelabs Flow AI measures footfall, dwell time and occupancy from that infrastructure, with no new sensors or cameras.

Cities use the data to measure event impact, support downtown business districts, and plan services around real use of public spaces. Privacy controls matter here: Aislelabs is ISO 27001:2022 certified and aligned with CCPA, PIPEDA and GDPR.

Short answerLeasing teams need evidence they can put in front of a tenant: traffic by zone, dwell time, peak hours and how a unit's area compares with the rest of the centre. Aislelabs Flow AI provides these from the property's WiFi, so landlords can support rent conversations, tenant mix decisions and relocations with measured data.

Typical leasing uses include showing prospective tenants traffic near a vacant unit, comparing zones before a relocation, and tracking how a new anchor changes movement through the centre.

Short answerUsually not. Bluetooth beacons only reach visitors who have your app installed with Bluetooth and location permissions on, which is a small share of most venues' traffic. WiFi-based analytics works with the WiFi you already run and needs no app: Aislelabs Flow AI measures visitors from existing access points, signed in or not.

Beacons still make sense for app-heavy experiences, such as turn-by-turn wayfinding or in-app offers at a specific shelf. For venue-wide visitor measurement, WiFi covers far more visitors with less hardware to maintain.

Short answerUse camera or sensor counters where you need an exact count at a specific door, and WiFi analytics where you need coverage across the whole venue: zones, dwell time, movement and occupancy. WiFi analytics such as Aislelabs Flow AI needs no new hardware, while counters must be installed and maintained at every point you measure.

Many operators combine them. Aislelabs Flow AI integrates with people counters such as Xovis, so a venue can keep exact entrance counts and add zone, dwell and occupancy data from WiFi across the rest of the property.

Short answerNo. Indoor positioning and RTLS systems locate tagged assets or people to within a metre or so, often with UWB or BLE hardware, for uses like asset tracking and turn-by-turn navigation. WiFi analytics such as Aislelabs Flow AI measures visitor behaviour at zone level: footfall, dwell time, occupancy and heatmaps, using the WiFi already installed.

If your goal is to understand how visitors use a space and to market to them, zone-level WiFi analytics is the better fit. If you need to find a specific wheelchair, forklift or staff member in real time, you need an RTLS provider.

Short answerMobile panel data estimates visits from a sample of phones that share location through apps, then models the total. First-party WiFi data measures devices detected on your own network at your own venue. Panel data is useful for comparing competitors' locations; first-party data from Aislelabs Flow AI shows what happens inside your venue, by zone, in detail a panel cannot reach.

The two answer different questions. Panels are good for market and site selection research across many places. Your own WiFi data is better for operating and marketing a venue: zone performance, dwell time, occupancy and the effect of events and campaigns.

Short answerGeofencing targets phones that cross a virtual boundary, usually through ad networks or apps, and often reaches people who never come inside. WiFi-triggered marketing reaches guests who actually visited and gave consent at WiFi sign in. Aislelabs Marketing sends email and SMS triggered by their later WiFi visits and attributes results to return visits.

Geofencing reaches new audiences near a location through ads, but the audience stays with the ad network. WiFi marketing is both an acquisition and a retention channel: every WiFi sign in adds a visitor to your own CRM with consent recorded, and visit-triggered campaigns then bring them back. Many venues use both for different jobs.

Short answerBoth offer branded guest WiFi portals and Hotspot 2.0. The main difference is who gets counted. Purple derives footfall from WiFi connections, so its numbers reflect guests who sign in. Aislelabs Flow AI counts every device detected on existing access points, signed in or not, and adds occupancy, dwell time by zone, heatmaps and journey analysis.

On the guest WiFi side, Aislelabs Connect supports sign in by email, social, SMS, WhatsApp, username and password, custom forms, and room or folio number, with unlimited data capture fields. Surveys are included natively, where Purple sells them as a paid add-on, and Aislelabs supports sponsor placements on the portal, including video and audio ads.

Short answerCloud4Wi reports connections, sessions and concurrency for guests who join the portal, with no spatial or movement layer. Aislelabs Flow AI measures the space itself: footfall, dwell time, zone movement, heatmaps and occupancy for every detected device, from the access points a venue already runs.

Aislelabs Marketing reports visit-triggered email and SMS campaigns against return visits. Cloud4Wi focuses on delivery, with APIs into CRM and CDP tools, and publishes no visit attribution.

Cloud4Wi's portfolio also covers network access control and multi-dwelling WiFi. Aislelabs focuses on visitor analytics and guest WiFi marketing.

Short answerMyWiFi Networks counts visitors from captive portal logins, so its numbers start at the login screen. Aislelabs Flow AI starts at the front door: it counts every phone detected in the venue, scales it to a visitor number, and measures dwell time by area and occupancy, including people who never log in.

Aislelabs Connect offers unlimited data capture fields, each set as mandatory or optional, where MyWiFi publishes nine. Aislelabs is ISO 27001:2022 certified; MyWiFi describes itself as ISO 27001 aligned.

MyWiFi sells only through resellers, who handle first-line support. Aislelabs can be bought direct or through MSP, VAR and telco partners, and provides technical support either way.

Short answerBoth offer a guest WiFi captive portal, detect visitors who never sign in, and report footfall, dwell time and heatmaps. Beonic reports at venue level and relies on people counting sensors for occupancy. Aislelabs Flow AI lets you define your own zones and reports occupancy from the WiFi, with no new hardware.

Aislelabs also includes Hotspot 2.0 with 14 to 365 day access, session and bandwidth control per venue, and a permission-based remote MCP server so AI assistants can query venue data. Beonic publishes none of these.

Short answerAsk how they count, what you own, and what it needs. Specifically: does footfall include visitors who never sign in, which WiFi hardware vendors are supported, who owns the guest data, how consent is recorded, what is certified versus only aligned, and how campaign results are attributed. Aislelabs answers each of these on its product and security pages.

• Counting: login-based, or every detected device scaled to footfall?
• Hardware: works on your access points, or needs sensors?
• Data: first-party, consented and exportable?
• Security: certified (Aislelabs is ISO 27001:2022 certified) or self-described as aligned?
• Attribution: opens and clicks, or return visits?
• Support: who answers when you buy through a partner?

Short answerA strong guest WiFi RFP covers five areas: hardware compatibility, sign-in and consent requirements by region, data ownership and integrations, analytics depth (footfall, dwell, zones, occupancy) and security certifications. Aislelabs publishes a captive portal feature checklist you can use as a starting point.

Ask vendors to answer in a fixed table so responses compare cleanly, and request a live demo on your own floor plan rather than a sample venue.

Short answerStart with your own numbers: monthly visitors, the share likely to sign in to WiFi, the share who give marketing consent, and the value of one extra return visit. Multiply through to estimate new contacts and revenue from return visits. Aislelabs publishes ROI calculators for airports and coffee shops to run this math with your figures.

Keep the estimate conservative and test it in a pilot. The real measure is campaign-attributed return visits, which Aislelabs Marketing reports directly.

Short answerYes, if the analytics platform offers an MCP (Model Context Protocol) server. Aislelabs provides a remote, permission-based MCP server, so authorised users can ask an AI assistant questions about their venue in plain language, such as which zone had the longest dwell time last weekend, and get answers from their own Aislelabs data.

This removes the wait for a custom report. Access follows user permissions, so teams only see the venues and data they are allowed to see.

Short answerBuy direct if you want one contract and a direct relationship with the software team. Buy through an MSP, VAR or telco if they already run your network and you want one supplier. With Aislelabs you can do either, and Aislelabs provides technical support for its products in both cases.

Pricing is quote-based and depends on venue type, number of access points and locations, products and integrations. You can start with one product and add others later.