Parameters

Almost every field in the Connection Creator asks you for a value. You can type it, but usually you pick it, and the picker shows you everything the scenario has available at that point.

There are four groups.

Form fields

The fields of the structure the lead came from, such as first_name or email. What appears here depends on the offer, so two integrations rarely show the same list.

Keys

The tokens, endpoints and credentials this integration uses. Store anything you would otherwise repeat, such as the base URL or an API key, and change it in one place.

System parameters

Values PalDock fills in itself. Always available, never something you set. The full list is below.

Previous steps

Everything the earlier nodes produced. Each node appears by name, and under it whatever it returned. What that is depends on the node, so this part of the picker looks different in every scenario and changes as you build.

An HTTP node gives you the most: the status code, the parsed response body, the headers, and what was actually sent. Other nodes give you what they produce.

Only nodes that ran before this one are here, because data travels forward and never back.

How a value is written

Picked values appear as a tag in the field. Underneath, they are stored in braces, as {email} or {external_id}.

Form fields carry a prefix when they are inserted, so the field you picked as email is stored as {data_email}. That is why a value copied from one integration into another may look different from what the picker showed you.

You can type instead of picking, and mix the two in one field:

Bearer {token}
{first_name} {last_name}

Every field with a picker also has a copy button, which is quicker when you need the same value in several places.

The system parameters

Conversion

• origin_id : the PalDock ID of the click or the lead. This is the identifier you use to attribute anything back to the affiliate
• send_id : the PalDock ID of one delivery of a lead to one channel. Use it when you need the conversion tied to a specific channel in a pingtree
• conversion_id : the PalDock ID of the sale or the prospect. One origin can have several
• external_id : the advertiser’s own ID for the order
• affcid : the affiliate’s own ID for the conversion
• action : whether the conversion is being created or updated
• type : the conversion type
• result : the transaction result, such as pending, approved or rejected
• ip_address : the IP address of the end user

For what each identifier addresses and which one to send when, see Conversion IDs explained.

Commission

• value : the order value, used when the commission is a percentage of it
• commission : the value the advertiser sent in their commission parameter
• adv_commission : the final commission from the advertiser
• aff_commission : the final commission for the affiliate
• commission_profit : the difference between the two
• commission_id : which commission applies, when several exist for the same type
• currency : the currency of the offer
• price : the price the advertiser bid, used in auction distribution

Offer

• offer_id : the ID of the offer
• offer_name : its name
• country : its country

Advertiser

• advertiser_id : the ID of the advertiser
• advertiser_name : their nickname

Affiliate

• owner_id : the ID of the affiliate
• owner_name : their nickname

Integration

• integration_name : the name of the integration
• channel_name : the channel name from the pingtree
• channel_visible_name : the name the customer sees
• postback_id : the postback the flow belongs to
• redirect_url : where the customer goes next

Time

• created_date : when the conversion was created, written out
• timestamp : the same moment as a Unix timestamp
• timestamp_sign : the timestamp used when signing a request

Advertiser custom

• advs1 through advs10. Ten free slots for whatever a particular advertiser needs. Nothing is predefined, so decide what each one means and keep it consistent.

Affiliate custom

• affs1 through affs10. The same, for values belonging to the affiliate.

Execution

• step_run_id : the ID of this run of this node. Advertisers often want it as a request ID, so a retry can be told apart from a new request
• random_uuid : a fresh random identifier, generated for each request

Security

• digest : the digest of the request body
• signature : the signature of the request

Both are produced by the Signature setting on the HTTP node, and you place them in the headers yourself.

Cookies

• custom_cookie_ga and custom_cookie_ga_container_id : Google identifiers
• custom_cookie_gcl_aw : the Google Ads click identifier
• custom_cookie_fbp and custom_cookie_fbc : Facebook identifiers

Use these when forwarding conversions into advertising platforms, which need their own identifier to match the conversion to the click.

Where each one can be used

This page is about what you can pick while building a scenario. Which parameters may be sent through a pixel, a postback, the Tracking API or an affiliate postback is a different question. See Tracking parameters.