Conversion tracking
Clicking a short link is only the first event. Nimriz lets you track what happens next — leads, sales, refunds, and reversals — with a signed server-side Conversion API tied to the same short link record.
- Server-to-server Conversion API requests — no client pixel, no third-party script dependency
- Leads, sales, refunds, cancellations, and reversals tied to the originating click
- Works in ad-blocked, email-client, and iframe contexts where pixels fail
Track what happened after the redirect without a client-side pixel dependency.
What you get
Your server sends a signed request to Nimriz when an outcome occurs through the Conversion API — no cookie or pixel match required.
Track leads, sales, refunds, cancellations, and reversals — all attached to the originating short link.
Works where browser pixels fail — ad blockers, email clients, and restricted iframe contexts.
Each short link is its own attribution unit — see which placement drove outcomes, not just clicks.
How it works
Attribution that survives the click
When an outcome occurs on your end, your server sends a signed Conversion API request to Nimriz. Attribution ties back to the originating click event on the short link — no cookie match, no third-party dependency.
- Each redirect event generates a click record; your server receives a signed click token linking the conversion back to the originating link.
- Conversion API requests are signed so Nimriz can verify authenticity — protecting against spoofed conversion events.
- Works alongside privacy mode — click events can omit IP and User-Agent while still recording outcomes.
- Refunds and reversals can be recorded after the fact so conversion data stays accurate when deals cancel.
- Outcome data stays tied to the short link record — no separate attribution tool needed to connect campaign clicks to downstream results.
Related use cases
Ready to get started?
Create your account and start using Nimriz in minutes. Starter is free — no credit card required.