Targeting for Intercepts
You have the ability to target screeners you've published as either web or app intercepts based on location, device, browsers, and operating system. That means you can choose to only display your screener to mobile users, or only display in certain countries or cities. This has been a long time in development, but beware that targeting relies on browser information called a "user agent string" and GeoIP and is only about 85% accurate.
That means you could lose out on a ton of potential responses if you turn on targeting. Consider adding simple screener questions for the things you really care about instead of using targeting. For example, create a dropdown question "Where are you located?" Then only put the answers you care about and an "Other" answer. You can then filter with more certainty in recruits on that answer.
To activate targeting, go to Screeners >> Targeting. Then you can toggle different devices, browsers, or locations on and off. If you start to see a drop in response rate, you probably just targeted out too many people, so don't forget to reset all four targets to "all" if you need to troubleshoot.
Cities & Countries Supported
You can just start typing in the field to search for cities or countries. Only countries and cities with a population of at least 100,000 are included.
How User Strings Work (from Device Atlas)
User-Agent strings, often referred to as User-Agent lookup or User-Agent parsing is based on analyzing User-Agent strings and is built in to the HTTP standard which briefly defines what User-Agents are and what they can be used for. The User-Agent string is one of the HTTP headers sent by the browser which informs the web server about the visiting device, name of the browser, rendering engine, etc.
For historical reasons, there is no strict structure to User-Agent strings. They contain many keywords which aren’t true for the request. For example, many User-Agent strings start with the word “Mozilla” even when they have nothing to do with the Mozilla’s browser Firefox. Here's an example of a User-Agent string used by IE Mobile on a Windows Phone-based device:
Mozilla/5.0 (Mobile; Windows Phone 8.1; Android 4.0; ARM; Trident/7.0; Touch; rv:11.0; IEMobile/11.0; Microsoft; RM-1141) like iPhone OS 7_0_3 Mac OS X AppleWebKit/537 (KHTML, like Gecko) Mobile Safari/537
There are hundreds of thousands of device and browser combinations with different User-Agent strings which have to be tracked in order to make the detection accurate. Lots of devices masquerade as something else, which is a common practice, and makes it even trickier.