One image tag on the page a customer sees after paying. It runs the same rules as the postback and gives up two things to be a browser request: it can be replayed, and it cannot tell you much about what happened.
The tag
Put it on the confirmation page, with the click id you stored when the visitor landed.
It reads exactly the same parameters as the postback, goal included, and applies the same window, the same pricing and the same duplicate rule. The postback page is the reference for all of it.
What comes back
Always a 200 and a transparent pixel, whatever happened. A customer who has just paid should not be shown a broken image, so the outcome is in X-Wo-Status instead.
A goal key the offer does not define is reported in X-Wo-Goal as well, because a browser never shows anybody the body.
Never cached, by four headers. A cached conversion pixel is a sale reported once and then never again.
What the headers look like when something is wrong