Redirect Rule Not Triggering
What to do when a geo, device, scheduled, or scan-limit redirect is not working as expected.
General Diagnostic Steps
Verify the rule is active
Open the QR code in Edit mode → Settings tab → Redirect Rules section. Check that the rule is enabled (the toggle is on).
Check rule priority
Rules are evaluated in priority order: Geo > Scheduled > Device > Scan-Limit. A higher-priority rule that matches will take precedence. If your Geo rule fires for a location and your Device rule also matches, only the Geo rule will execute.
Verify your plan includes this rule type
Some rules require specific plans. Geo-targeting requires Premium+, Device and Scheduled redirects require Pro+, Scan-Limit requires Basic+. If you are on a lower plan, the rule will not trigger.
Geo-Targeting Not Triggering
Confirm you are physically in or near the targeted location, or use a VPN to test from that region
City-level targeting has ~92–95% accuracy — there is a small chance the detected city is incorrect due to IP geolocation limitations
VPN users may appear in a different location — test without a VPN
WiFi may provide less accurate location than mobile data — test on cellular
Scheduled Redirect Not Triggering
All schedule times are in IST (India Standard Time). Confirm the current IST time falls within your configured window
Check that the correct days are selected for the rule. If you set 'Monday only' and today is Tuesday, the rule will not trigger
The scheduled redirect only applies to new scans — a scan that was already in progress before the time window ended will still go to the scheduled URL
Device Redirect Not Triggering
Test on a different device to confirm the device you are using is correctly identified (try both iPhone and Android)
Some privacy-focused browsers mask their User-Agent, which can prevent accurate device detection — these will fall through to the default URL
Check that you have entered the correct URL for the device type that should trigger
Was this article helpful?