Scan rules & routing

Scan rules decide what happens when someone scans a code: redirect, show a landing page, block, or send them to a fallback URL.

#Rule evaluation order

QR Hero evaluates rules in a fixed pipeline:

1. Active window — honour start/end dates and paused status
2. Password gate — challenge before continuing
3. Scan cap — stop after N total or unique scans
4. Routing rules — match country, language, device, or custom signals
5. Default destination — the primary URL configured on the code

#Simple routing maps

Legacy routing used flat maps (country, language, device). New codes use the rules array with explicit operators:

• eq / neq — equals or not equals
• in / nin — membership lists
• Combine conditions with AND / OR groups

Each matching rule chooses an action: redirect to a URL or landing to show the prelander.

#Routing pointers

Some product types attach routing pointers on the code record for language, geo, or app-store routing without opening the full rule builder. Pointers compile into the same runtime contract consumed by the redirect engine.

#Prelander and pixels

When action is landing, QR Hero renders a branded countdown page. Attach tracking pixels (Meta, TikTok, Google Analytics, Google Ads, LinkedIn, Snapchat) so tags fire before the final redirect.

#Testing rules

Use browser dev tools or curl with appropriate headers to simulate countries and devices. Always test from a real mobile network before campaign launch — carrier DNS can differ from desktop VPN tests.

#Protection and disputes

Hyper dynamic and high-volume codes may pass through destination protection. If a URL is flagged, resolve disputes from the code editor without republishing the QR image.