Configure and test smart QR routing
Last updated
Availability depends on your plan or configuration
Routing rules
iOS / Android
Test routing
22:00 → 02:00
Fallback URL
https://example.com
What to do
1. Choose More → Smart QR code, or use the button above. Sign in to a workspace with a paid smart-routing allowance; this code always uses a managed dynamic link.
2. Enter complete destination URLs. Give each rule a useful name, choose its conditions, and move it up or down to set priority. The time zone applies to every rule, rather than the visitor’s phone time.
3. Use Test routing to select a device and date/time. Check a matching visit, an unmatched visit, overlapping rules and the moment the window closes. A start time is included; an end time is excluded. The preview uses the same server rule logic as live redirects.
4. Choose the platform domain or an active custom domain, save the code, then download its artwork. Check the final printed size on real iOS and Android devices. Later edits keep that saved scan address; changing your default domain only affects new codes.
5. Choose iOS, Android, desktop or any device for each rule. Use it for store links or mobile-specific instructions. Detection uses browser information; an unusual or disguised browser can receive the desktop or fallback destination.
6. Select the applicable weekdays and set both start and end time, or leave both blank for all day. No selected weekday means every day. A 22:00–02:00 window crosses midnight and belongs to the day on which it starts.
7. Rules run from top to bottom. Within one rule, the device, day and time conditions must all match. Put a specific exception before a broad rule. A valid HTTP or HTTPS fallback is required, so unmatched visits still have a destination.
8. Routing chooses a destination; it does not check stock, identify a person, verify a payment or restrict access to your destination website. Do not use device detection as an authorization check.
9. Time windows repeat by weekday. Date-based campaigns, language or country targeting, random splits and conversion attribution are not available in these rules. General scan analytics record visits; they do not report which destination converted.