Aggregated reporting
Dashboards use pre-aggregated metrics instead of scanning raw event streams, which keeps analytics fast and stable at any click volume.
Analytics & privacyAll plans, depth varies
Privacy-first link analytics
Measure clicks with referrer, geo, device, and bot-aware context. Privacy-aware analytics is the default, with no raw IP or full User-Agent storage.
Default
Standard privacy
5 dimensions
Click context
Bot-aware
Traffic filtering
app.nimriz.com/analytics/go.acme.com~launch
go.acme.com/launch
Last 24 hours
Human clicks
16,762
Live now
Apr 26May 3May 10May 17May 24May 31
Human clicks17k
QR scans4.7k
Bots filtered1.1k
Privacy mode on. No raw IP or User-Agent stored. Bots and prefetch are flagged, not counted as humans.
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With Analytics & privacy
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you get
- Track referrer, geo, device, and social-source inputs without storing raw IP or full User-Agent.
- Flag bots and obvious prefetch traffic so dashboard views and exports reflect real human engagement.
- Separate QR-origin traffic from ordinary short-link clicks without creating a second link object.
Availability
Privacy-aware analytics and core click reporting are available on every plan.
Retention windows, realtime analytics, unique clicks, and advanced breakdowns vary by tier. See pricing for the full analytics matrix.
How it works
1
Every redirect captures privacy-aware context
When a visitor clicks a short link, Nimriz records referrer, country, device category, and bot signals - without storing raw IP addresses or full User-Agent strings.
2
Aggregated metrics power your dashboards
Dashboards use pre-aggregated metrics instead of scanning raw event streams. Reporting stays fast and stable regardless of click volume.
3
QR scans and link clicks stay separable
QR assets encode a reserved `?nr=qr` marker so scan traffic is reportable as its own trigger type - no duplicate links required.
The privacy-aware event model
1 · Redirect
Visitor clicks a short link
go.acme.com/launch resolves at the edge.
2 · Privacy-aware capture
Context, not identity
CountryDeviceReferrerTriggerBot signal
Raw IPFull User-Agent
3 · Aggregated metrics
Dashboards stay fast
Pre-aggregated counts, no raw-event scans.
Everything included
Bot-aware inputs
Traffic classification preserves likely bot and prefetch signals so teams can filter noise instead of inflating campaign performance metrics.
Privacy-aware by default
Raw IP addresses and full User-Agent strings are never stored. Standard privacy may use daily-salted hashes, and strict privacy omits those hashes.
QR-aware attribution
Generated QR assets reserve the Nimriz-managed `nr=qr` classification so QR scans stay reportable as their own trigger type.
Referrer and channel mix
See which referrers and channels are driving traffic without building a separate attribution layer on top of your short links.
Geo and device breakdowns
Understand where clicks come from and what devices your audience uses - without tying that data to individual identities.
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 surface recent event context safely.
app.nimriz.com/analytics/acquisition
Trigger split
Link clicks72%
QR scans28%
Reporting posture
Summary metrics power dashboards; live views surface recent context safely.
Channel mix
No raw IP or full User-Agent in analytics events for new accounts.
Why privacy-aware analytics matters
- Analytics are tied directly to redirect behavior rather than stitched together from multiple weak signals.
- Bot classification and privacy-aware event design make dashboards more useful 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-aware default posture without giving up everyday performance reporting.
Related next steps
Ready to try it?
Analytics & privacy is available now
Create an account to try this workflow, then compare plans if you need higher limits or related controls.