Embeddable form

Users with access to a specific Offer can view its details together with allowed propagation options (Link, iFrame, API).

Embeddable forms allow affiliates to embed a lead form directly on their website. Visitors can fill in the form to convert into a lead, which is then sent to PalDock for processing. The affiliate can copy the embed code from the Offer Preview section and customize the form’s style to match their website.

Admins define the form structure in Form Structures and assign them to offers. In the Design section, forms can be styled according to tenant needs.

Form Parameters

The most common parameters used in PalDock are:

• affcid – a custom click identifier provided by the affiliate.
• affs1 to affs10 – custom fields where affiliates can pass their own IDs or values for tracking and reporting.
• affiliateID – identifier of the affiliate sending traffic, which can rewrite the original owner of the form. The AffiliateID rewrite feature must be enabled.
• external_redirect_url – an alternative URL where the user should be redirected after form submission. The External Final Page feature must be enabled.
• test – marks the lead as a test so it will not be processed as a standard lead.

Parameters can be passed either in the URL, which takes precedence, or in the form body.

Form Features

• Pre-filling fields – the form can be prefilled by passing data_fieldname=value, where the field name matches a field in the offer’s form structure. The Pre-filling fields feature must be enabled.
• Auto-submit – the form can be set to submit automatically by adding system_submit=true. If some fields are missing, validation triggers an error and the user is asked to complete them. The Auto submit feature must be enabled.

The form and the page around it

The form runs in an iframe on the partner’s site, which has two consequences worth knowing before you go live:

• The form cannot read the page it sits on. URL parameters, cookies and referrer belong to the partner’s page, not to the iframe. Anything the form should know has to be passed into the embed URL, or collected afterwards with the update pixel.
• Cookies inside the iframe are third-party cookies. That is why the redirect after submission goes to a page on your own domain rather than staying inside the iframe. See Pingtree Distribution.

Tracking in DataLayer

The form pushes events to the DataLayer so PalDock or any other tracking scripts can pick them up, for example started when the visitor begins filling the form and lead when it is submitted.

On submission the form also pushes the conversion ID, so tracking scripts can use it to update the lead with additional information from cookies or URL parameters. See Update pixel.