Global postback vs per-offer postback — when one URL isn't enough

Global postback vs per-offer postback — when one URL isn't enough

Your tracker can accept conversions on one global URL or unique per-offer URLs. Choose by network behavior.

Use a global postback when:
— Networks reliably return your click_id — the tracker maps the conversion itself.
— You manage many offers from few networks and want one URL to configure.

Use per-offer (unique) postbacks when:
— A network can't pass click_id but can hardcode a per-offer URL.
— You need to set different payout/event values per offer at the postback.
— You're isolating one offer's conversions for debugging.

Tradeoffs to record:
— Global = configure once, but every network must honor click_id passthrough or conversions go null.
— Per-offer = bulletproof matching, but you manage a URL per offer — tedious at scale.
— A network that drops click_id silently is the #1 cause of "missing" conversions on a global setup.

Rule: global by default; switch a specific offer to per-offer the moment its click_id passthrough proves unreliable.

Save this SOP. Run this before every launch.