Nimriz
Marketing teams

Analytics integration

Teams already trust GA4, Segment, Amplitude, and warehouse-backed reporting. Nimriz lets short-link clicks and QR scans land in those systems directly, without leaving analytics teams stuck with UTM-only workarounds.

  • Send click and QR events into analytics tools your team already uses
  • Start with built-in mappings, then add filters or mapping overrides when needed
  • Keep reporting privacy-aware with redaction applied before outbound delivery
Start for freeAll use cases
Analytics destination feed

One canonical event layer, multiple reporting destinations, visible delivery health.

Server-side
Google Analytics 4
link.qr_scanned, utm_campaign, device_category
Healthy
Segment
link.qr_scanned, utm_campaign, device_category
Healthy
Amplitude
link.qr_scanned, utm_campaign, device_category
Mapped
Forwarded event
event_type: link.qr_scanned
domain_name: go.brand.com
utm_source: direct-mail
country: US

What you get

Direct analytics forwarding

Send click and QR events straight to GA4, Segment, Amplitude, and related tools without building a custom event relay first.

Built-in mappings

Named connectors ship with default event names and properties so teams can start with minimal setup and refine later.

Per-feed filtering

Route only the events that matter by touch type, domain, tag, space, geography, or field-level rules instead of sending everything everywhere.

Delivery monitoring

Watch success rate, recent failures, retries, and test-send results from the dashboard instead of debugging integrations blind.

How it works

Connect once, keep every downstream feed aligned

A single Nimriz event can populate multiple analytics destinations at once. The event is normalized first, then filtered, redacted, mapped, and dispatched per connector.

  • Choose a destination such as GA4, Segment, or Amplitude and add credentials from the integrations dashboard.
  • Start with the default mapping for that platform so event names and properties are ready immediately.
  • Create focused feeds by filtering on touch type, domain, tag, or campaign fields when different teams need different slices of traffic.
  • Use privacy mode and workspace policy controls so outbound payloads respect the same redaction posture as the rest of Nimriz analytics.
  • Validate a destination with test send before launch, then monitor delivery history once campaigns are live.
  • Scale into multiple destinations without rebuilding your tracking model for each platform.
Integrations & destinations featuresTrust & privacyFAQ
Example
Launch QR campaign
1. Visitor scans code on print mailer
2. Nimriz records link.qr_scanned with campaign metadata
3. GA4 receives campaign reporting event
4. Segment receives the same event for warehouse sync
Result
One QR interaction appears in both campaign reporting and downstream analytics ops.

Related use cases

Campaign links
Pair destinations with campaign links and QR traffic.
Client reporting & attribution
Use filtered feeds for client-specific reporting stacks.
Workflow automation
Trigger downstream workflows from the same event layer.

Ready to get started?

Create your account and start using Nimriz in minutes. Starter is free — no credit card required.

Start for freeView pricing