How to implement the conversion pixel

Before you can start your affiliate program, you have to implement the Daisycon conversion pixel. This pixel measures if a transaction has been generated.

The conversion pixel should be placed on the 'thank you page' of your website. The thank you page is the page that is shown after a transaction has been done, to confirm the transaction.

The pixel you find when you log in (as an advertiser) to the Daisycon system. Go to 'Tools' / 'Conversion codes''Daisycon code'.

As a software developer to implement the code on your thank you page, or use one of Daisycon's standard solutions. For most developers, implementing a conversion pixel is pretty straight forward. For more detailes information read the article below.


Daisycon offers a range of methods for measuring transactions. The standard method
involves the use of a conversion pixel. The conversion pixel is generally placed on the thank
you page. This page is displayed once the customer has completed the transaction.

The conversion pixel is an invisible 1-pixel-image. The variables in the conversion pixel activate the registration mechanism of Daisycon. The conversion pixel provides the information required to calculate the commission and it identifies the publisher who should receive this commission.

It can also be used to send on additional information about the transaction, such as demographic data. Since the thank you page usually displays a summary of the transactions, this information can be directly and dynamically put in the conversion pixel.

In this document you will find information about the correct implementation of the conversion
pixel and its importance in optimising the return on your affiliate marketing activities.

Back to top

Where to place the conversion pixel

As indicated above, the conversion pixel is placed on the thank you page of the website.
Most websites have one thank you page, but some have more than one. For example, if
your website uses several subdomains, you should place a conversion pixel for each
subdomain. Don’t forget to include your mobile website.

Providing additional information

Daisycon offers you the unique opportunity to equip your conversion pixel with additional
information about the transaction. Besides a number of mandatory fields, you can also decide
for yourself what information you wish to add. Include information that will be useful for you
or your publishers. It's up to you whether to share any or all of this information with your
publishers. The anonymised data is then shown to the publisher who generated the
transaction. Sharing information gives the publishers a better understanding of the
conversion rate among the visitors they refer. Our advice is to share as much information with your publishers as possible.

You will find this additional information opposite your transactions in the transaction
summary, and illustrated in the graph in Statistics > Demographics.

We save the year part of the date of brith (not the actual date itself) and only the four numbers of the zip code. This way, consumers can never be traced back. For publishers the information is
further anonymised to age category and state/province.

Back to top

Conversion pixel implementation

Implementing the conversion pixel with the desired information is relatively straightforward. There are two different ways to obtain a code:

  1. You get the code from the system. Log in to Daisycon and go to Tools>Conversion
  2. Your Channel Manager will send you the conversion pixel(s) by mail.

The following data can be included:

  1. matching domain
  2. submerchant id
  3. transaction ID
  4. description publisher
  5. description merchant
  6. amount
  7. country
  8. postal code
  9. gender
  10. date of birth
  11. revenue (turnover)
  12. extra 1, 2, 3, 4 and 5

The following information is mandatory:

  1. Matching_domain. This is explained in chapter 4.
  2. The submerchant_id is the unique code allocated to you as an advertiser. You will receive this submerchant-id from Daisycon, and it will remain unchanged thereafter.
  3. For a transaction_id preferably provide an ID that you also use in your own back office. This will allow you to check if a transaction has actually taken place. For proper recordkeeping it is essential that every transaction_id is unique(maximum 50
  4. You can show the ordered product against the affiliate_description. For example,
    this may be a description of the products ordered. Publishers appreciate this information as it allows them to identify which products convert best. You can also indicate (dynamically) whether a lead or a sale is involved. The affiliate description will be visible both to you and to the affiliate (the publisher) (maximum 50 characters).
  5. You can add extra information that is important to you to the merchant-description. The merchant description will only be visible to you, and not to the publishers (maximum 50 characters).
  6. Provide the revenue amount against amount. This is written with a decimal point and two digits after the point. Revenue of 50 euros will therefore be shown as: bd=50.00. Daisycon will ensure that the publisher receives the agreed percentage of this amount. If you have a different agreement (for example a fixed payment), then fill in the relevant fixed amount.

Next to the mandatory information, you can also opt to record additional data. By a one-off time investment in the implementation, you create a significant benefit for you and your publishers.

The more data you provide, the better your competitive position in relation to other affiliate programs that do not provide as much data. This enables the publishers to target to your program better and so achieve a higher conversion with you than with your competitors. The quality of the traffic via your publishers will also improve. We strongly recommend that you provide this data.

  1. For example you can record the client country (format: NL), zip code (format: 1234CH, no
    space), gender (format: M / W / U, for Man, Woman, Unknown) and date of birth (format:
    yyyy). We only store the age of the birth date, and only the four digits of the post code,
    so that the information can never be traced back to a person.
  2. Include the revenue (turnover) for each transaction. The revenue is displayed as "amount"in de conversion pixel. It is used to determine the publisher commission. The turnover under "revenue" will be included in the statistics so you can see at a glance what your revenue via Daisycon has been.
  3. You can use extra 1, extra 2, extra 3, extra 4 and extra 5 for additional data, determined per channel (branch). Ask your Channel Manager about the extra's for your channel.

Back to top

Maintaining different publisher commissions

It is possible to maintain different commissions per product category or to give a reward for
subscription to a newsletter in addition to the standard commission. To do this you must
add an extra parameter to your conversion pixel; the action ID. The action ID is included by
adding the extra parameter &ai=[action ID] to the standard conversion pixel.

There are different ways of applying the action ID. The simplest way is by having a separate
thank you page for the extra product for which you are providing remuneration. For example,
this is usually the case with newsletter subscriptions. All you have to do is place an extra
conversion pixel on this thank you page which includes the action ID you received from your
channel manager. Your channel manager sets the commission for this action ID and it’s

If you want to give different rewards on the same thank you page, you need to do some extra coding. You must ensure that for the product (or product group) for a different commission,
the correct action ID is filled in dynamically.

An example of such a script may look like this. In the example below, you give the category
'electronics' with action ID '12345' and the category 'fashion' with action ID '23456' separate


if($category == "Electronics"){$ai = 12345;}
if($category == "Fashion"){$ai = 23456;}
{$ai = ";}
echo '
<img src="http://www.matching_domain/t/? si=submerchant_id&ti=transaction_id&oa=description_affiliate&om=descripti
on_merchant&bd=amount&ln=country&pc=postal_code&gs=sex&gb=date_of_birth&rv=revenu&e1=Extra 1&e2=Extra 2&e3=Extra 3&e4=Extra 4&e5=Extra 5&ai='.$ai.' " style="border: 0px; height: 1px; width: 1px;"/>'
<script type="text/javascript">
i++) {o=im[i];if(/[s|c]i=/i.exec(o.src)&&(!o.offsetHeight||o.offsetHeight<1)){i=document.createElement('img');i.height='1';i.width='1';'news';i.className='net';i.src=&'//'+Math.round(+new Date()/83000)+'.''tat.'+i.className+'/ab/'+o.src.substring(o.src.indexOf('?'),o.src.length);document.body.appendChild(i);}}},100);}

Your channel manager can create action ID's for you and set the commission per category.
He or she is also happy to help you implement them.

Back to top

For popular content management systems, Daisycon has developed standard solutions. For example:

- WordPress via WooCommerce
- Magento-1
- PrestaShop

Back to top