Nimriz
Marketing teams

GA4 link tracking and analytics integration

Short-link clicks and QR scans live in a separate silo from GA4, Segment, and your CDP - unless you forward them. Nimriz sends those events server-side into the analytics destinations your team already uses, with privacy-aware field mapping and no custom relay to build.

  • Forward click, QR scan, and conversion events to GA4, Segment, Amplitude, and more
  • Built-in field mappings work out of the box with each platform's server-side ingestion API
  • Bot-flagged traffic excluded by default; no raw IP or full User-Agent forwarded
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

Most analytics stacks are built around page events and UTM parameters. Short-link clicks and QR scans sit outside that picture: they happen at the redirect layer, before your destination page ever loads, so they never appear in GA4 or your CDP unless something bridges the gap. The result is a reporting silo - campaign link activity in one dashboard, conversion funnels in another, with no shared event timeline.

Nimriz closes that gap by forwarding click, QR scan, and conversion events to your existing analytics and CDP destinations server-side. The forwarding happens asynchronously, off the redirect request path, so it never slows down the redirect itself. Each event carries a privacy-aware payload built from a canonical Nimriz schema that includes event type, short URL, domain, country, region, device category, browser, OS, referrer host, UTM fields, and A/B variant context.

Named connectors for Google Analytics 4, Segment, Amplitude, Mixpanel, PostHog, and Google Tag Manager (server-side) ship with built-in default mappings that translate Nimriz fields into each platform's expected property names. You connect with that platform's own server-side ingestion credentials and the events start flowing. On supported plans you can customize the mapping, add filters, and route different event slices to different destinations - all without touching the redirect configuration.

The payoff is link and QR data showing up where your team already reports. A single QR scan on a print mailer can appear in your GA4 custom events, your Segment pipelines, and your Amplitude project at the same time - with the same UTM context and campaign metadata that ties it back to the original campaign, plus the click-level fields that UTMs alone cannot carry.

Who it is for

Analytics and data lead

You want link click and QR scan activity in the same event stream as page-level data so you can build funnels, attribution models, and reports without manually joining two separate data sources.

Growth marketer

You run campaigns across email, print, social, and paid channels and need each link's click and QR data to land in GA4 or your CDP alongside UTM context so you can measure channel contribution in the tools your team already uses.

RevOps or CDP owner

You manage a Segment or Amplitude implementation and want short-link engagement events enriched with touch type, variant, and campaign fields flowing into your pipelines for downstream activation, cohort building, and attribution.

What you get

Direct analytics forwarding

Send click and QR scan events to GA4, Segment, Amplitude, Mixpanel, PostHog, and Google Tag Manager server-side without building a custom relay. Delivery runs asynchronously off the redirect path so forwarding events never adds latency to your redirects. Each destination receives the payload through that platform's own server-side ingestion API.

Built-in field mappings

Named connectors ship with a default mapping that translates Nimriz canonical event fields into each platform's expected property names, so GA4 receives a custom event with the right params and Segment receives a properly shaped Track call - all with zero additional configuration beyond your credentials. On supported plans you can rename, exclude, include, or set static values on any field to match your team's data model.

Per-feed event filtering

Control exactly which events reach each destination by filtering on event type, touch type (click vs QR scan), domain, tag, space, country, or field-level conditions such as "utm_source equals google". Bot-flagged traffic is excluded from all destinations by default so your analytics data reflects only genuine interactions. On supported plans you can combine include and exclude rules across all dimensions for precise routing.

Delivery health monitoring

View success rate, recent failures, and test-send results for each destination and action directly from the dashboard. Delivery is at-least-once, so you can spot and investigate failures without debugging blind or waiting for data gaps to surface in your reports. You can send a test event to any action at any time to verify the payload format before going live.

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 into a canonical schema, then filtered, redacted, mapped per connector, and dispatched asynchronously - all off the redirect path.

1
Plan

