Every tracking method moves the same set of parameters. What differs is the direction and which parameters are available in it.
- Pixel and S2S postback bring data into PalDock, usually from the advertiser.
- Tracking API and affiliate postback send data out of PalDock, to the advertiser or to the affiliate.
This page is the reference for what may travel in each direction. For what you can pick while building a scenario in the Connection Creator, see Parameters.
The identifiers
Four parameters decide whether a tracking request matches anything at all, so read these before the rest:
origin_idis the click or the lead.send_idis one delivery of that lead to one channel in a pingtree. One lead can have several.conversion_idis the sale or the prospect. One origin can have several.external_idis the advertiser’s own ID for the order, sent together withadvertiser_id.
To create a conversion, send the origin_id, or the advertiser_id together with the external_id. Sending both pairs is the safest option. To update one, send the external_id with the advertiser_id, or the conversion_id when you have it.
Full detail on which to send and when: Conversion IDs explained.
The full list
A ✅ means the parameter can be used in that direction, a ❌ means it cannot. The first column is the group the parameter belongs to, so you can sort the table by it.
| Group | Parameter | Pixel | S2S postback | Tracking API | Affiliate postback | Description |
|---|---|---|---|---|---|---|
| Conversion | origin_id | ✅ | ✅ | ✅ | ✅ | PalDock ID of the click or the lead. Use it to attribute a conversion back to the affiliate. |
| Conversion | send_id | ✅ | ✅ | ✅ | ✅ | PalDock ID of one delivery of a lead to one channel in a pingtree. One lead can have several. |
| Conversion | conversion_id | ❌ | ❌ | ✅ | ✅ | PalDock ID of the sale or the prospect. One origin can have several. |
| Conversion | external_id | ✅ | ✅ | ✅ | ✅ | The advertiser’s own ID for the order. |
| Conversion | affcid | ✅ | ✅ | ✅ | ✅ | The affiliate’s own ID for the conversion. |
| Conversion | action | ✅ | ✅ | ✅ | ✅ | Whether to create a new conversion or update an existing one. |
| Conversion | type | ✅ | ✅ | ✅ | ✅ | The conversion type. Required when action is create. |
| Conversion | result | ✅ | ✅ | ✅ | ✅ | The transaction result, such as pending, approved or rejected. |
| Conversion | ip_address | ❌ | ❌ | ✅ | ✅ | IP address of the end user. |
| Commission | value | ✅ | ✅ | ✅ | ✅ | The order value. Used when the commission is a percentage of it. |
| Commission | commission | ✅ | ✅ | ❌ | ❌ | The amount the advertiser sent in their commission parameter. |
| Commission | adv_commission | ❌ | ❌ | ✅ | ❌ | The final commission from the advertiser. |
| Commission | aff_commission | ❌ | ❌ | ✅ | ✅ | The final commission for the affiliate. |
| Commission | commission_profit | ❌ | ❌ | ✅ | ❌ | The difference between adv_commission and aff_commission. |
| Commission | commission_id | ✅ | ✅ | ✅ | ❌ | Which commission applies, when several exist for the same type. |
| Commission | commission_code | ✅ | ✅ | ✅ | ❌ | The commission’s own text code. Works as an alias for commission_id. |
| Commission | currency | ❌ | ❌ | ✅ | ✅ | The currency of the offer, in ISO 4217 format. |
| Commission | price | ❌ | ❌ | ✅ | ❌ | The price the advertiser bid. Used in auction distribution. |
| Offer | offer_id | ✅ | ✅ | ✅ | ✅ | The ID of the offer. |
| Offer | offer_name | ❌ | ❌ | ✅ | ✅ | The name of the offer. |
| Offer | country | ❌ | ❌ | ✅ | ✅ | The country of the offer, in ISO 3166 format. |
| Advertiser | advertiser_id | ✅ | ✅ | ✅ | ✅ | The ID of the advertiser. |
| Advertiser | advertiser_name | ❌ | ❌ | ✅ | ❌ | The advertiser’s nickname. |
| Advertiser | advs1 to advs10 | ✅ | ✅ | ✅ | ❌ | Ten free slots for values belonging to the advertiser. |
| Affiliate | owner_id | ✅ | ✅ | ✅ | ✅ | The ID of the affiliate. |
| Affiliate | owner_name | ❌ | ❌ | ✅ | ❌ | The affiliate’s nickname. |
| Affiliate | affs1 to affs10 | ✅ | ✅ | ✅ | ✅ | Ten free slots for values belonging to the affiliate. |
| Integration | integration_name | ❌ | ❌ | ✅ | ❌ | The name of the integration. |
| Integration | channel_name | ❌ | ❌ | ✅ | ❌ | The channel name from the pingtree. |
| Integration | channel_visible_name | ❌ | ❌ | ✅ | ❌ | The channel name the customer sees. |
| Integration | postback_id | ✅ | ✅ | ✅ | ❌ | The postback the flow belongs to. Works only when there are follow-up steps. |
| Integration | redirect_url | ❌ | ❌ | ✅ | ❌ | Where the customer goes next. Comes from the advertiser in the integration. |
| Time | created_date | ❌ | ❌ | ✅ | ✅ | When the conversion was created, in Y-m-d H:i:s format. |
| Time | timestamp | ❌ | ❌ | ✅ | ✅ | The same moment as a Unix timestamp. |
| Time | timestamp_sign | ❌ | ❌ | ✅ | ✅ | The timestamp used when signing a request. |
| Form data | data_XYZ | ❌ | ❌ | ✅ | ❌ | Any field from the form structure, with data_ in front of its system name. |
| Custom | custom_XYZ | ✅ | ✅ | ✅ | ✅ | Any parameter sent with the custom_ prefix is stored. |
| Cookies | custom_cookie_ga | ✅ | ✅ | ✅ | ✅ | Google identifier from the cookie. |
| Cookies | custom_cookie_ga_container_id | ✅ | ✅ | ✅ | ✅ | Google container identifier from the cookie. |
| Cookies | custom_cookie_gcl_aw | ✅ | ✅ | ✅ | ✅ | Google Ads click identifier from the cookie. |
| Cookies | custom_cookie_fbp | ✅ | ✅ | ✅ | ✅ | Facebook identifier from the cookie. |
| Cookies | custom_cookie_fbc | ✅ | ✅ | ✅ | ✅ | Facebook identifier from the cookie. |
| Execution | random_uuid | ❌ | ✅ | ✅ | ✅ | A fresh random identifier, generated for each request. |
Parameters with a prefix
Two entries in the table are patterns rather than fixed names:
data_XYZis any field from the form structure, withdata_in front of its system name. A field calledemailis sent asdata_email. See Local, Global and Custom fields.custom_XYZis anything you send with acustom_prefix. PalDock stores it whether or not it is defined anywhere, which makes it the place to put values that have no parameter of their own.
The custom_cookie_ parameters are separate from these. They carry advertising platform identifiers collected in the visitor’s browser, and the names are fixed. Forward them when you send conversions into Google or Facebook, which need their own identifier to match the conversion to the click.
Where to see what was sent
Every tracking request is recorded with the parameters it carried. See Tracking and Conversion Logs, and Tracking errors and reasons when a request did not do what you expected.
