To better understand how conversions and transactions are processed in PalDock, you have access to tracking logs and a separate conversion log. These logs help you identify where a request came from, whether it was processed correctly, and if it resulted in a transaction.
Tracking Logs
Tracking logs record all S2S postback, pixel and Tracking API requests. Each row represents one full tracking flow.
When expanded, you can see all underlying requests that belong to this flow.
Types of tracking logs
- S2S Postback tracking – requests received from the advertiser
- Tracking API – requests PalDock sends to the advertiser
- Tracking Pixel – requests triggered by pixel placements
- Affiliate postback – postbacks that affiliate partners created themselves
Affiliate postbacks are always outgoing requests, but unlike Tracking API calls, they are tied directly to a specific affiliate who configured them. Affiliates can view only their own postbacks created by them.
What you can see in tracking logs
- State – shows whether the request was accepted or rejected
- Details / Reason – if rejected, shows the rejection reason; if accepted, shows the processing status (processed, forwarded, etc.)
- Expandable details – for each flow you can expand and see all requests within it (useful when multiple requests were triggered for one flow)
This makes it clear:
- Which requests failed
- Which requests successfully created a conversion
Conversion Log
While tracking logs show raw requests, the conversion log gives you a consolidated view of all conversions recorded in PalDock.
A conversion can originate from:
- Postback tracking
- Tracking API
- Pixel tracking
- Manual import
What you can see in the conversion log
- Conversion ID – unique PalDock identifier (a single conversion can have multiple Transaction IDs if more than one commission applies)
- State – shows whether the conversion generated a transaction or not
Why a conversion might not generate a transaction
- It did not meet the conditions of a commission conditions
- It was filtered out by deduplication
- It was rejected due to a recurrence limit
Multiple transactions from one conversion
A single conversion may trigger multiple transactions (e.g. when more commissions apply). This will be visible in the conversion log, so you always know how many transactions were created and under which commission.
✅ Tip: Use the tracking logs when you need to debug the technical flow of requests, and the conversion log when you need to confirm business outcomes (which conversions became transactions, why, and how many).
