Signed Conversion API requests
Send outcome events from your backend with a dedicated signing secret so Nimriz can verify authenticity without relying on client-side scripts.
Conversion trackingProfessional+
Track conversions after the click
Measure what happened after the redirect with signed server-side Conversion API requests tied back to the originating short link. Record leads, sales, refunds, cancellations, and reversals without depending on a client-side pixel.
Server-side
Conversion API
5 core
Outcome types
Up to 30 days
Attribution window
app.nimriz.com/analytics/go.brand.com~demo · conversions
go.brand.com/demo
Spring launch campaign
Attributed conversions · 30d
1,284
Attribution rate
38.2%
Click to conversion
LiveClick
Click token
Conversion API
Outcome
Short link redirect
go.brand.com/demo → brand.com/signup
302 redirect, routing preserved
Signed, server-side. Outcomes are verified from your backend with the Conversion API signing secret. No client pixel required.
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With Conversion tracking
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you get
- Track leads, sales, refunds, cancellations, and reversals on the same short-link record instead of rebuilding attribution in a separate tool.
- Use signed server-side Conversion API requests when browser pixels are blocked, stripped, or unavailable.
- Keep redirects safe by suppressing click-token appending on signed or query-sensitive destinations when mutation would be risky.
Availability
Conversion tracking, conversion reporting, and the signed Conversion API are included on Professional and Enterprise.
Query-sensitive destinations suppress click-token appending when a safe redirect requires it. Workspace access may still need to be enabled on eligible plans.
How it works
1
Enable conversion tracking on the link
Turn conversion tracking on for the links you want to measure. Nimriz appends a click token when the destination is safe to modify, keeping the redirect path explicit and reliable.
2
Capture the click token and send a Conversion API request
Your landing page or backend stores the click token, then your server sends a signed Conversion API request to Nimriz when a lead, sale, refund, cancellation, or reversal occurs.
3
Review attributed outcomes in analytics
Conversion reporting ties the outcome back to the originating short link, including experiment and routing context where available, so teams can compare clicks to business results.
Everything included
Five immutable outcome types
Track leads, sales, refunds, cancellations, and reversals as distinct events. Negative follow-on outcomes do not overwrite the original conversion.
No client pixel required
Attribution still works in email clients, embedded contexts, and privacy-restricted environments where third-party scripts or pixels are not dependable.
Query-safe click tokens
If a destination looks signed or query-sensitive, Nimriz suppresses click-token appending rather than risk breaking the redirect destination.
Variant-aware attribution
When an experiment drove the click, conversion reporting can preserve the routed variant context so teams can compare clicks to actual business outcomes.
Export-ready reporting
Conversion totals, attribution rate, and per-link outcome reporting stay available in the same analytics model teams already use for click reporting and exports.
How click-to-conversion attribution works
A campaign team can keep click measurement and downstream business outcomes on the same short-link record instead of stitching multiple tools together later.
Click
Visitor opens go.brand.com/demo and lands on your signup page with a safe click token.
Capture
Your app stores that token on the lead, order, or account record when the visitor converts.
Conversion API
Your backend sends a signed lead or sale event back to Nimriz using the Conversion API signing secret.
Report
The conversion appears under the original link with attribution rate, outcome type, and routed context where available.
POST api.nimriz.com/v1/conversions
Conversion API · signed request
server-sidePOST /v1/conversions
Authorization: Nimriz-HMAC-SHA256 t=1718…,v1=8c4f…a91
{
"click_token": "nrc_8f3a92c4e7",
"type": "sale",
"value": 149.00,
"currency": "USD",
"event_id": "ord_5521"
}
Verifying signature
Attributed to go.brand.com/demo
Why dedicated conversion tracking matters
- Click counts alone cannot tell you whether a campaign generated leads, revenue, or refunds after the redirect.
- Server-side Conversion API requests let attribution survive ad blockers, privacy restrictions, and script-hostile surfaces where pixels fail.
- Query-sensitive destinations need an explicit safety model so measurement does not come at the cost of broken redirects.
- Keeping outcomes on the same short-link record gives growth and analytics teams a cleaner path from campaign click to business result.
app.nimriz.com/analytics/go.brand.com~demo · outcomes
Outcome ledger
One click token · click cvt_5521
Lead–
Signup completedMar 2 · 14:08
Sale+$149.00
Order ord_5521Mar 3 · 09:41
Refund−$149.00
Appended, original keptMar 9 · 16:22
3
Events
$0.00
Net value
Preserved
Original
Ready to measure outcomes?
See what happens after the click
Turn on conversion tracking for a link, send a signed event from your backend, and watch outcomes attribute back to the same short link.