Feature
Route by device, language, or geography - App/Device, Language, and Geo-Fencing pointers, all on the same rule engine.
QR Hero smart routing sends a single QR code to different destinations by device, language, or geography, all from the same rule engine.
A single printed code has no way to know who's scanning it - an iPhone user needs the App Store, an Android user needs Play, a visitor in France reads French, and a poster in an airport gets scanned by people from a dozen countries in the same hour. Printing separate codes for every combination isn't practical, and guessing wrong sends people to the wrong store or the wrong language entirely.
QR Hero's smart routing puts a rule engine behind a single code instead. Layer conditions by device (iOS, Android, desktop), language (based on browser or device locale), or geography (country or region), and each one gets its own destination - an App Store link, a Play Store link, or a localized page - decided in milliseconds at scan time, before the redirect ever fires. Rules can be combined too, so "iOS + French" is as valid a branch as any single condition.
A required default fallback means a rule miss never dead-ends the scan - there's always somewhere for an unmatched visitor to land. It combines directly with scheduling and A/B testing for routing that shifts by time as well as by rule, and per-branch scan analytics show exactly how traffic actually splits across device, language, or region, turning a guess about audience mix into real data from the poster or campaign itself.
Smart routing builds on the same Dynamic links a code already uses, and pairs well with Scheduling & A/B testing for time-based rules and Scan analytics for confirming which route actually performs best.
iOS needs the App Store, Android needs Play, France needs French copy.
Layer them together for a genuinely multi-market audience.
The rule engine decides in milliseconds, before the redirect fires.
Device (iOS/Android/desktop), language, or geography (country/region).
App Store vs Play Store vs web, or a localized page per market.
No guessing which version to print for which audience.
Device rules
iOS, Android, or desktop - for app-install codes that need the right store.
Language rules
Based on browser/device locale, for multi-market campaigns.
Geography rules
By country or region, for localized pages or regional offers.
Required default fallback
A rule miss never dead-ends the scan.
Combines with scheduling
Time-and-rule-based routing together with A/B testing.
Per-branch scan analytics
See how traffic splits across device, language, or region.
Put it to work on your next print run
Your first dynamic code is live in minutes, on your own domain.
Yes - rules can be layered (e.g. iOS + French) so a single code serves a genuinely multi-dimensional audience correctly.
The code falls back to a default destination you set, so nothing dead-ends even for an unmatched device, language, or region.
Routing uses the browser/device locale reported at scan time, which is the standard signal most routing tools rely on.
Common pairings for campaign-driven teams.
See this feature in context, industry by industry.
Your first dynamic code is live in minutes, on your own domain.