Aggregated reporting
Dashboards use pre-aggregated metrics instead of scanning raw event streams, which keeps analytics fast and stable.
Analytics & privacy
Advanced link detail reporting
Measure clicks with referrer, geo, device, and bot-aware context while keeping privacy mode on by default for new accounts.
What teams get
- Track referrer, geo, device, and social-source inputs without relying on raw IP or full User-Agent storage.
- Flag bots and obvious prefetch traffic so dashboard views and exports are easier to trust.
- Separate QR-origin traffic from ordinary short-link clicks without creating duplicate short URLs.
Availability
Available now
Retention windows and some advanced analytics surfaces vary by plan, but the privacy-safe event model and core reporting are live today.
Bot-aware inputs
Traffic classification preserves likely bot and prefetch signals so teams can filter noise instead of inflating campaign performance.
Privacy mode on by default
New workspaces start with privacy mode enabled, omitting IP and User-Agent entirely from analytics events unless a team chooses otherwise.
QR-aware attribution
Generated QR assets reserve Nimriz-managed `nr=qr` classification so QR scans stay reportable as their own trigger type.
What a cleaner reporting workflow looks like
A campaign owner can compare regular clicks, QR scans, device mix, and referrers without needing full user-level identifiers.
Channel mix
Email, social, partner, and direct traffic stay readable in the same reporting model.
Trigger split
Short-link clicks and QR scans remain separable on the same destination URL.
Privacy default
No raw IP or full User-Agent in analytics events for new accounts.
Reporting posture
Summary metrics power dashboards; live views can still surface recent event context safely.
Why this matters
- Analytics are tied directly to redirect behavior rather than stitched together from multiple weak signals.
- Bot classification and privacy-safe event design make dashboards more believable during campaign reviews.
- QR reporting remains part of the same canonical short link instead of fragmenting performance into separate assets.
- Teams can keep a privacy-conscious default posture without giving up everyday performance reporting.