Device classes
Configure supported mobile, tablet, and desktop destinations from the same link.
TRAFFIC CONTROL
Device-Targeted Redirects from One Smart URL
Adapt the destination to broad device classes when the best mobile experience differs from the desktop journey.
Default destination
Keep a reliable fallback for unknown or unmatched user agents.
Native-app support
Use compatible deep-link destinations where the operating system and target app support them.
When device routing is useful
A mobile visitor may need an app-aware destination, while a desktop visitor may need a full website or web dashboard. Device routing keeps the shared URL consistent while selecting the configured journey.
Use device rules only when destinations genuinely differ. Unnecessary branching makes campaigns harder to test and maintain.
- Mobile app and desktop web destinations
- Platform-specific store pages
- Mobile checkout versus desktop catalog
- Device-aware onboarding
User-agent classification
Device routing typically uses the browser user-agent to classify a request. This is a broad technical signal, not a guaranteed description of the person or hardware.
Keep a working default URL because privacy settings, new devices, embedded browsers, and automated clients can produce unexpected values.
- Mobile, tablet, and desktop groups
- Default fallback
- No assumption of personal identity
- Testing across common browsers
Deep links and fallbacks
Opening a destination in a native app depends on the destination's supported universal links, app links, URI schemes, installed applications, and browser behavior. No redirect platform can guarantee an app handoff in every environment.
Pair app-aware destinations with a useful web fallback so visitors can still continue when the application is unavailable.
- Use supported destination formats
- Provide a web fallback
- Test iOS and Android separately
- Avoid absolute app-opening claims
Frequently asked questions
Can Linktery guarantee that every link opens an app?
No. App opening depends on the destination, operating system, installed app, browser, and supported linking standards.
What happens when a device is not recognized?
The link should continue to its configured default destination.
Is device targeting based on personal identity?
No. It uses broad technical request information such as the browser user-agent.