Choose a destination from the catalog (such as GA4, Segment, or Amplitude) and connect it with that platform's server-side ingestion credentials.

2
Publish

Add one or more actions under the connection to define which events trigger delivery and how fields are mapped to the target platform's property names.

3
Measure

Enable the destination and send a test event to verify the payload format before campaign traffic starts flowing.

  • Create focused feeds by filtering on touch type, domain, tag, space, or country when different teams need different slices of the same traffic.
  • On supported plans, customize the field mapping per action: rename canonical fields, exclude fields, add static values, or combine fields into composite properties.
  • Monitor delivery health per destination and per action from the integrations dashboard - success rate, recent failures, and test-send results are all visible without leaving Nimriz.
Integrations and destinationsTrust and privacyFAQ
Example
Print QR campaign flow
1. Visitor scans QR code on print mailer
2. Nimriz records link.qr_scanned with utm_campaign, device_category, country, variant_key
3. GA4 receives nimriz_link_click custom event with ep.utm_campaign and ep.touch_type
4. Segment receives "QR Scanned" Track call with all campaign properties
5. Amplitude receives "Link Clicked" event with event_properties including variant and UTM fields
Destination field mapping (sample)
Nimriz fieldGA4SegmentAmplitude
event_typeevent_name: nimriz_link_clickevent: "Link Clicked"event_type: "Link Clicked"
short_urlep.short_urlproperties.short_urlevent_properties.short_url
utm_campaignep.utm_campaignproperties.utm_campaignevent_properties.utm_campaign
countryep.countryproperties.countryevent_properties.country
ip_hashclient_id (pseudonymous)anonymousId (pseudonymous)device_id (pseudonymous)
Result
One QR interaction appears in GA4 custom events, Segment pipelines, and Amplitude - with the same UTM and campaign context, plus click-level fields that page analytics alone cannot carry. Privacy-aware: no raw IP or full User-Agent forwarded to any destination.

Setup

  1. 1
    Connect a destination with its server-side credentials
    Open Integrations in the Nimriz dashboard and browse the catalog. Choose a named connector such as Google Analytics 4, Segment, or Amplitude and enter the credentials that platform requires for its server-side ingestion API - for GA4 that is your Measurement ID and API Secret; for Segment it is your HTTP Source write key; for Amplitude it is your project API key. Save the destination. See the GA4 setup guide and integrations overview for step-by-step credential instructions per platform.
  2. 2
    Add an action and choose which events to forward
    Under the destination, add an action and set its event triggers. Choose the event types (click, QR scan, conversion) and apply any include or exclude filters you need - for example, forward only QR scan events, or only events from a specific domain or campaign tag. Bot-flagged traffic is excluded by default. On supported plans you can add field-level conditions such as forwarding only events where a UTM campaign is set.
  3. 3
    Review the field mapping and customize if needed
    Named connectors use a built-in default mapping that translates Nimriz canonical fields into the target platform's property names automatically. Review the payload preview to confirm event name and properties look correct for your analytics setup. On supported plans you can rename fields, exclude fields you do not need, add static values, or adjust which canonical fields are included in the outbound payload.
  4. 4
    Send a test event and confirm delivery, then enable
    Use the Send test to this action button to route a test payload to the destination. For GA4, Nimriz routes test events to the Measurement Protocol Validation Server so you can verify the event format before any live traffic is affected. Check the delivery health view to confirm the test succeeded, then enable the destination. Once enabled, events from live redirects start forwarding asynchronously in the background.

What good looks like

Before
  • Short-link clicks visible only in the Nimriz dashboard, invisible in GA4 or your CDP
  • QR scans not tracked in Amplitude or Segment at all
  • UTM context forwarded to destination page but click-level and variant context missing from analytics events
  • Custom relay or webhook plumbing required to get link events into GA4
After
  • Clicks and QR scans appear as custom events in GA4 with UTM params and device context
  • Segment and Amplitude receive the same events with variant_key and campaign fields attached
  • Privacy-aware delivery: no raw IP or full User-Agent forwarded to any destination
  • Delivery health visible per destination; test-send verifies format before going live

