Two logs, two questions.
- The tracking log answers “did the request arrive and what did it do”.
- The conversion log answers “what exists in PalDock now and did it produce a payout”.
Start with the tracking log when something is missing, and move to the conversion log once you know the request arrived.
Tracking log
Records every S2S postback, pixel, and Tracking API request. One row is one flow, and expanding it shows all the individual requests inside.
What appears in it:
- S2S postback: requests received from advertisers.
- Tracking API: requests PalDock sends to advertisers.
- Tracking pixel: requests fired by pixel placements.
- Affiliate postback: outgoing requests that affiliates configured themselves. Affiliates see only their own.
What each row tells you:
- State: whether the request was accepted or refused.
- Details and reason: the refusal reason, or the processing outcome when it was accepted.
- The requests inside the flow, when one incoming request triggered several calls.
For what each outcome means and what to do about it, see Tracking errors and reasons.
Conversion log
A consolidated view of every conversion PalDock holds, whatever created it: postback, pixel, Tracking API, manual import, or PalDock itself.
What each row tells you:
- Origin ID, Send ID, Conversion ID, Transaction ID: the whole chain, so you can follow one journey end to end. See Conversion IDs explained.
- State: whether the conversion is valid, and whether it produced a transaction.
- Transactions: how many were created and under which commission. One conversion can have several.
Why a conversion produced no transaction
- The conversion matches no commission, usually because of the conversion type.
- The commission is inactive or outside its active period.
- The recurrence limit was reached.
- It was deduplicated on the advertiser’s external ID.
- The conversion is not valid, for example refused by validation, by a filter, or by the Pingtree.
- The conversion was created by a commission. Those never trigger commissions again. See Transaction type.
Full list of states and what they mean: Tracking errors and reasons. Commission side: How PalDock picks a commission.
Conversions you did not create
Some rows in the conversion log were created by PalDock, not by a tracking request.
- A commission whose transaction type differs from the conversion creates the matching conversion and puts the transaction there.
- The original conversion then carries no transaction, and the new one does.
This is expected. Look at the transaction, not at the conversion that triggered it.
Which log to use
- Debugging a request: tracking log. Is it there, was it accepted, what did it say.
- Confirming a result: conversion log. What was recorded, is it valid, how many transactions came out of it.
