Meta Pixel + CaptiveWiFi

Retarget the guests who
actually walked through your door.

CaptiveWiFi fires Meta Pixel PageView and Lead events the moment a guest connects to your venue WiFi. Build custom audiences of real, verified in-venue visitors — not just website browsers — and retarget them on Facebook and Instagram.

Book a demo Help Centre
Pixel event fired — Meta
fbq('track', 'Lead', {
  venue: 'The Bell, Oxford',
  visit_type: 'first_visit',
  visit_date: '2026-06-21',
  source: 'wifi_login'
});
Guest added to custom audience
How it works

WiFi login to Meta custom audience
in a single connection.

1
Guest joins your WiFi
The guest connects to your venue WiFi and the CaptiveWiFi portal loads on their device.
2
Pixel events fire
CaptiveWiFi fires PageView and Lead pixel events through your Meta Pixel, passing venue and visit data as event parameters.
3
Custom audience built
Meta adds the guest to your custom audience of WiFi visitors — real people who physically visited, not just cookie-based website browsers.
4
Retargeting ads serve
Your Facebook and Instagram ads reach a warm, high-intent audience of people who have already been to your venue — with far higher relevance than cold targeting.
Pixel events

Which Meta Pixel events
CaptiveWiFi fires.

PageView
WiFi portal page view
Fires as soon as the guest's device loads the CaptiveWiFi portal — before they log in. Useful for broader reach audiences.
Lead
WiFi login completed
Fires when the guest submits their details and connects. This is the high-intent event — a verified, in-venue visitor. Best for your core retargeting audience.
Why it matters

Not cookies. Real guests
who visited your venue.

Verified in-venue audiences
Unlike cookie-based website audiences, WiFi-triggered pixel events are based on physical presence. Every person in your custom audience actually walked into your venue.
Lookalike audiences from real guests
Use your WiFi-built custom audience as the seed for Meta lookalike audiences. Find new customers who look like the people who already love visiting your venues.
Better ad relevance and ROAS
Retargeting people who have already visited drives dramatically higher click-through and conversion rates than cold audiences. Your ad spend goes further.
FAQ

Common questions about
Meta Pixel + CaptiveWiFi.

Do I need a Meta Business account to use this integration?
Yes. You need an active Meta Business Manager account with a Meta Pixel created and your Pixel ID to hand. During CaptiveWiFi setup you enter your Pixel ID and the integration handles the rest. No developer required.
Can I use a different Pixel ID per venue?
Yes. CaptiveWiFi supports one Pixel ID per venue. If you run multiple venues for multiple brands or ad accounts, each venue can fire events to a different Meta Pixel, keeping your audience data cleanly separated.
Is this affected by iOS privacy changes?
The WiFi login event is a server-side trigger from the CaptiveWiFi platform — it is not reliant on browser cookies or client-side JavaScript. This makes it significantly more resilient to iOS tracking limitations than website-based pixel implementations.
Does this integrate with Meta's Conversions API?
Server-side event firing via the CaptiveWiFi platform is compatible with Meta's Conversions API approach. Speak to our team about a Conversions API setup if you want the highest fidelity event matching for your Meta campaigns.
Related integrations

Connect CaptiveWiFi to
your whole stack.

Klaviyo
Advanced WiFi-to-Klaviyo sync with custom events and online-to-offline journey tracking.
Brevo
Sync WiFi guests into Brevo contact lists with visit tags and welcome automations.
Mailchimp
WiFi guest emails into Mailchimp audiences with visit tags and welcome series.
Campaign Monitor
Grow your Campaign Monitor subscriber list from every in-venue WiFi connection.
Get started

Retarget real guests
on Meta.

Fire Meta Pixel events at WiFi login. Build audiences of verified in-venue visitors. Retarget them on Facebook and Instagram with ads that are actually relevant.

Book a demo