Update pixel

This pixel is placed either by the Advertiser on the conversion page (e.g., thank-you/confirmation page) or by the Affiliate on their form page to collect URL and cookie parameters that an iframe (or API form) cannot collect automatically. Its job is to update a conversion event in PalDock.

 <script>
 window.paldock=window.paldock||{q:[],conversion:function(){window.paldock.q.push(["conversion"].concat([].slice.call(arguments)))}};

  // Create a new conversion of type "lead"
  paldock.conversion({
    action: 'update', 
    type: 'lead',
    affiliate: 'advertiser_id', // only for affiliates
    advertiser: 'advertiser_id', // only for advertisers
    external_id: 'advertiser_external_id', // only for advertisers
    pldk_conversion_id: 'paldock_conversion_ID', / Required only if the PalDock conversion ID is not available in the dataLayer, from which this pixel can automatically retrieve it.
    queryParam: {
      key1: 'utm_content',
      key2: 'utm_medium',
      key3: 'utm_source'
    },
    cookieParam: {
      key1: '_ga',
      key2: 'fbp',
      key3: 'fbc'
    }
  });
 </script>

Parameters

You can find all available parameters, along with their descriptions, on the Tracking Parameters page. Below are the most common ones:

• action – defines whether the conversion should be created (create) or updated (update).
• type – what type of conversion you want to create (lead, sale or custom)
• advertiser – the advertiser ID from PalDock
• external_id – your external event ID (Advertiser Conversion ID or Affiliate Conversion ID)

Required fields depend on the chosen pairing method:

As mentioned on the page Tracking processing, there are 2 pairing methods:

1. Via PalDock Conversion ID – only this parameter is required, since it is always unique in the system.
2. Via Advertiser External ID – the External ID is required. On its own, it may not be unique, but uniqueness is ensured in combination with the PalDock Advertiser ID. (not available for Affiliates)

The pldk_conversion_id a parameter is created with every conversion, and you need to save this ID. If you store it in the data layer, the pixel will use it automatically, so you don’t need to include this parameter in the pixel code. If you store it elsewhere, you’ll need to populate the value in the pixel code later when the update pixel is fired.

If you’re an affiliate using an iframe form, the form handles this automatically and you don’t need to do anything. If you’re an affiliate using an API form, or if you’re an advertiser, you need to save the pldk_conversion_id and store it in the data layer (or elsewhere). In the data layer, this is done as follows:

Populating ID through Data Layer

You can manually include the pldk_conversion_id in the Updating conversion script, or it will be picked up automatically when you use the iframe form (affiliates only) or when you push it to the dataLayer. After firing Update pixel, you will have updated information about the conversion, which can be sent through postback anywhere (your system, Google Ads, Meta etc.).

Creating conversion through Pixel

When a conversion is created, the pixel automatically stores the created pldk_conversion_id parameter in the Data Layer.

Creating conversion through API / Postback

When a conversion is created, the API response includes the pldk_conversion_id parameter, for example:

{"status": "accepted" "id": "1234"}

Push the pldk_conversion_id into your dataLayer; the pixel for updating conversion will then retrieve it automatically. Use the same type (e.g., “lead” or “sale”) as when creating the conversion, and include the stored pldk_conversion_id.

window.dataLayer = window.dataLayer || [];window.dataLayer.push({  
    event: 'sale',  
    pldk_conversion_id: id  // conversion id received from pixel or API
});