Understanding postbacks
See who reports a sale, why two systems may send messages, and which visit ID each one needs.
Reviewed 24 September 2026 · MyCPANetwork team
Explain who sends each result message and how it connects to the right visit.
Before you start
In lesson 8, you saw a visit and a result in OfferDaemon. Here you will see how the two records connect. One example offer and one publisher are enough. You do not need to write code.
The dashboard screenshots below come from a controlled test in the demo network on 22 September 2026. Its advertiser callback was simulated. They show OfferDaemon receiving and recording a request; they do not show a real advertiser sending one or a publisher tracker receiving one.
What is a postback?
A postback is an automatic message between two systems. After an agreed action, such as a sale, the advertiser sends your network the visit ID and what happened. The visitor does not need to come back to your site for this message to arrive.
Think of it as a delivery note: “The action linked to this visit happened.” Your network still has to find the visit and apply the offer rules. The message does not mean that the result was approved or that anyone was paid.
Follow one visitor from click to result
Imagine a publisher uses its own tracking software and sends one visitor to your offer. There can be two messages: the advertiser reports the action to your network; your network may then report it to the publisher's software.
- The publisher sends a visitor. Its link may carry the ID from its own tracker. Call this P-204.
- OfferDaemon records the visit. It creates a different ID, N-861, and passes it to the advertiser's page.
{click_id}in the offer URL becomes the real value N-861. - The advertiser saves N-861. When that visitor completes the agreed action, the advertiser can report which visit produced it.
- The advertiser messages your network. It sends N-861, an event such as
sale, and a reference for that sale to your network's/postbackaddress. - OfferDaemon finds the visit. It can now find the offer and publisher. If it accepts the message, it records a conversion. That conversion may still wait for approval.
- Your network may message the publisher. If the publisher saved a receiving URL, OfferDaemon can send it a separate message with P-204. The publisher's tracker uses P-204 to find its own visit.
Remember the direction: visitor → network → advertiser. The result comes back advertiser → network. Only if the publisher needs it, a second message goes network → publisher's tracker.
- Advertiser postback: the advertiser or its tracker sends a message to your OfferDaemon network. OfferDaemon normally needs its own
click_idfrom the destination URL. - Publisher postback: OfferDaemon sends a different message to the publisher's external tracker. That tracker normally needs its own
external_click_idfrom the original tracking link.
The publisher postback is optional. OfferDaemon already records the conversion for the publisher without it; the extra message is for a publisher who wants the result in another tracking system.
Three IDs with three jobs
- Network
click_id: OfferDaemon creates this at click time. It uses the ID to match the advertiser's later message to its click record. - Publisher
external_click_id: the publisher's tracker creates this, if one is used. That tracker uses it to match OfferDaemon's later callback to its own click. - Advertiser
tx_id: the advertiser creates this for the action. It helps identify one transaction and avoid counting an ordinary retry twice.
These are three different values. The publisher may put its own ID in sub1 instead of external_click_id if both sides agree how to use it. The advertiser still needs to return OfferDaemon's click ID for the normal test. OfferDaemon has a special way to report a result without a click ID, but that cannot show which recorded visit produced it. Start with the click-based method.
Quick check: A sale comes back from the advertiser with N-861. Which ID would the publisher's own tracker recognize? P-204, because that tracker created it. The two messages can describe the same sale while using different visit IDs.
The advertiser-to-network message in OfferDaemon
Open Settings → Postback URL in the admin dashboard. Your postback URL is the address to give the advertiser. Click Copy. The advertiser adds this address to its own result-reporting settings. Ask exactly which value in its system contains the OfferDaemon click ID; different systems give that value different names.
A simplified, non-live example after the advertiser has substituted real values is:
https://network.example/postback?click_id=N-861&event=sale&tx_id=ORDER-42
Here click_id answers “which visit?”, event answers “what happened?”, and tx_id answers “which sale?”. These are sample values, not a live URL. For a fixed-rate offer, the rates already saved in OfferDaemon can be used without amount. Percentage-based offers need an amount; check the OfferDaemon parameter reference before setting up another rate model.
After the advertiser sends the message, open Postback Log. accepted means OfferDaemon processed it. duplicate means an ordinary retry did not create another conversion. Both may show HTTP 200, which only says the web request reached the service. Read the result, then open Conversions to check the offer, publisher, amounts and approval status.
The optional network-to-publisher message
The publisher's receiving URL is a different address. In OfferDaemon, the publisher can save it under Profile → Conversion Postback → Your postback URL. For example, a publisher might provide this template:
https://publisher-tracker.example/postback?clickid={external_click_id}&payout={payout}&status={status}
OfferDaemon replaces the words in braces with real values, then requests the publisher's URL. In this example, clickid must become the publisher's P-204, not your network's N-861. If the publisher did not send P-204 in the original link, its tracker may not recognize the result. Ask the publisher to check that its tracker received and matched the message.
This second message is sent when a publisher conversion is created, even if it still says pending. Approving or rejecting it later does not automatically send a new status message. Sending happens separately from recording the conversion, and delivery is not guaranteed. Ask the publisher to check its tracker and compare records if numbers differ. The publisher postback guide lists the values you can include.
One confusing name: in the message from the advertiser, payout= is another name for amount=. It does not change the publisher's rate. In the message to the publisher, {payout} means the amount assigned to that publisher. Check which direction you are working on before using it.
Test the two directions separately
- Ask the advertiser to save the OfferDaemon click ID from a permitted test click and trigger the agreed test action through its own system. Agree beforehand how that event will be excluded from normal billing.
- In OfferDaemon, compare the click ID in Clicks, the outcome in Postback Log, and the publisher row in Conversions. A
pendingconversion means it awaits approval; it is not a failed postback. - If the publisher uses an external tracker, confirm it sent its own click token in the tracking link and saved a valid callback URL. Then ask it to find the matching callback and conversion in that tracker.
If you only open a completed postback URL yourself, you test OfferDaemon's receiving path. You have not tested whether the real advertiser stored and returned the ID. The controlled screenshots on this page show that limited kind of test. Follow the full click-to-conversion walkthrough when you need exact screen steps.
Common mix-ups
- “The click appeared, so the conversion must appear.” A click proves the visit was tracked. The advertiser still has to report the completed action with a matching ID.
- “The advertiser can send its own click ID instead.” OfferDaemon needs the ID it created, unless you deliberately use and validate the separate clickless path.
- “The postback returned 200, so the publisher was paid.” A duplicate can also return 200; a new conversion can remain pending; payment is a later business step.
- “The publisher callback is the advertiser postback.” They have different senders, receiving URLs and often different click IDs.
- “The Postback Log proves the publisher got the result.” It covers the incoming request. Check the publisher's receiving tracker for the optional outgoing request.
Check what you learned
Try to explain each idea in your own words, then tick to see a one-sentence reminder.
The click goes through the network to the advertiser; the advertiser reports a result to the network, which may separately notify the publisher's tracker.
The advertiser returns the unchanged ID from the offer destination so OfferDaemon can find the original visit.
A publisher using its own tracker sends its visit ID and gives the network a receiving URL so it can match a later result.
An accepted incoming message can create a result that still awaits approval, while delivery to the publisher is a separate event.
The advertiser's message must match an OfferDaemon click, and any publisher callback must be confirmed in the publisher's own tracker.
0 of 5 ideas reviewed
Your progress stays in this browser.Next step
Use the weekly operating routine to keep click, conversion and partner records aligned after the pilot starts.
Want a hand with this step?
Get practical setup help from the team behind OfferDaemon.