Conversion types are the events PalDock records. Every conversion has exactly one type, and it decides which commissions can apply and which pixel is used. See table below to know which types are created by which event.
| Conversion type | PalDock | Tracking | Transaction Type |
|---|---|---|---|
| Sale | ❌ | ✅ | ✅ |
| Prospect | ❌ | ✅ | ✅ |
| Send | ✅ | ❌ | ❌ |
| Lead | ✅ | ❌ | ❌ |
| Click | ✅ | ❌ | ❌ |
| View | ✅ | ❌ | ❌ |
- Click: a visitor followed an affiliate link.
- Lead: a form was submitted through an iFrame or the API.
- Send: one delivery of a lead to one channel in a Pingtree. A lead can have several.
- View: an impression.
- Prospect and Sale: reported by the advertiser through tracking.
Types created by PalDock cannot be created by a tracking request. Tracking can only update them, and an update that carries a different type creates a conversion of that type instead. See Tracking processing.
Custom conversion types
When the six built-in types are not enough, create your own in Workspace Settings, Tracking, Conversion types and pixels. Custom types behave like sale and prospect: they are reported through tracking and can be paid on.
Each type, custom ones included, comes with its own tracking pixel, in an advertiser version and an affiliate version.
Rules that apply to every type
- Transaction type does not have to match. A commission can create a transaction of a different type, and PalDock will create the conversion for it. See Transaction type.
typeis required when creating a conversion, and must match a type that is allowed on that channel.- Click, lead, and send cannot carry an external ID. It belongs to the advertiser’s order, which those types do not represent.
- A type can have several commissions. Send the Commission ID to say which one applies, otherwise the first one in the order is used.
