Know the second a campaign lights up — or something's wrong.
First-scan notifications, spike detection, bot-traffic alerts, and new-geo callouts. Routed to email, Slack, or a webhook so the right person sees the signal inside the app they already live in.
- First-scan notification when a code goes live
- Spike detection tuned per campaign baseline
- Bot traffic alerts on suspicious scan bursts
- New-country / new-region first-scan alerts
- Delivery to email, Slack, or webhook
- Mute rules per QR or per workspace
What's included
First-scan alert
Get pinged the moment someone scans a newly-printed code for the first time. Useful for confirming production runs shipped correctly and that yard signs / packaging / event badges actually made it into the wild.
Spike detection
Every QR builds a baseline over time. When scans spike meaningfully above that baseline — the kind of signal you'd actually want to know about — ScanForge alerts you so you can ride the moment.
Dip detection
The inverse: when a code that normally sees steady traffic suddenly goes quiet, an alert fires. Common causes: QR got obscured, landing page went down, sticker got removed. Catch it early.
Bot traffic alerts
When ScanForge detects a bot-driven scan burst — scrapers, security scanners, spam — you get a heads-up. Bot scans are already excluded from your main numbers; the alert just tells you so you can block the source if it persists.
New-geography alerts
The first scan from a new country (or region) triggers an alert. Useful for global brands watching international launches, and for security ops watching for scans in geographies where a code shouldn't be.
Email, Slack, or webhook
Route alerts to the channel your team actually checks. Per-alert routing — spike alerts to marketing, bot alerts to ops, first-scan alerts to the campaign owner.
Common questions
- Can I get alerted when a QR code gets its first scan?
- Yes. ScanForge sends a first-scan alert to the campaign owner the instant a newly-created QR code is scanned for the first time. Useful for confirming production runs actually shipped and that yard signs, packaging, or event badges made it into the wild.
- How does spike detection work?
- Every dynamic QR builds a rolling baseline of its own scan rate. When current scans run meaningfully above that baseline (not a generic percentage threshold — a statistically significant spike), ScanForge fires a spike alert. You can tune sensitivity per code or per workspace.
- Does ScanForge alert me when bots are scanning my code?
- Yes. When bot-detection classifies a burst of scans as likely non-human (scrapers, security scanners, spam), a bot-traffic alert fires. Bot scans are already excluded from your main analytics — the alert just gives you awareness so you can block a source if it persists.
- Where do alerts go?
- Email by default. You can also route alerts to a Slack channel or an arbitrary webhook endpoint. Routing is per-alert-type, so critical ops alerts can go one place and routine campaign alerts can go somewhere quieter.
- Can I mute alerts for specific codes?
- Yes. Mute a specific QR code, an entire campaign, or a whole workspace. Mutes can be time-bounded (e.g. 'quiet until next Monday') so you don't accidentally leave them off forever.
Related features
First scan. Biggest spike. Earliest warning.
7-day free trial — full access, no credit card required.