HubSpot CRM + WiFi Marketing: Lead Capture to Pipeline

Key Takeaways: The HubSpot + WiFi integration creates CRM contacts automatically from captive portal logins, enriches profiles with physical visit data (frequency, dwell time, location), and triggers HubSpot workflows based on real-world customer behavior. This bridges the gap between online CRM and offline foot traffic. HubSpot reports 228,000+ customers across 135 countries (HubSpot Annual Report, 2025). The integration works via MyWiFi's native HubSpot connector or through Zapier for advanced workflows. Available on MSP plans and above.

HubSpot is the CRM that marketing agencies already use. If your agency clients manage their own lead pipelines in HubSpot, or if their clients do, the WiFi-to-HubSpot integration closes a gap that's been bugging them: offline customer data.

HubSpot tracks everything that happens online — website visits, email opens, form submissions, chatbot conversations. What it can't see: the 300 people who walked into your client's store today. Those people don't exist in HubSpot until someone manually enters them. Which nobody does.

WiFi login makes them appear. Automatically. With behavioral data attached.

What the Integration Does

Every WiFi portal completion creates or updates a HubSpot contact:

The custom properties need to be created in HubSpot before enabling the integration. They live under a custom property group called "WiFi Marketing Data."

Beyond contact creation, the integration can:

• •Create timeline events — each WiFi login appears as a timeline entry on the contact record, showing when and where the person visited
• •Apply lifecycle stages — new WiFi contacts default to "Lead" or "Marketing Qualified Lead" depending on your configuration
• •Trigger workflows — HubSpot workflows fire based on WiFi-specific properties (visit count changes, lapsed visit triggers, new location visits)

Setup: Native Integration

Prerequisites

• •MyWiFi account on MSP plan ($999/month) — HubSpot integration requires API access
• •HubSpot account (free CRM works, Marketing Hub recommended for workflows)
• •Admin access to both platforms

Step-by-Step Configuration

Step 1: Create Custom Properties in HubSpot

In HubSpot, go to Settings > Properties > Create Property Group: "WiFi Data"

Create each custom property listed in the table above. Set field types appropriately (text, number, date). This takes about 15 minutes.

Step 2: Generate HubSpot API Key

In HubSpot: Settings > Integrations > Private Apps > Create Private App

• •Name: "MyWiFi Integration"
• •Scopes: crm.objects.contacts.write, crm.objects.contacts.read, timeline
• •Copy the access token

Step 3: Configure MyWiFi Integration

In MyWiFi dashboard: Integrations > CRM > HubSpot

• •Paste the HubSpot access token
• •Map MyWiFi fields to HubSpot properties
• •Set default lifecycle stage for new contacts
• •Choose sync direction: MyWiFi → HubSpot (recommended) or bidirectional

Step 4: Enable and Test

Submit a test portal login. Verify:

• •Contact appears in HubSpot within 60 seconds
• •All mapped fields are populated
• •Timeline event shows the WiFi login
• •Lifecycle stage is correct

Zapier Alternative

For resellers on Agency plans ($499/month) who don't have the native HubSpot integration, Zapier bridges the gap:

Zap 1: New WiFi Guest → Create HubSpot Contact

• •Trigger: New Guest (MyWiFi)
• •Action: Create or Update Contact (HubSpot)
• •Field mapping: same as native integration

Zap 2: WiFi Disconnect → Add Timeline Event

• •Trigger: Guest Disconnect (MyWiFi)
• •Action: Create Engagement (HubSpot)
• •Content: "WiFi visit at [Location] — Duration: [X] minutes"

Zap 3: Visit Count Threshold → Update Lifecycle Stage

• •Trigger: Guest Update (MyWiFi) with filter (visit_count >= 5)
• •Action: Update Contact Property (HubSpot) — Lifecycle Stage: "Customer"

HubSpot Workflows Powered by WiFi Data

The real value isn't contact creation — HubSpot can already store contacts. The value is workflows triggered by physical-world behavior.

Workflow 1: New WiFi Guest Welcome

Trigger: Contact created with property "WiFi Visit Count" = 1 Actions:

1. •Send welcome email (HubSpot template)
2. •Wait 3 days
3. •If contact hasn't opened email → send SMS follow-up
4. •Wait 7 days
5. •Send second email with venue highlights / menu / product showcase
6. •Add to "WiFi Leads" active list

Workflow 2: Repeat Visitor → Sales Opportunity

Trigger: "WiFi Visit Count" updated to 3+ Actions:

1. •Update lifecycle stage to "Marketing Qualified Lead"
2. •Create deal in pipeline: "WiFi Repeat Visitor — [Venue Name]"
3. •Assign to account manager
4. •Send internal notification: "Repeat visitor [Name] has visited 3 times — follow up"

This workflow is gold for B2B venues (coworking spaces, event venues, conference centers). A person who's visited a coworking space 3 times is a hot lead for a membership sale.

Workflow 3: VIP Recognition

Trigger: "WiFi Visit Count" updated to 10+ Actions:

1. •Update lifecycle stage to "Customer"
2. •Add tag: "VIP-WiFi"
3. •Send personalized VIP email (handwritten-style, from the owner)
4. •Add to "VIP" segment in Mailchimp (via Zapier)

