Facebook Pixel + WiFi Data: Retargeting Your Walk-In Traffic
Key Takeaways: WiFi captive portal data synced with Facebook Pixel and Custom Audiences lets you retarget physical walk-in visitors with paid ads — bridging the offline-to-online attribution gap. A restaurant running WiFi-to-Facebook retargeting sees 2–3x higher ROAS compared to cold-audience campaigns (WordStream, 2025). MyWiFi fires the Facebook Pixel on portal load, captures email/phone for Custom Audience upload, and enables Lookalike expansion to reach similar profiles. This turns every WiFi login into a retargeting signal.
Every person who walks into your client's venue, connects to WiFi, and leaves has just raised their hand. They're a qualified prospect — they've physically visited the location, spent time there, and interacted with the brand.
And then they leave. Without retargeting, they're gone. Maybe they come back. Probably they don't remember the venue name by Thursday.
Facebook retargeting changes that equation. The WiFi captive portal captures identity (email, phone, or Facebook profile). That identity feeds into Facebook Custom Audiences. Now every walk-in visitor sees the client's ads in their Instagram and Facebook feed for the next 30, 60, or 90 days.
It's the most direct bridge between "someone walked into the store" and "someone saw our ad" that exists for local businesses. And it's one of the highest-value services you can offer as a reseller.
How the WiFi → Facebook Pipeline Works
Three integration points between MyWiFi and Facebook:
1. Facebook Pixel on the Captive Portal
MyWiFi supports embedding a Facebook Pixel on the splash page. When a guest loads the portal, the Pixel fires — tracking the "PageView" event. If the guest completes the portal (logs in), a "Lead" or custom event fires.
This puts the guest into the venue's Facebook Pixel audience automatically. No manual data export. No CSV uploads. The Pixel does the matching using Facebook's cross-device identity graph.
Setup: Add the Facebook Pixel ID (format: 15-digit number) in the portal's advanced settings. MyWiFi injects the Pixel script into the splash page HTML. Done.
Limitation: The captive portal browser on iOS (CNA — Captive Network Assistant) blocks some third-party scripts, including Pixel in some configurations. Standard browser-based portals work reliably. Test on actual iOS devices before deploying.
2. Facebook Custom Audiences (Email/Phone Upload)
Custom Audiences are more reliable than Pixel-based tracking because they use deterministic matching (email or phone → Facebook account) rather than cookie-based matching.
How it works:
- •WiFi portal captures guest email and/or phone number
- •Export guest contact list from MyWiFi (manual CSV or automated via Zapier)
- •Upload to Facebook Ads Manager as a Custom Audience
- •Facebook matches contacts to Facebook/Instagram profiles (typical match rate: 50–70%)
- •Target the Custom Audience with retargeting ads
Automated sync: Use Zapier with the "New WiFi Guest" trigger in MyWiFi → "Add to Custom Audience" action in Facebook. This keeps the audience current without manual exports.
Match rates by data type:
| Data Point | Facebook Match Rate |
|---|---|
| Email address | 55–65% |
| Phone number | 60–75% |
| Email + Phone | 70–80% |
| Email + Phone + Name | 75–85% |
Source: Facebook Business Help Center, Custom Audience match rate benchmarks (2025).
The more data points you capture on the WiFi portal, the higher the Facebook match rate. This is another argument for multi-field email capture over single-field forms — the name and phone fields improve ad targeting even if the client never sends them an email.
3. Facebook Social Login (Direct)
When guests log in to WiFi via Facebook Social Login, the connection is direct — Facebook knows exactly who this person is. No matching required. 100% match rate.
What you get from Facebook Login:
- •Facebook User ID
- •Name
- •Email (if permitted by user)
- •Profile photo
What you can do with it:
- •Create Custom Audiences of Facebook-login WiFi guests (100% match)
- •Build Lookalike Audiences based on these profiles
- •Track post-login engagement (did they visit the Facebook page? Did they interact with the brand?)
The tradeoff: Facebook Login portal completion is high, but the data you own is limited (Facebook controls the identity, not you). For retargeting purposes, it's powerful. For email marketing purposes, email capture is better.
Building Retargeting Campaigns
Campaign 1: Visit Retargeting (Core)
Audience: All WiFi guests from the past 30 days Objective: Traffic or Conversions Ad content: "Thanks for visiting [Venue]. Here's 15% off your next order." Budget: $5–$10/day per location Expected ROAS: 4–8x for restaurants, 3–5x for retail
This is the bread-and-butter campaign. Someone visited, you retarget them with a return offer. WordStream's 2025 Facebook Ads Benchmark Report found that retargeting audiences convert 2–3x higher than cold audiences, with CPC 40–60% lower.
Campaign 2: Lapsed Visitor Win-Back
Audience: WiFi guests from 31–90 days ago (no visit in last 30 days) Objective: Traffic Ad content: "It's been a while. We saved your table." Budget: $3–$5/day per location Expected ROAS: 2–4x
Lapsed visitors need a stronger incentive. Pair this with the WiFi win-back email automation for a multi-channel approach — email + Facebook ad for maximum touchpoints.
Campaign 3: Lookalike Expansion
Audience: Lookalike (1%) based on all WiFi guests Objective: Reach or Traffic Ad content: Brand awareness — venue photos, menu highlights, what makes the location special Budget: $10–$20/day per location Expected ROAS: 1.5–3x
Lookalike audiences find people who resemble your WiFi guests but haven't visited yet. Facebook's algorithm uses the Custom Audience profiles (demographics, interests, behaviors) to build a targeting model. A 1% Lookalike in the US is ~2.3 million people; geo-filter it to a 10–15 mile radius around the venue.
Campaign 4: Event Promotion
Audience: WiFi guests from past 90 days + Lookalike (1%) Objective: Event Responses Ad content: "Live music this Friday. You've been here before — bring a friend." Budget: $15–$25 for the event, 3–5 days before Expected ROAS: Hard to measure directly; track WiFi connections on event night vs. average
Setting Up the Pixel Correctly
Standard Events to Configure
| Event | Trigger Point | Purpose |
|---|---|---|
| PageView | Portal loads | Tracks all WiFi guests who see the portal |
| Lead | Portal completed | Tracks WiFi guests who submitted the form |
| CompleteRegistration | Post-portal redirect | Confirms successful registration |
| ViewContent | Sponsor/promo page view | If portal redirects to offer page |
Custom Events
Create custom events for richer tracking:
| Custom Event | Trigger | Use Case |
|---|---|---|
| WiFiConnect | Guest device authenticated | Track total WiFi connects (including Welcome Back) |
| WiFiNewGuest | First-time portal completion | Track new vs. returning guest ratio |
| WiFiReturning | Welcome Back auto-connect | Track returning guest frequency |
Custom events feed into Facebook's conversion optimization algorithm. The more events you track, the better Facebook can optimize ad delivery.
Attribution: Proving WiFi-to-Ad ROI
The hardest part of offline marketing has always been attribution — proving that the person who saw the ad actually showed up at the venue.
WiFi data closes this loop:
- •Guest visits venue → connects to WiFi → captured in Custom Audience
- •Guest sees Facebook retargeting ad → clicks or doesn't click
- •Guest returns to venue → connects to WiFi again → logged as return visit
You now have a measurable cycle: Visit 1 → Ad exposure → Visit 2. The attribution is: "Of the WiFi guests who were retargeted, X% returned within 30 days, compared to Y% of WiFi guests who were NOT retargeted."
Attribution Report Template
Retargeting Attribution Report — [Venue Name] — March 2026
Custom Audience size: 2,340 guests (WiFi captures, past 60 days)
Ad spend: $450 (14 days, $15/day)
Impressions: 38,200
Clicks: 1,146 (3.0% CTR)
Return visits (retargeted group): 18.2%
Return visits (non-retargeted control): 11.4%
Incremental return rate: +6.8 percentage points
Estimated incremental visits: 159
Estimated revenue per visit: $24
Estimated incremental revenue: $3,816
ROAS: 8.5x ($3,816 / $450)
This is powerful data to present to clients. You're directly connecting ad spend to foot traffic — something most local marketing agencies can't do.
Compliance and Privacy
Facebook's Custom Audience Terms
When uploading customer data to Facebook:
- •You must have consent to use the data for advertising purposes
- •Your WiFi portal's consent language should include "personalized advertising" or "targeted marketing"
- •You cannot upload data obtained from third parties without their consent
- •Facebook hashes all uploaded data (SHA-256) before matching
GDPR/CCPA Considerations
- •GDPR: Custom Audience uploads require explicit consent for ad targeting. Your portal consent checkbox should specifically mention "advertising" or "promotional targeting."
- •CCPA: California consumers have the right to opt out of "sale" of personal data. Facebook Custom Audience uploads may be considered a "sale" under CCPA. Include a "Do Not Sell My Data" link on the portal for California-based locations.
- •Data deletion: If a guest exercises their right to erasure, you must also remove them from any Custom Audiences. Document this process.
iOS 14.5+ Impact
Apple's App Tracking Transparency (ATT) framework reduced Facebook Pixel effectiveness significantly. Users who opt out of tracking can't be matched via Pixel. However:
- •Custom Audience uploads (email/phone matching) are NOT affected by ATT — they use deterministic matching, not cookie/device tracking
- •Facebook Login is NOT affected — it's a first-party authentication flow
- •Pixel on the captive portal IS affected on iOS devices where the user has opted out of tracking
This is why Custom Audience uploads and Facebook Login are more reliable than Pixel-only approaches in 2026.
Pricing This Service
WiFi-to-Facebook retargeting is a premium upsell:
| Service | Monthly Price | What's Included |
|---|---|---|
| Setup | $300–$500 one-time | Pixel install, Custom Audience creation, campaign structure |
| Ad management | $200–$400/mo | Campaign management, audience refresh, reporting |
| Ad spend | Client direct | Typically $150–$500/month per location |
| Full service | $400–$800/mo | Management + reporting + strategy + A/B creative testing |
The margin is strong because the operational work after setup is light — refresh the Custom Audience weekly, monitor campaign performance, adjust budgets monthly. An hour per client per month covers it.
Income Disclaimer: Revenue and ROAS figures are illustrative examples based on industry benchmarks. Actual results depend on vertical, ad creative, audience quality, and market conditions. MyWiFi Networks does not guarantee specific advertising outcomes.
Common Mistakes
Not refreshing Custom Audiences. A 90-day-old Custom Audience includes people who visited once and forgot about the venue. Refresh weekly or use Zapier to auto-sync new guests. Stale audiences = wasted ad spend.
Over-targeting. Showing the same ad to the same 500 people for 60 days creates ad fatigue. Rotate creative every 2 weeks. Expand with Lookalikes to keep reach fresh.
Ignoring the Lookalike. Resellers often stop at retargeting existing guests. The Lookalike is where growth comes from — reaching NEW people who look like the client's best customers. Always run a Lookalike campaign alongside retargeting.
No exclusion audiences. Exclude recent visitors (last 7 days) from retargeting. They just came in — they don't need an ad yet. Target the 8–60 day window.
FAQ
Do I need Facebook Business Manager access to set this up?
Yes. The client needs a Facebook Business Manager account with an Ad Account and a Pixel. If the client doesn't have this, set it up for them as part of the onboarding service (add $200–$300 to setup fee).
How often should I upload Custom Audiences?
Weekly is ideal. Automated via Zapier is even better — new WiFi guests get added within hours. At minimum, update monthly. Stale audiences waste ad spend on people who've already returned (or forgotten entirely).
Can I combine WiFi data with in-store purchase data for targeting?
Yes. If the client's POS exports customer email/phone data, merge it with WiFi capture data to create a richer Custom Audience. The combined audience has higher match rates and better targeting signal.
What ad budget should clients start with?
$5–$10/day per location for retargeting, $10–$20/day for Lookalikes. Start small, measure ROAS for 30 days, and scale based on results. Most local businesses see positive ROAS within the first two weeks of retargeting.
Does this work with Google Ads too?
Yes. Google Customer Match accepts email lists similar to Facebook Custom Audiences. Upload the same WiFi guest data and run retargeting on Google Search and YouTube. See our Google Analytics integration guide for the full offline-to-online attribution setup.
What if my client already works with a separate Facebook ad agency?
Share the Custom Audience with the external agency via Facebook Business Manager. Grant them access to the audience without giving them access to the raw guest data. The WiFi data enriches whatever campaigns the agency is already running.