Attribution model

How click-time partner snapshots, conversion attribution, negative outcomes, and privacy posture work.

Attribution model

Nimriz Partners uses link-native attribution. Partner and program context starts with the partner assignment on a short link, then becomes click-time context when the visitor opens the link.

This model keeps reports explainable because historical rows use what was true at click time instead of relying only on current partner or program labels.

Flow diagram of partner attribution: a partner is assigned to a link, a visitor click creates a click-time snapshot of partner and program context, the snapshot feeds traffic reporting, and — when the nim_ct token is captured and conversion tracking is on — a signed conversion event becomes an attributed outcome row that powers conversion reporting and the commission-ready CSV export; later partner or program edits do not rewrite click-time snapshots — From assignment to export: every report row traces back to what was true at click time.

Click-time snapshots

Eligible partner clicks can capture:

Partner ID, display name, and key.
Program ID, name, and key.
Partner assignment ID.
Assignment timestamp.
Privacy-safe reporting context such as trigger type, source, referrer, country, and device where available.

Raw IP addresses and full User-Agent strings are not stored in partner reports or exports.

Conversion attribution

Partner conversion reporting uses Nimriz conversion tracking.

When a conversion is attributed to a click that carried partner context, the partner and program context can be copied into the attributed outcome row for reporting and exports.

Supported outcome types include leads, sales, refunds, cancellations, and reversals.

Negative follow-on events

Refunds, cancellations, and reversals remain visible as negative follow-on outcomes. They do not erase the original lead or sale.

This helps teams reconcile partner outcomes outside Nimriz without losing the event trail.

Privacy posture

Nimriz Partners follows Nimriz analytics privacy rules:

No raw IP addresses in partner reports or exports.
No full User-Agent strings in partner reports or exports.
Partner reports prefer click-time context for historical facts.
Conversion attribution uses signed Conversion API events.

Limitations

If a destination is query-sensitive, Nimriz may avoid appending a click token to protect the redirect destination. Traffic reporting can still capture partner context for the click, but conversion attribution may need another supported path.

Partner assignment changes do not backfill historical clicks.