Destination monitoring
EZQR checks that the pages your dynamic codes open are working and tells you when one breaks or recovers.
A printed code is only as good as the page behind it. If a landing page is deleted or a server goes down, people who scan your code hit an error and you rarely hear about it. Destination monitoring checks each dynamic code's destination on a schedule and alerts you when it breaks and when it comes back.
Monitoring is on for every plan. It runs automatically for active dynamic codes, with no setup.
Check intervals
| Free | Lite | Pro | Max | |
|---|---|---|---|---|
| Check frequency | Once a day | Every 6 hours | Every hour | Every 15 minutes |
What's checked
EZQR requests the code's Target URL and follows up to 5 redirects. A check fails if:
- The page returns
404,410, a5xxserver error or another4xxerror. - The request takes longer than 10 seconds.
- The domain doesn't resolve, the connection is refused or reset, or the SSL certificate is invalid.
Responses of 401, 403, 405 and 429 count as working. They show the server is up even if the page needs a login or limits requests.
Before marking a working destination as down, EZQR checks it a second time a few seconds later. This avoids alerts for brief blips.
Monitoring doesn't run for static codes or deactivated codes. Only the main Target URL is checked. URLs used in smart rules, geo-targeting or A/B variants aren't monitored. Destinations that point to private network addresses can't be checked.
Status on a code
Each dynamic code's page has a Destination card. It shows:
- Whether the destination is Working or Down, and the reason for the last failure, such as "Page not found (404)" or "Timed out after 10 seconds".
- Next check, or Down since while the destination is failing.
- A history bar of checks for the last 7 days, from 7 days ago to Today.
Click Check now to run a check immediately, for example after you fix a page. Codes with a broken destination also show a red dot in your code list.
Email alerts
EZQR emails workspace owners and admins when a destination goes down and again when it recovers. Choose how in Settings → Destination alerts:
| Option | Behavior |
|---|---|
| Email right away | One email per change, sent as it happens. This is the default. |
| One email a day | A daily digest listing each change and how many destinations are still down. |
| Don't email me | No emails. Status still shows on each code. |
Only workspace owners and admins can change this setting.
With Email right away, a destination that fails on its very first check is included in the daily digest instead of triggering an instant email.
Webhook alerts
On Pro and Max, you can send status changes to your own systems with webhooks. Subscribe an endpoint to these events:
| Event | Sent when |
|---|---|
qr.destination_down | A dynamic code's destination stopped responding |
qr.destination_recovered | A dynamic code's destination is reachable again |
The payload includes the code's ID and name, the URL checked, the HTTP status code and the failure reason.
Webhook endpoints per workspace: 5 on Pro and 25 on Max.