Implementing the product-level conversion pixel (transaction part pixel) – Daisycon Advertiser FAQ

To measure transactions with Affiliate Marketing, you need to place a conversion pixel
on the thank you page of your website. The thank you page is the page that is shown
after a purchase or other transaction is completed.

A standard conversion pixel calculates the commission on the (sub)total amount of the transaction. Daisycon offers the option for a so-called 'part transaction pixel'. This conversion pixel measures each individual product within a transaction, which offers the possibility to set variable fees at product level.

For a number of e-commerce (CMS) platforms such as Magento, WordPress (WooCommerce) and Lightspeed, Daisycon has developed a standard solution, for which a separate manual is available.

If you are using one of these systems (except DanDomain), you do not need to follow the tutorial below.

Warning: This article may be more advanced and may require a deeper understanding of the topic before proceeding. The product level conversion pixel requires more development work.

Do you want to implement the part transaction conversion pixel in Google Tag Manager? Then don't use the Daisycon template, but do this by using a custom html tag.

Example standard conversion pixel:

<img src="https://matching-domain/t/?ci=[campaign_id]&a=[amount]&ti=[transaction_id]&cc=[compensation_code]&pr=[promotion_code]&r=[revenue]&pn=[description]&iv=[description_internal]&e1=[extra_1]&e2=[extra_2]&e3=[extra_3]&e4=[extra_4]&e5=[extra_5]" style="border: 0; height: 1px; width: 1px;" alt="Daisycon Affiliate Marketing" />

ci	Campaign ID
a	Order amount
ti	Transaction ID
cc	Compensation code
pr	Promotion code
r	Revenue
pn	Product name/description
iv	Internal description
e1 - e5	Extra fields

Explanation product-level transaction part pixel

Unlike the normal conversion pixel, with the part transaction pixel we need data for each individual product within a transaction. These so-called 'parts' are added to the transaction and the commission is then calculated over the (product) price of each individual part.

The first part is for identifying the campaign and transaction. The second part &p[] is a so-called query-string array per ordered product within a transaction.

Example transaction part pixel:

<img src="https://matching-domain/t/?ci=[campaign-id]&ti=[transaction-id]&cur=[currency]&np=[unique_products]&pr=[promotioncode]&p[]={a:total-product-price}{r:total-product-price}{qty:qty}{sku:sku}{cc:compensation-code}{pn:product-name}{iv:product-name}{e1:extra1}{e2:extra2}{e3:extra3}{e4:extra4}{e5:extra5}" style="border: 0; height: 1px; width: 1px;" alt="Daisycon Affiliate Marketing" />

Basic variables: [variable]

ci	Campaign ID
ti	Transaction ID
cur	Currency
np	Number of unique products in this order (checksum)
pr	Promotion code

For each unique product (part) / line item within the transaction, fill a p[] with the following variables:

Product variables: {variable}

a	Total order amount of unique product. Excl. VAT if needed. This is used to calculate commission*
r	Total revenue of unique product
qty	Quantity of unique product in this order
sku	SKU or unique ID of this product
cc	Compensation Code **
pn	Product name (visible to publishers)
iv	Internal description, can be the same as pn (visible to advertisers only)
e1 - e5	Extra fields

Make sure the content of each variable is url-encoded.

* Discounts

It is important to take into account any coupon codes or other discounts that might be used. Discounts must be deducted from the product price. This also applies to fixed discounts (10 euro discount for example).

* Order amount

Make sure you multiply the value of a product with the number of products in this order (qty). Two of the same products, with a value of €10 each means {qty: 2} and {a: 20}.

** Compensation Code

Based on the compensation code / compensation group variable (cc), Daisycon can set the variable fees. Creating a custom 'product attribute' is the easiest solution for this, when possible. A custom attribute could be for example: 'Group1' / 'Group2' / 'Group3' or any other random code. Create only the number of attributes for the number of different reimbursement groups you want to use. Link the new attributes to the appropriate products / categories. On our side, we set up the compensation groups based on the compensation codes we just created.

Testing the conversion pixel

After a developer has implemented the conversion pixel or if you have activated one of our standard solutions, the operation of the conversion pixel needs to be tested. You can do this by following each step of the Test Instructions manual.