Device targeting uses browser and operating-system signals to choose a destination. One public URL can send iPhone visitors to the App Store, Android visitors to Google Play and desktop visitors to a product page.
Plan before publishing
Choose the universal fallback first, then add only destinations that materially improve the experience. OS-specific iOS and Android routes take priority over a generic mobile route.
- Set the default destination.
- Add iOS and Android routes.
- Preserve UTM values on every branch.
Build and test the workflow
Test iOS, Android, desktop, tablet, an in-app browser and an unknown user agent. Confirm the final URL and campaign parameters rather than stopping after the redirect appears to work.
Worked example
A store link opens a listing. A deep link attempts to open a screen inside an installed app and requires app and website configuration. Do not describe ordinary store routing as deferred deep linking.
Measure the right outcome
DrutoLink can report redirect activity by device category, but a click does not prove an installation. Use store or app analytics for installs, registrations and purchases.
Troubleshooting checklist
- Wrong store: inspect broad mobile rules.
- App does not open: verify deep-link configuration.
- Unknown device fails: improve the fallback page.
Product limits and responsible use
User-agent detection can be incomplete or misleading. A universal fallback page with explicit choices prevents unknown devices from reaching an error or inappropriate store.