Myth: Device routing means splitting mobile vs desktop

Myth: Device routing means splitting mobile vs desktop

The shortcut: one rule for mobile, one for desktop. Done.

The correction: "mobile" hides iOS vs Android, app-webview vs browser, and tablet — each with different offers and payouts. A two-bucket split routes an iOS user to an Android-only offer and eats the loss.

Framework — device routing axes:

— Step 1: Split OS (iOS / Android) before anything else.
— Step 2: Add browser vs in-app webview (in-app blocks some redirects/SDKs).
— Step 3: Separate tablet from phone where the offer's UX differs.
— Step 4: Keep desktop as its own track, not "everything not mobile."

Checklist:
☐ iOS and Android routed separately
☐ In-app webview detected and handled
☐ Tablet not lumped with phone

Re-test device detection after any offer swap.