Analytics and CDP
LivePut branded link and QR activity into Amplitude charts with event properties mapped to your taxonomy, so growth and product teams can analyze campaigns next to product behavior.
Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.
Why Amplitude with Nimriz
Campaign links usually live outside product analytics, which leaves acquisition charts guessing. Nimriz forwards click, scan, and conversion events to the Amplitude HTTP V2 API with event properties shaped to match your existing taxonomy, so link-driven behavior shows up in cohorts and funnels you already trust.
Most link platforms ship one fixed payload and leave the cleanup to you. Nimriz lets you rename fields, drop fields, pin static values, and build template fields per action, so events arrive in Amplitude already matching the event taxonomy conventions your team agreed on.
Trigger on exactly the events you want: filter by event type, touch type, domain, space, tag, or country, and add field conditions such as utm_source equals google. Bot traffic is excluded by default, so Amplitude only sees activity worth analyzing.
Run multiple actions against the same Amplitude connection, each with its own filters and field mapping. Send all click activity through one action and keep a second action focused on conversions only, without duplicating credentials.
Parse, map, transform
Amplitude rewards consistent event property names. Map Nimriz fields into the property names your charts expect, and exclude anything your governance rules keep out.
1{2"event_type": "link.qr_scanned",3"event_id": "9f4d5dbd-c8b8-4c89-a080-b4f70fce8f53",4"timestamp": "2026-04-13T12: 15: 00.000Z",5"domain_name": "go.brand.com",6"short_code": "spring",7"short_url": "https://go.brand.com/spring",8"touch_type": "qr_scan",9"country": "US",10"device_category": "mobile",11"browser_family": "Mobile Safari",12"referrer_host": "instagram.com",13"utm_source": "direct-mail",14"utm_medium": "qr",15"utm_campaign": "spring-launch",16"variant_key": "B"17}
1{2"events": [{3"event_type": "QR Scanned",4"time": 1776082500000,5"device_id": "8f3a1c5d9e2b44a7",6"event_properties": {7"campaign_name": "spring-launch",8"data_source": "nimriz",9"link_label": "go.brand.com/spring",10"utm_source": "direct-mail",11"utm_medium": "qr",12"device_category": "mobile",13"country": "US"14}15}]16}
Every rule above is configured per action in the dashboard, with a default, raw, or empty base payload to start from. No code, no middleware, no waiting on an engineering sprint.
Under the hood
Forward click, scan, and conversion events to Amplitude with reviewed setup docs.
Connector access, mapping controls, and event volume depend on plan. Use pricing and setup docs to confirm the right path before configuring production delivery.
Guided setup
Add credentials in the destination catalog and run Test connection before anything is saved.
Choose triggering event types and narrow delivery by domain, space, tag, country, or field conditions.
Start from the default schema, then rename, exclude, pin, or template fields to fit the destination.
Send a dry-run test event, confirm the payload, then enable the action for live delivery.
Nimriz uses destination-aware payloads and privacy-aware analytics language. Do not send secrets, raw personal data, or provider credentials in public links.
Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.
Analytics privacy docsMore in Analytics and CDP
Forward click, scan, and conversion events from branded links and QR codes into GA4 with field mapping you control, so campaign activity lands beside the reporting your team already uses.
Route link, QR, and conversion events into a Segment source with per-action filters and field mapping, so your CDP receives clean track calls instead of raw shortener noise.
Forward link and conversion events into Mixpanel with per-action filters and property mapping, so campaign behavior is analyzed beside product events with names that fit your setup.
Connect branded link activity to PostHog Cloud or your self-hosted instance, with mapped properties and privacy-aware identifiers that respect how you run analytics.
Send mapped link, QR, and conversion events to your server-side Google Tag Manager container, then fan them out to any tag your measurement stack already governs.