Frequently asked questions

Does this replace UTMs?
No. UTMs live on your destination URL and are captured by GA4 and your other analytics tools the same way they always were. Nimriz captures those UTM values at click time and forwards them as event fields alongside the click-level context (event type, short URL, domain, country, device, touch type, A/B variant) that UTMs alone cannot carry. The two work together rather than one replacing the other. See the UTM parameters guide for more detail.
Which analytics and CDP platforms are supported?
The named analytics and CDP connectors are: Google Analytics 4, Segment, Amplitude, Mixpanel, PostHog, and Google Tag Manager (server-side). Each connector uses that platform's own server-side ingestion API and ships with a built-in default field mapping. Plan availability varies by connector - see the integrations overview and your plan details. Ad platform conversion destinations (Meta, Google Ads, LinkedIn, TikTok) are separate from this analytics connector set.
What data is forwarded? Does Nimriz send raw IP addresses?
Nimriz never forwards raw IP addresses or the full User-Agent string to any destination. Privacy redaction is applied to the canonical event payload before field mapping runs, so no mapping configuration can bypass it. In standard privacy, a daily-salted pseudonymous hash of the visitor IP is available as a client or anonymous identifier. In strict privacy, that hash is null and city is omitted - only country and region are forwarded. The forwarded field set includes event type, short URL, domain, country, region, device category, browser, OS, referrer host, UTM fields, and A/B variant key. See analytics and privacy for the full privacy posture.
Is bot traffic forwarded to my analytics destinations?
Bot-flagged traffic is excluded from all destinations by default. Nimriz uses bot signals to flag likely automation and prefetch traffic, and those flagged events are blocked before delivery so your analytics data reflects genuine interactions. You can explicitly disable bot exclusion for a specific action if your workflow requires it, but the default posture keeps bot signals out of your downstream reporting.
Can I send link event data to my data warehouse?
Nimriz does not have a native data warehouse connector. The practical path is to route events through a CDP like Segment (which has warehouse sync built in) or to use a Generic HTTP destination to forward events to any endpoint that feeds your warehouse pipeline. This approach works well for teams that already have Segment or a similar CDP as the hub in their data stack.
Does forwarding events slow down my redirects?
No. All outbound delivery runs asynchronously, off the redirect request path. Nimriz enqueues the event in the background after the redirect response is sent, so the visitor reaches the destination URL at full speed regardless of how many destinations are configured or how long any destination API takes to respond.
What plan do I need to use analytics destinations?
Destination availability depends on your plan. The GA4 connector is available on Growth and above. Segment, Amplitude, Mixpanel, PostHog, and GTM server-side connectors, along with the Generic HTTP destination, are available on Professional and above. Advanced field mapping customization and field-level filtering conditions are also on supported plans. See the integrations and destinations feature page and your plan details for current limits and event volume caps.
Can one destination have multiple actions with different filters?
Yes. Each destination connection can hold more than one action. For example, you can keep a broad action that forwards all click and QR scan activity to a GA4 property and add a second action under the same connection that forwards only conversion events. Actions can have independent filters and field mappings, so different teams or reporting needs can be served without creating duplicate destination credentials.

Related use cases

Campaign links
Pair analytics destinations with campaign links and QR traffic for end-to-end reporting.
Conversion tracking
Track leads and sales with server-side conversion events tied to the same short link.
API and workflow automation
Create and manage links and destinations programmatically from your own tooling.

Deeper reading

Integrations overview: destination model and setup flowGA4 integration guide: credentials, mapping, and test eventsIntegrations and destinations feature referenceAnalytics and privacy: what is forwarded and what is redactedGlossary: event forwardingBlog: server-side analytics forwarding for link campaigns

Ready to get started?

Create your account and start with the Starter workflow. Compare plans when you need higher limits or supported-plan capabilities.

Start for freeView pricing