Targeting
Targeting lets one short link route visitors to different destinations based on who they are. You can route by geography, language, device, operating system, browser, or a mix — and control the order Shortn checks them.
Targeting is set in a link’s advanced settings, in the Geo targeting, Device targeting, OS targeting, Browser targeting and Language targeting sections, and is plan-gated.
Geo targeting
Send visitors to different destinations by country or world region.
- Country — route by ISO country code (for example
us,de,br).ukis accepted for the United Kingdom and saved asgb. - Region — route by world region: North America, South America, Europe, Asia, Africa, Oceania, or Middle East.
Region here means a continent or world area, not a state or province.
Middle East countries also belong to their continent. A visitor from Egypt, Turkey, or the UAE matches a Middle East rule first, and falls back to the Africa, Europe, or Asia rule when the link has no Middle East rule.
Each rule pairs a target with a destination URL, for example:
| Target | Destination |
|---|---|
country:us | https://example.com/us |
country:de | https://example.com/de |
region:europe | https://example.com/eu |
A visitor is sent to the destination for their country if one matches; otherwise a region rule is checked.
Language targeting
Send visitors to different destinations by the language their browser asks for, for
example Spanish speakers to /es wherever they are. Language comes from the browser’s
language settings, not from the visitor’s location, so a VPN doesn’t change it.
Each rule pairs a language code with a destination URL:
| Language | Destination |
|---|---|
es | https://example.com/es |
pt-BR | https://example.com/br |
pt | https://example.com/pt |
zh-Hant | https://example.com/tw |
Use a base language (es, pt) or a regional variant (pt-BR, es-419, zh-Hant)
when the difference matters. Shortn picks the closest rule:
- A Brazilian visitor (
pt-BR) gets thept-BRrule, and a visitor from Portugal getspt. - A visitor from Mexico (
es-MX) gets theesrule. - Browsers list several languages in order of preference. If the first one has no rule,
the next one is tried, so a visitor who prefers French but also reads German gets your
derule when there’s nofrrule. - Only close matches count. A Catalan visitor doesn’t get the Spanish page, and a visitor whose languages have no rule goes to the next rule or the default destination.
Many browsers add English to the end of the list, so an en rule also catches visitors
whose own language has no rule.
Device, OS, and browser targeting
Route by the visitor’s device, operating system, or browser.
- Devices —
desktop,mobile,tablet. - Operating systems —
ios,android,windows,macos,linux. - Browsers —
chrome,safari,firefox,edge,opera.
Each maps a target to a destination URL — for example, send mobile visitors to a mobile site, or Windows visitors to a PC download.
App store destinations
The ios and android rules of OS targeting are the simplest way to send iPhone
users to the App Store and Android users to Google Play. There’s no separate mobile
setting: these are ordinary OS rules, and the links list’s Deep links filter finds the
links that have one.
How visitors are detected
Device, OS, and browser come from what the visitor’s browser reports about itself.
- iPads in desktop mode count as Macs. Safari on iPad requests desktop websites by
default and then reports itself exactly like Safari on a Mac, so it matches
macosanddesktoprules, notiosandtablet. Firefox’s desktop mode on iPad does the same. Chrome and Edge on iPad, and Safari’s “Request Mobile Website” mode, are detected as iPads. - App Store links work everywhere. To send iPad visitors to the App Store as well,
use the same
apps.apple.comlink as themacosdestination. - Apps’ built-in browsers on iPhone and iPad count as Safari. Links opened inside
Instagram, Facebook, TikTok, and similar apps match
safarirules. - Some browsers don’t match a browser rule. Samsung Internet doesn’t count as
chrome, because Chrome-only destinations such as the Chrome Web Store don’t work in it. Brave reports itself exactly like Chrome, so it matcheschrome. - Unrecognised visitors get no device match. A visitor counts as
desktoponly when it reports Windows, macOS, Linux, or ChromeOS. Requests with no or unknown browser details, such as scripts and most bots, skip device rules and go to the next rule or the default destination.
When a destination stops working
Shortn checks every destination of a link every 30 minutes, not only the main one (see destination health): each country, region, language, device, OS and browser target is checked too, and a new or changed one right after you save it. If one stops working (it returns an error or can’t be reached):
- its section in the link’s settings shows a red warning, with the address and the error;
- everyone in the workspace gets a notification once, and again when it works again;
- the link’s log records both.
Visitors keep going to that destination until you fix or replace it: Shortn never moves them elsewhere on its own.
What each plan can target
| Capability | Professional | Agency |
|---|---|---|
| Country targeting | ✓ | ✓ |
| Language targeting | ✓ | ✓ |
| Region (world) targeting | — | ✓ |
| Device-type targeting (desktop/mobile/tablet) | ✓ | ✓ |
| OS targeting (including iOS and Android app destinations) | — | ✓ |
| Browser targeting | — | ✓ |
Free and Starter plans don’t include targeting. See plans.
Routing priority
When a visitor opens the link, Shortn checks your rules in a priority order and uses the first match. The default order is:
- Geo (country, then region)
- OS (including
iosandandroid) - Browser
- Device type
- Language
As soon as a rule matches, the visitor is sent to that destination and no further rules are checked. You can change the order in the link’s Routing priority section.
If nothing matches, the visitor goes to the link’s default destination. A/B testing, if enabled, only applies when no targeting rule matches.