Practice
Device, OS and Connection Targeting: What You Can Narrow and Why
In this article
- Start with the device
- Consider operating systems and versions
- Account for browsers
- Match the connection to the experience
- Narrow with a reason, then test
Start with the device
Device targeting lets an advertiser choose which kinds of screens can receive an ad. The broadest distinction is usually desktop versus mobile, though some platforms offer more detailed device categories. This choice affects more than who sees the ad: it also shapes how the creative appears and what the destination page needs to support.
A desktop ad may have room for a wider layout, while a mobile ad is more likely to appear in a compact, touch-first setting. The landing page should make its main information easy to find on a small screen, with readable text, clear navigation and controls that are comfortable to tap. If an ad promises an experience that the destination cannot deliver on that device, the mismatch can undermine the visit.
Consider operating systems and versions
Targeting by operating system can help align a campaign with the software environment a visitor uses. This can matter when a page, form or interactive feature behaves differently across systems. It may also help identify a technical issue that appears only in a particular environment.
Version targeting can be more precise, but it can also exclude visitors whose software differs from the selected range. Use it when there is a clear compatibility reason, rather than narrowing simply because the option is available. Before setting restrictions, check whether the page’s essential functions work across the operating systems and versions the campaign is likely to reach. If older software cannot support a feature, consider whether there is a simpler fallback experience.
Account for browsers
Browsers can display the same page differently, and their privacy settings or support for web features may vary. A page that looks correct in one browser may have layout problems, blocked elements or a form that does not behave as expected in another. Browser targeting can be useful when a campaign depends on a feature that is not consistently supported.
It can also remove potential visitors without solving the underlying problem. When possible, make the page work across commonly used browser environments instead of relying on a narrow audience filter. Test the ad and destination together: a creative may render properly while the page it opens does not, or the reverse.
Match the connection to the experience
Connection targeting may distinguish between broad types of access, such as mobile data and fixed connections. Carrier targeting can further limit delivery to people using particular mobile networks. These settings can be relevant when the offer, service or page is designed for a specific connection context, but they do not guarantee that every visitor will have the same speed or reliability.
A landing page should remain usable when a connection is slow or unstable. Large images, heavy scripts and unnecessary page elements can delay the content people came to see. Mobile page speed matters because visitors may be browsing on variable connections, and a long wait can interrupt the path from ad to page. Keep essential content available early, optimize media and avoid making the core action depend on optional features loading first.
Narrow with a reason, then test
Every added restriction reduces the pool of eligible impressions in general terms. Device, operating system, browser, connection and carrier filters can combine, leaving fewer opportunities for an ad to appear. A smaller audience may be appropriate when it reflects a genuine technical or campaign requirement; otherwise, broad settings can provide room to learn which environments are suitable.
Before sending traffic, test the complete journey on real devices, not only in a desktop preview or an emulator. Open the ad where possible, follow it to the landing page and check that the layout, text, forms and buttons work as intended. Try different screen sizes and connection conditions, and confirm that the page remains understandable if some content loads slowly. Review delivery and page behavior after launch, then adjust targeting only when the evidence points to a specific compatibility issue.