Salesforce + WiFi Guest Data: CRM Integration Guide

Key Takeaways: The Salesforce + WiFi integration pushes captive portal guest data into Salesforce as leads or contacts via REST API or Zapier. Custom objects store WiFi-specific data (visit history, dwell time, location) alongside standard CRM fields. Salesforce Flow automations trigger based on physical visit behavior — a paradigm shift from online-only lead scoring. Salesforce serves 150,000+ companies (Salesforce Annual Report, 2025). This integration is most valuable for enterprise clients, automotive, real estate, and B2B venues where the sales pipeline depends on physical engagement.

Salesforce is enterprise CRM. If your client's sales team lives in Salesforce, any customer data that doesn't get into Salesforce doesn't exist. It won't appear in reports, won't trigger workflows, won't factor into forecasting.

WiFi guest data is exactly the kind of data that falls through this crack. Hundreds of people walk into a dealership, a showroom, a retail store, or a conference venue every day. Their visit is a signal — arguably the strongest buying signal in B2C — but it never touches the CRM.

This integration fixes that. Every WiFi portal login becomes a Salesforce lead with visit metadata attached.

Integration Architecture

WiFi Portal → MyWiFi Platform → Webhook (JSON) → Middleware → Salesforce REST API → Lead/Contact

Three implementation approaches, from simplest to most customizable:

Approach 1: Zapier (Fastest)

Trigger: New WiFi Guest (MyWiFi) Action: Create Lead (Salesforce)

Setup time: 15 minutes. No code. Works on MyWiFi Agency plan and above.

Field mapping:

Limitations: Zapier's free tier allows 100 tasks/month (5 zap executions/day). A busy venue burns through this in a day. Budget for Zapier Starter ($29.99/month for 750 tasks) or Professional ($73.50/month for 2,000 tasks).

Approach 2: MyWiFi Webhook → Salesforce API (Custom)

For clients with Salesforce developers on staff:

