Checklist: Mobile routing — carrier (3G/4G) vs WiFi split

Checklist: Mobile routing — carrier (3G/4G) vs WiFi split

Many mobile offers only convert on carrier connection. Routing on device alone leaks money.

Step 1 — Detect connection type. You can't read it directly server-side; infer from the IP's ASN (carrier ranges vs ISP/datacenter ranges).
Step 2 — Build the rule.
☐ Carrier ASN → carrier-locked offer (PIN-submit, content billing)
☐ WiFi / ISP ASN → fallback to CPA or CPI offer that converts on any connection
Step 3 — Maintain the ASN list. Carrier ranges shift; refresh monthly from a current ASN dataset.
Step 4 — Flag datacenter ASNs separately — those are bots/proxies, not real WiFi. Route them to a null/house page.

Tradeoff: ASN inference is approximate but the only server-side signal; client-side connection API is exact but JS-only and patchy.

Refresh the carrier ASN list monthly; audit datacenter blocks weekly.