Wi-Fi / mobile
Wi-Fi / mobile traffic describes how a visitor reached the landing page — over a local Wi-Fi network or through the carrier's mobile data (3G/4G/5G). It's read from IP type and device signals, and it decides which offers a visitor can even convert on. In PWA arbitrage it's a base-level filter, right alongside geo and carrier.
Why connection type limits which offers convert
Some verticals — carrier billing offers and mobile subscriptions in particular — physically require a mobile connection, since billing runs through the operator's SIM session. Wi-Fi traffic, by contrast, often gives an equally clean audience for gambling and utility apps but can't support anything tied to a phone number's carrier session. Ignoring the difference means paying for clicks that structurally can't convert on that specific offer.
Wi-Fi / mobile as a quality signal and targeting layer in APEX
A sudden subnet switch on the same device, or a Wi-Fi-range IP where the geo implies mobile-only traffic, is a solid trigger for extra scrutiny in APEX's antibot. In targeting, connection type gets combined with carrier and device to route only qualifying visitors into the PWA. APEX's sticky split tests are a natural way to slice results by this exact signal and spot where conversion actually drops.
FAQ
- Is Wi-Fi or mobile traffic better?
- Neither is universally better — it depends on the offer: carrier billing and mobile subscriptions need a mobile connection, while plenty of other verticals convert just as well on Wi-Fi.
- Can connection type be detected without device access?
- Yes, approximately — from the IP range and ASN, since mobile carriers and home Wi-Fi ISPs typically hand out different address pools, which is exactly what antibot systems use for a first-pass filter.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free