A dynamic QR code points at a short link we resolve, so the printed code never has to change — only where it sends people.
A wrong URL on 5,000 flyers becomes a one-minute edit instead of a reprint.
Set the code live for the campaign window, then point it at an evergreen page instead of a dead link.
Scans are attributed to the code, the campaign and the day, so print channels finally get measured.
A dynamic QR code does not contain your destination. It contains a short Qrievo URL, and that URL is what the printed pattern encodes forever. When someone scans, their phone opens the short URL, Qrievo looks up where it currently points and redirects. Changing the destination changes a database row, not the code — which is why the printed artwork never needs to change and why the pattern looks identical no matter how long the real URL is.
Dynamic is not automatically right. A Wi-Fi code on a café wall should be static: it needs no analytics, it must work when your subscription does not, and the password is not going to change on a schedule. The same applies to a vCard on a personal card and to anything that must keep working with no service behind it. Choose dynamic when the destination might change, when you need scan data, or when the printed item will outlive the campaign.
A campaign has an end date, and a code that outlives it usually points at a dead page. Set an expiry so the code stops on the day the offer does, and a fallback URL so a late scanner lands on something sensible rather than a 404. Pausing does the same thing immediately, which is what you want when a product is withdrawn. Password protection is available where a code is printed publicly but the destination is not meant to be.
It stops resolving. Because the destination lives on our side, an inactive subscription means the redirect no longer runs, and scanners reach a page saying the code is not currently active. Resubscribing restores it immediately and the printed pattern is unchanged, so nothing needs reprinting. This is the real trade-off of dynamic codes and it is worth knowing before you print ten thousand of them: convenience now, a dependency later.
A static code contains the data itself, so the data can never change. A dynamic code contains a short URL that we resolve, which means the destination stays editable while the printed pattern stays the same.
Not while your account is active. If a subscription lapses the codes stop resolving, and resubscribing brings them back — the printed pattern is unchanged.
Lookups are cached and the analytics event is recorded after the visitor has already been sent on, so tracking never delays the scan.
Yes, as often as you like. Each change takes effect on the next scan.
Create one in under a minute and edit the destination as often as you need.