Postbacks Are Not Coming: Diagnosis Checklist

If conversions do not appear in Adset or do not reach the traffic source — go through the steps below in order.

Let’s recall the chain: when clicked, Adset creates an internal event_click_id and passes it to the CPA network (usually as sub1 or clickId); upon conversion, the partner calls the postback URL and returns this ID; Adset finds the click and sends the event to the source using the saved ext_click_id. More details: How Postbacks Work: In Simple Terms

Step 1. Check the postback URL with the partner

The incoming postback Adset accepts the parameters clickId, status, revenue, currency, externalId. Example of a global postback URL:

https://adset.pro/postback/?clickId={ref_id}&status={status}&revenue={sum}&currency={currency}

{ref_id}, {status}, {sum}, {currency} — macros of the partner, each CPA network has its own.

There are two approaches possible:

• One global URL — the status comes through a macro. In the settings of the partner program in Adset, all possible status values must be added.
• Separate URLs for each status — the value of status is hardcoded in the URL and must exactly match the value from the postback status template.

More details: Conversion Statuses and Postback Setup

Step 2. Check that the click id is passed in the offer link

In the parameters of the offer link (paramTemplate), the outgoing tracker macro {event.event_click_id} must be present — this is the value that the partner is obliged to return in the postback in the clickId parameter. If the macro is missing or the partner returns its own ID instead of the one passed, Adset will not be able to find the original click and the conversion will not be linked.

Step 3. Check the postback logs

Open the actions menu (⋮) for the pixel → Logs. Each entry has a status: success (green), error (red), pending (yellow). Use filters by ClickId, status, trigger (Deposit — accept, Registration — hold, etc.) and period; in the columns "Request Data" and "Response Data" you can see the exact request and response from the external server.

A special case is the Ignored status in the pixel logs: if in the campaign "Conversion share for the source" is less than 100% (or the payout share nullifies revenue), some postbacks to the source pixel are marked as Ignored and not sent. This is a setting, not an error.

More details: Viewing Postback Logs

Step 4. Typical errors

• Incorrect network macro — a raw string like {ref_id} comes in clickId: the partner did not substitute the value. Check that the macros used in the postback URL are indeed from your CPA network.
• Trimmed or modified click id — the value must return exactly as Adset sent it in the offer link.
• Incorrect status value — the string in the postback (lead, sale, reg…) does not match the values in the partner program's status template. Configure the status mapping in the network settings in Adset and do not mix different names without setting up correspondences.
• Errors sending to the source (visible in logs): Invalid ext_click_id — check the mapping of traffic source parameters; Invalid OAuth access token — update the Access Token in the pixel settings; Timeout / Connection refused — check the postback URL and retry sending; Purchase event requires positive revenue and currency — the partner did not pass revenue/currency, if necessary, set a default value in the offer settings.

Step 5. For pixels — test events (CAPI)

Facebook CAPI is checked through Test Events: copy the Test Event Code in Facebook Events Manager (pixel → Test Events → Test Server Events), in the tracker open the menu (⋮) of the pixel → Test, paste the code, select events and click Run Test. For each event, the result OK/Failed will be displayed, and in Events Manager, events will appear with the label "Server".

More details: CAPI Check (server-to-server) — Sending Test Events

Step 6. When to contact support

If steps 1–5 have been completed and postbacks still do not come, contact support and attach:

• the name of the partner network, offer, and campaign;
• the postback URL configured with the partner, and an example of a real call;
• clickId of the problematic conversion and the event time;
• screenshots of the logs (status, request and response data).

How statuses are related

In CPA templates, partner statuses are mapped to internal tracker events: for example, lead → hold, sale → accept. Registrations and deposits are displayed in statistics as CPA_HOLD and CPA_ACCEPT events.