Workflow 4: Lapsed Customer Re-Engagement

Trigger: "Last WiFi Visit" is more than 30 days ago AND "WiFi Visit Count" >= 3 Actions:

1. •Send win-back email with incentive
2. •Wait 7 days
3. •If no new WiFi visit → send second email
4. •Wait 14 days
5. •If still no visit → add to "Lapsed" list for manual outreach or ad retargeting

Workflow 5: Cross-Location Notification

Trigger: "Venue Location" property updates with a new value (guest visited a different location) Actions:

1. •Internal notification to account manager
2. •Send cross-promo email: "Great to see you at [New Location]! Did you know we also have [promotion] at [Original Location]?"

Use Cases by Vertical

Coworking / Shared Office

WiFi visit data feeds the membership sales pipeline. 1st visit = lead. 3rd visit = MQL. 5th visit = sales call. The pipeline mirrors physical engagement.

Real Estate (Model Homes / Open Houses)

Every open-house WiFi login creates a lead in HubSpot with the property address as the location. Agents follow up based on visit data — someone who visited two open houses is a more serious buyer.

Automotive Dealerships

Service department WiFi captures owner data. Sales department WiFi captures prospect data. Both feed into HubSpot with different pipeline assignments. A service customer who visits 3x is a retention target. A showroom visitor who returns is a hot prospect.

Healthcare / Clinics

Patient check-in via WiFi creates a contact in HubSpot (with appropriate HIPAA considerations — see compliance note below). Visit frequency data helps with appointment reminder workflows and patient retention campaigns.

Franchise / Multi-Location Retail

Corporate-level HubSpot instance receives WiFi data from all locations. Cross-location visitor identification, portfolio-wide analytics, and centralized campaign management. See our franchise WiFi guide for the full architecture.

Data Enrichment Strategy

WiFi data is one input. Combine it with other HubSpot data sources for a complete customer profile:

A contact in HubSpot with both WiFi visit data AND website tracking has a 360-degree profile: online + offline behavior. This composite view enables hyper-targeted campaigns that neither data source could support alone.

Compliance Considerations

GDPR (EU/UK)

• •WiFi portal consent must explicitly mention "CRM data processing" or "customer relationship management"
• •HubSpot acts as a data processor; ensure a Data Processing Agreement (DPA) is in place (HubSpot offers a standard DPA)
• •Right to erasure: deleting a contact in HubSpot should trigger deletion in MyWiFi (and vice versa) — configure this process manually or via Zapier

HIPAA (Healthcare)

• •Standard HubSpot is NOT HIPAA-compliant
• •If using WiFi + HubSpot in healthcare settings, do NOT sync Protected Health Information (PHI)
• •Contact info (name, email, phone) is generally acceptable; visit data to a specific clinic may constitute PHI
• •Consult a healthcare compliance attorney before deploying

CCPA (California)

• •California consumers can request data deletion — ensure your process covers both MyWiFi and HubSpot
• •Include a "Do Not Sell My Personal Information" link on WiFi portals serving California locations

Reporting: WiFi Metrics in HubSpot

Build custom reports in HubSpot using WiFi properties:

These reports appear in HubSpot's dashboard alongside all other marketing data. Clients see WiFi performance integrated with their broader marketing metrics — not siloed in a separate WiFi dashboard.

Pricing Impact

Source: HubSpot pricing page (March 2026).

Most WiFi marketing use cases require Marketing Hub Professional for advanced workflow triggers based on custom properties. The free CRM works for basic contact storage but lacks the automation capabilities that make the integration valuable.

FAQ

Which MyWiFi plan supports the HubSpot integration?

The native HubSpot integration requires the MSP plan ($999/month) which includes API access and webhook capabilities. The Agency plan ($499/month) can connect to HubSpot via Zapier as an alternative.

Can I use HubSpot's free CRM with this integration?

Yes, for contact creation and basic property mapping. But the free CRM limits workflows to simple triggers. To get the full benefit — multi-step workflows, custom reporting, lifecycle stage automation — you need Marketing Hub Professional.

How does the integration handle duplicate contacts?

The integration uses email as the primary dedup key. If a WiFi guest's email already exists in HubSpot, the integration updates the existing contact (incrementing visit count, updating last visit date) rather than creating a duplicate.

Can I integrate WiFi data with HubSpot's deal pipeline?

Yes. Use HubSpot workflows to create deals automatically when a contact meets criteria (e.g., visit count >= 3). Assign the deal to a pipeline stage and an owner. This is particularly powerful for B2B verticals like coworking, events, and automotive.

What happens if the HubSpot API key expires?

The integration will stop syncing. MyWiFi queues unsynced contacts and retries when the connection is restored. No data is lost — just delayed. Monitor integration health in the MyWiFi dashboard and set up alerts for sync failures.

Can I sync HubSpot data BACK to MyWiFi?

The primary flow is MyWiFi → HubSpot. Bidirectional sync is possible via Zapier (HubSpot trigger → MyWiFi action) but requires careful configuration to avoid sync loops. Most resellers keep it one-directional.