⚠️ This setting is only available for workspace commissions from advertisers, because partner commissions reflect those values.
Transaction type sets what kind of transaction a commission creates. You can choose any conversion type, including custom ones. By default, the system has the following transaction types.
| Conversion type | PalDock | Tracking | Transaction Type |
|---|---|---|---|
| Sale | ❌ | ✅ | ✅ |
| Prospect | ❌ | ✅ | ✅ |
| Send | ✅ | ❌ | ❌ |
| Lead | ✅ | ❌ | ❌ |
| Click | ✅ | ❌ | ❌ |
| View | ✅ | ❌ | ❌ |
The default
If you leave the setting empty, the transaction gets the type of the conversion that triggered the commission. A sale conversion creates a sale transaction, a prospect conversion creates a prospect transaction.
Why you would change it
- To pay for a different event than the one that arrived, for example paying a prospect commission on an incoming sale.
- To split payouts inside one offer, with one commission for prospects and another for sales.
- To group several custom conversion types into one transaction type for reporting.
Combine it with the other commission conditions so each commission catches the right conversions. See Prospect + Sale vs Pending Sale for a worked example.
When the type differs from the conversion
A transaction always belongs to a conversion of the same type. When the transaction type is different from the type of the conversion that triggered the commission, PalDock creates the missing conversion for it.
- PalDock first looks for an existing conversion of that type under the same original conversion. If it finds one, the transaction is added there.
- If there is none, PalDock creates a new conversion of that type and puts the transaction under it.
- The new conversion inherits the data of the conversion it came from, so the affiliate, offer, and IDs stay the same.
- The new conversion never triggers commissions again, so this cannot loop.
- One commission creates one transaction on that conversion. If the same commission runs again for the same conversion, no second transaction is added.
What you see as a result:
- Reports count the new conversion under its own type.
- An extra conversion appears in the conversion log, and the original conversion carries no transaction.
- The workspace transaction and the partner transaction both sit on this new conversion.
