Mistake: global postback silently overriding offer-level postback

Mistake: global postback silently overriding offer-level postback

Failure mode: you set a workspace-wide global postback, then add a custom one on a specific offer. Depending on tracker precedence rules, one silently overrides the other — and you cannot tell which fired until conversions land in the wrong place.

Fix — 4 steps:
— Know your tracker's precedence: does offer-level override global, or does global always fire? Read the docs, do not guess.
— Use global postbacks only for networks that are truly identical across every offer. Anything custom belongs at offer level.
— Avoid stacking both on the same offer unless you have confirmed the tracker fires them in the order you expect.
— Label each postback with its scope in the name so you can see at a glance what is global vs offer-specific.
— After any postback change, re-test the affected offers — a global edit can break offers you did not touch.

Verify: fire a test conversion on an offer with both scopes present and confirm exactly the intended postback(s) fired, once each.

Save this SOP. Run this before every launch.