Device targeting is the practice of serving different website content, layouts, CTAs, or personalised experiences to users based on the type of device they are using — most commonly segmented into mobile (smartphones), tablet, and desktop. Device type is detected via the browser's User-Agent string or client hints, which identify the operating system, device category, and sometimes the specific device model. In ecommerce, device targeting is used to optimise the experience for the screen size, input method (touch vs. mouse), connection speed, and user context associated with each device category.
Why Device Targeting Matters for Ecommerce
In India, mobile accounts for 70–80% of ecommerce traffic, yet desktop typically converts at 2–3x the rate of mobile for most D2C brands. This gap exists because mobile experiences are often directly ported from desktop designs without rethinking for touch navigation, smaller screens, and on-the-go context. Device targeting allows brands to close this gap by delivering genuinely optimised experiences per device, rather than relying on responsive design alone to handle the differences.
Key device-specific optimisations in Indian ecommerce:
- Mobile: Sticky add-to-cart bars, tap-friendly navigation, UPI-first payment options prominently displayed, one-thumb-reach CTAs, and streamlined checkout with autofill.
- Desktop: Multi-column product grids, hover-state product previews, richer product imagery (large format), and comparison tables.
- Tablet: A hybrid layout optimised for landscape viewing with touch navigation.
Showing a desktop-optimised promo banner to mobile users, or hiding a multi-step desktop navigation on mobile without providing an equivalent, creates friction that directly reduces conversion rate.
Real-World Example
A D2C supplement brand (similar to The Good Bug) notices their mobile checkout completion rate is 38% vs. 61% on desktop. They run a device-targeted test: mobile visitors see a new one-page checkout with UPI and Cash on Delivery as the first two payment options; desktop visitors continue with the existing three-step checkout. Mobile-specific test runs for 12 days (high mobile traffic makes sample accumulation fast). Mobile checkout completion lifts from 38% to 49% — an 11-percentage-point improvement worth approximately ₹4.2 lakh/month in recovered checkout revenue. Desktop is unchanged. The finding: the mobile checkout problem was device-specific and required a device-specific solution, not a global redesign.
How to Improve / Optimize Device Targeting
- Segment your analytics by device first. Before building device-specific experiences, audit your conversion funnel by device type. Identify where mobile and desktop diverge — the largest gap is typically at checkout, but may also appear at add-to-cart or product page. This tells you where device targeting will have the most impact.
- Run device-segmented A/B tests. When testing a checkout improvement, run the test only for mobile visitors. Including desktop visitors dilutes the result (since the test change is optimised for mobile) and may produce a misleading "no significant difference" conclusion.
- Don't treat device targeting as a substitute for responsive design. Device targeting should handle experience differences that responsive design cannot — content decisions, offer customisation, payment method prominence — not layout differences that CSS should handle.
- Test on real devices, not just browser emulation. Browser developer tools approximate mobile screens but don't replicate actual touch interaction, real-device performance, or mobile browser behaviour quirks. Always QA device-targeted experiences on a physical device — especially budget Android phones prevalent in India.
- Monitor device mix shifts. As your acquisition mix changes (more Instagram mobile traffic vs. Google desktop search), your device distribution changes. Re-evaluate device targeting rules quarterly to ensure they reflect your current traffic reality.
Device Targeting in A/B Testing
Device targeting is one of the most important experiment segmentation dimensions in ecommerce. Most A/B tests should be analysed by device (not just globally), because the same change can lift mobile conversion and harm desktop (or vice versa). Shipping a variant based on a combined mobile + desktop result may help one group while hurting another. CustomFit.ai supports device-level experiment targeting and reporting.
Run smarter A/B tests with CustomFit.ai — 14-day free trial, no credit card required.