Analytics definitions

Nimriz analytics are designed to be useful without storing more personal data than necessary. This guide explains what the main fields mean and why some numbers may differ from other tools.

Core metrics

Clicks

Clicks are redirect events that Nimriz recorded for a short link.

When the product says Total clicks, that number includes both:

• canonical short URL clicks
• QR-origin redirects classified from the reserved ?nr=qr marker

QR scans

QR scans are the subset of total clicks where the redirect was classified as QR-origin traffic.

This means QR scans are part of Total clicks, not a second competing total.

Bots

Some traffic is flagged as bot or automation traffic. This helps you separate human engagement from scanners, previews, or scripted requests.

Referrer

The referrer is the site or app that sent the visitor. Referrer data is best-effort, not guaranteed. Many privacy settings, apps, and browsers reduce or remove it.

Country, browser, and device category

These fields are derived from request metadata and user-agent parsing. They are useful for trends, but they should be treated as approximate classifications rather than perfect identity data.

Why your numbers may not match another tool

• Some tools count page views, while Nimriz counts redirect events.
• Bot filtering rules differ across platforms.
• Referrer data can disappear between apps, browsers, or privacy settings.
• Reporting views can lag behind raw redirect activity for a short period.

Privacy mode expectations

Privacy-aware analytics can still show campaign-level trends, but they intentionally avoid storing raw IP addresses or full user-agent strings.

This means:

• some visitor-level analysis may be reduced
• some dimensions can be less precise than in invasive analytics tools
• privacy-preserving aggregation is favored over fingerprint-style tracking

Freshness and lag

Recent traffic may appear in one part of the product before it appears in every dashboard breakdown. When investigating a campaign, allow for short reporting lag before assuming data is missing.

Interpreting bots

Bot traffic does not always mean abuse. Common bot sources include:

• messaging app link previews
• security scanners
• social crawlers
• QA or uptime checks

If a campaign looks inflated, compare total clicks with human-only filtered views when available.

Best ways to use Nimriz analytics

• Compare relative performance across links or campaigns instead of expecting identity-grade attribution.
• Use consistent UTM conventions so referrer and campaign grouping stay cleaner.
• Review both total traffic and bot-filtered traffic before making decisions.

When to contact support

Contact support if:

• a link is receiving live traffic but shows no analytics after reporting lag should have passed
• a campaign suddenly appears to be all bot traffic and that seems incorrect
• a field is empty for nearly every click on a channel where you expect it to exist

Include the short link, the time window you checked, and screenshots of what looks wrong.