Tracking parameters

There are numerous parameters you can use to retrieve information from advertisers (via pixel or postback) or to send data outside of PalDock (through the tracking API or affiliate postback). To scroll the table, click and hold the middle mouse button while dragging.

Parameter	Pixel	Postback	API	Affiliate Postback	Description
eid	✅	✅	✅	✅	Unique event ID of the transaction
conversion_id	❌	❌	✅	✅	Unique conversion ID of the source conversion (click or lead). Use primarily eid, the conversion_id is for specific use cases
external_id	✅	✅	✅	✅	External ID indicating conversion in the advertiser’s system
affcid	✅	✅	✅	✅	External ID indicating conversion in the affiliate’s system
action	✅	✅	✅	✅	Defines whether to create a new conversion or update an existing one
type	✅	✅	✅	✅	Conversion type (required when action = create)
result	✅	✅	✅	✅	Transaction result (status), e.g. pending, approved, rejected
value	✅	✅	✅	✅	Order value used for commission calculation when the commission is a percentage of the order value
advertiser_id	✅	✅	✅	✅	Advertiser ID
commission_id	✅	✅	✅	❌	ID for commission specification when multiple commissions exist for the same type
commission	✅	✅	❌	❌	Value sent by the advertiser in the “commission” parameter during tracking. Internally referenced as {adv_commission}
adv_commission	❌	❌	✅	❌	Final commission amount used in PalDock
aff_commission	❌	❌	✅	✅	Final affiliate commission amount used in PalDock
commission_profit	❌	❌	✅	❌	Difference between adv_commission and aff_commission
advs1 up to advs10	✅	✅	✅	❌	Custom parameters of the advertiser
postback_id	✅	✅	✅	❌	Postback ID – works only if there are follow-up steps
created_date	❌	❌	✅	✅	Conversion date in Y-m-d H:i:s format
timestamp	❌	❌	✅	✅	Conversion date in timestamp format
currency	❌	❌	✅	✅	Offer currency (ISO 4217 format)
country	❌	❌	✅	✅	Offer country (ISO 3166 format)
offer_id	✅	✅	✅	✅	Offer ID
offer_name	❌	❌	✅	✅	Offer name
advertiser_name	❌	❌	✅	❌	Advertiser nickname
integration_name	❌	❌	✅	❌	Integration name
channel_name	❌	❌	✅	❌	Channel name as defined in Offer Distribution
channel_visible_name	❌	❌	✅	n/a	Visible channel name as defined in Offer Distribution
owner_id	✅	✅	✅	✅	Affiliate ID
owner_name	❌	❌	✅	❌	Affiliate nickname
price	❌	❌	✅	❌	Bid price received from the advertiser in the integration for Auction Offer Distribution
redirect_url	❌	❌	✅	❌	Redirect URL received from the advertiser in the integration for Offer Distribution
data_XYZ	❌	❌	✅	❌	Fields from the form structure, using “data_” before each system name.
affs1 up to affs10	✅	❌	✅	✅	Custom Data of the conversion owner (affiliate)
custom_cookie_ga	✅	✅	✅	✅	Google ID from cookie
custom_cookie_ga_container_id	✅	✅	✅	✅	Google ID from cookie
custom_cookie_gcl_aw	✅	✅	✅	✅	Google ID from cookie
custom_cookie_fbp	✅	✅	✅	✅	Facebook ID from cookie
custom_cookie_fbc	✅	✅	✅	✅	Facebook ID from cookie
custom_XYZ	✅	✅	✅	✅	Any custom parameter send with prefix “custom_” will be stored
ip_address	❌	❌	✅	✅	IP address of the end user

Insights that
helps you grow

Release notes 2025/12/19
We added country-based categorization. You can now categorize offers, integrations, and other items by a specific country, or keep them global across all markets. We also…
Release notes 2025/12/17
More flexible lead rejection: based on validation rules, filters, or pingtree sales results, by source (iframe, API) or by partner (include / exclude). It is now possible to…
Case study: How Lender Orka Ventures Scaled Affiliate Operations
Orka Ventures, an online lending group that wanted to scale fast across countries and onboard affiliates quickly. Their custom affiliate API and tracking layer soon…