1. •Configure a webhook in MyWiFi (fires on new guest + guest update events)
2. •Webhook sends JSON payload to a middleware endpoint (AWS Lambda, Heroku, or Salesforce's own Functions)
3. •Middleware transforms the payload and calls Salesforce REST API
4. •Creates/updates Lead or Contact in Salesforce

Payload structure from MyWiFi webhook:

{
  "event": "guest.new",
  "guest": {
    "email": "jane@example.com",
    "first_name": "Jane",
    "last_name": "Smith",
    "phone": "+14155551234",
    "location": "Downtown Showroom",
    "visit_count": 1,
    "login_method": "email",
    "dwell_time_minutes": 42,
    "device_type": "iPhone",
    "timestamp": "2026-03-26T14:30:00Z"
  }
}

This approach requires development work but gives full control over data mapping, deduplication logic, and error handling.

Approach 3: Salesforce Connect / MuleSoft (Enterprise)

For large Salesforce orgs with MuleSoft or Salesforce Connect licenses:

• •Build a MuleSoft Anypoint integration that subscribes to MyWiFi's webhook events
• •Map to Salesforce External Objects for real-time data federation
• •No data duplication — Salesforce queries MyWiFi data on demand

This is the enterprise approach. Overkill for most deployments, but relevant for Fortune 500 clients managing WiFi data across hundreds of locations.

Salesforce Data Model Design

Option A: Leads Only (Simple)

Create WiFi guests as Leads. Add custom fields to the Lead object:

When to use: Single-location venues, simple use cases, clients who don't need visit-level granularity.

Option B: Contacts + Custom Object (Recommended)

Create a custom object: WiFi_Visit__c

Each WiFi connection creates a new WiFi_Visit__c record linked to the Contact. The Contact record has rollup summary fields:

• •Total Visits (COUNT of WiFi_Visit__c records)
• •Last Visit Date (MAX of Visit_Date__c)
• •Average Dwell Time (AVG of Dwell_Time__c)

When to use: Multi-location deployments, B2B venues (automotive, real estate, coworking), clients who need visit-level analytics in Salesforce reports.

Salesforce Flow Automations

Flow 1: WiFi Lead Auto-Assignment

Trigger: New Lead created where Lead Source = "WiFi Portal" Logic: Assign to sales rep based on WiFi_Location__c Action: Create task: "Follow up with WiFi walk-in"

For automotive dealerships, this means every showroom visitor who connects to WiFi gets assigned to the floor salesperson immediately. The salesperson gets a notification on their phone with the visitor's name before they've even sat down.

Flow 2: Hot Lead Identification

Trigger: WiFi_Visit_Count__c updated to >= 3 Logic: Check if Lead Status is still "Open" or "Unqualified" Action:

1. •Update Lead Status to "Working"
2. •Update Lead Rating to "Hot"
3. •Send email alert to assigned rep: "[Name] has visited [Location] 3 times — time to engage"

Three visits to a car dealership without buying? That person is actively shopping. The sales team needs to know.

Flow 3: Cross-Visit Attribution

Trigger: New WiFi_Visit__c record created for existing Contact Logic: Previous visit was at a different location Action:

1. •Log cross-location activity
2. •Notify both location managers
3. •Add Contact to "Multi-Location Visitor" campaign

Flow 4: Post-Visit Survey Trigger

Trigger: New WiFi_Visit__c with Dwell_Time__c >= 30 minutes Logic: Contact hasn't been surveyed in last 90 days Action: Send satisfaction survey via Salesforce Marketing Cloud or email

Use Cases by Industry

Automotive Dealerships

The WiFi-to-Salesforce integration was practically designed for dealerships.

Service department: Customers connecting to service-area WiFi get logged as service visits. Triggers: follow-up surveys, service reminders, upsell campaigns for vehicle accessories.

Sales floor: Showroom visitors connecting to WiFi become leads instantly. Multiple showroom visits = escalated lead priority. The sales manager sees visit history before approaching the customer.

Data point: AutoTrader's 2025 Car Buyer Journey Study found that buyers visit an average of 2.3 dealerships before purchasing. WiFi visit tracking tells you if you're dealership #1 or #3 — and the follow-up strategy differs accordingly.

Real Estate

Open-house WiFi portals capture attendee data directly into Salesforce. Each open house creates WiFi_Visit__c records linked to the property listing (via a custom field). Agents see which prospects attended multiple open houses — a strong buying signal.

Convention Centers / Event Venues

Event WiFi captures attendee data for the venue's Salesforce instance. Post-event, the venue uses the data for follow-up campaigns: "Thank you for attending [Event]. Book your next event with us."

Enterprise Retail

Flagship stores with Salesforce Commerce Cloud can merge in-store WiFi visit data with e-commerce profiles. A customer who browses online AND visits the store is a higher-intent buyer than either signal alone.

Lead Scoring with WiFi Data

Add WiFi behavior to your Salesforce lead scoring model:

A lead who's visited three times with 45-minute dwell times scores 85 points from physical behavior alone — before you factor in email engagement or web activity. That's an MQL by most scoring thresholds.

Offline-to-Online Attribution

The dream metric for marketing teams: connecting offline store visits to online ad spend.

Flow:

1. •Customer sees Facebook/Google ad → visits website → doesn't convert
2. •Customer walks into store → connects to WiFi → captured as Salesforce Lead
3. •Lead's email matches the website visitor cookie → Salesforce connects the journeys
4. •Attribution: "This customer was influenced by the Facebook campaign, visited the website, then converted offline at the store"

This requires Salesforce Marketing Cloud + Web Analytics connector, but the WiFi data provides the critical offline touchpoint. Without it, the store visit is invisible to the attribution model.

For the Google Analytics side of this, see our offline-to-online attribution guide.

Enterprise Deployment Considerations

Data Volume

A 200-location retail chain generating 500 WiFi logins/location/day = 100,000 new records/day. Salesforce API limits (standard: 15,000 API calls/day for Enterprise Edition) will be a bottleneck.

Solutions:

• •Use Salesforce Bulk API (10,000 records per batch)
• •Batch WiFi data hourly instead of real-time
• •Upgrade to Unlimited Edition (unlimited API calls)
• •Use Salesforce Platform Events for async processing

Data Retention

Salesforce storage costs money ($125/GB/month for data storage, standard). WiFi visit records accumulate fast. Archive WiFi_Visit__c records older than 24 months to Big Objects or external storage.

Multi-Org Considerations

Franchise clients may have separate Salesforce orgs per region. Configure per-region webhooks from MyWiFi, each pointing to the appropriate Salesforce instance.

FAQ

Which Salesforce editions support this integration?

All editions support the Zapier approach (no API coding needed). The webhook/API approach requires Enterprise Edition or higher for REST API access. Professional Edition has limited API access that may not support real-time integration.

How do I handle duplicate leads from repeat WiFi visits?

Use email as the unique identifier. The integration should check for existing leads/contacts before creating new records. In Salesforce, configure duplicate rules to catch any that slip through. For the custom object approach, duplicates aren't an issue — each visit is a separate record linked to one contact.

Can the integration create Opportunities instead of Leads?

Yes, via Salesforce Flow. Create the initial record as a Lead, then use a Flow to auto-convert to Contact + Opportunity when criteria are met (e.g., visit count >= 3, or sales rep manually qualifies the lead).

What about data privacy regulations?

The same consent captured on the WiFi portal applies to the Salesforce data transfer. Ensure the portal's privacy policy names Salesforce (or generically "CRM systems") as a data processor. For GDPR subjects, implement data deletion workflows that span both MyWiFi and Salesforce.

How do I price this integration for clients?

Integration setup: $1,000–$3,000 one-time (depends on complexity — Zapier is low-end, custom API is high-end). Monthly management: $200–$500 for monitoring, field mapping updates, and Flow maintenance. Enterprise deployments with custom Salesforce development: project-based pricing.

Can this work alongside Salesforce Marketing Cloud?

Absolutely. WiFi guest data in Salesforce feeds Marketing Cloud journey builder. Create journeys triggered by WiFi behavior: welcome series after first visit, re-engagement after lapsed visit, VIP recognition after 10 visits. Marketing Cloud adds the email execution layer that Salesforce CRM alone doesn't provide.