To measure conversions through affiliate marketing, Daisycon uses a tracking pixel that is placed on the thank you page of your website. This is the page that appears after a successful order or transaction.
The standard conversion pixel calculates commission on the (sub)total value of the transaction. If you want to calculate commissions at product level, Daisycon offers a product-level conversion pixel (also known as transaction part pixel). This makes it possible to assign variable commissions per product.
If your webshop is built on Magento, WooCommerce, PrestaShop, Lightspeed or another common platform, Daisycon provides ready-made integrations. Use one of the manuals below if applicable.
- Implement the Daisycon conversion pixel in Magento 1
- Implement the Daisycon conversion pixel in Magento 2
- Implement the Daisycon conversion pixel in PrestaShop
- Implement the Daisycon conversion pixel in WordPress / WooCommerce
- Implement the Daisycon conversion pixel in Shopify
- Implement the Daisycon conversion pixel in Lightspeed
- Implement the Daisycon conversion pixel in DanDomain (no product-level tracking possible)
If your system is not listed above (or if you want to implement product-level tracking), follow the instructions below.
Note: This article is intended for developers or technically proficient users. Product-level tracking requires a custom implementation and a correct data structure.
Standard conversion pixel (for total transactions)
The standard pixel tracks the total value of a transaction. Below is a basic example:
<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=[internal_description]&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" />
Standard pixel variables
| ci | Campaign ID |
| a | Order amount (used for commission calculation) |
| ti | Transaction ID |
| cc | Compensation code |
| pr | Promotion code |
| r | Revenue |
| pn | Product name or description |
| iv | Internal description (not visible to publishers) |
| e1 – e5 | Optional custom fields |
Product-level conversion pixel
The product-level pixel allows you to track each individual product within a transaction. This enables Daisycon to calculate variable commissions for different products or product groups using the cc value.
This pixel contains two main parts: the overall transaction data, and a repeating p[] array for each product.
Example product-level pixel
<img src="https://matching-domain/t/?ci=[campaign_id]&ti=[transaction_id]&cur=[currency]&np=[number_of_products]&pr=[promotion_code]&p[]={a:total}{r:total}{qty:qty}{sku:sku}{cc:code}{pn:name}{iv:internal}{e1:...}{e2:...}{e3:...}{e4:...}{e5:...}" style="border: 0; height: 1px; width: 1px;" alt="Daisycon Affiliate Marketing" />
Transaction-level variables
| ci | Campaign ID |
| ti | Transaction ID |
| cur | Currency (e.g. EUR, USD) |
| np | Number of unique products in this transaction |
| pr | Promotion code |
Product-level variables (within p[] array)
| a | Total amount for this product (price × quantity) |
| r | Total revenue for this product |
| qty | Quantity of this product |
| sku | Product ID or SKU |
| cc | Compensation code (used for variable commission) |
| pn | Product name (visible to publishers) |
| iv | Internal product description (not visible to publishers) |
| e1 – e5 | Optional custom fields |
All values must be URL-encoded.
Implementation notes
Discounts
Always subtract discounts or coupons from the product price before sending the value. This includes both fixed and percentage-based discounts.
Order amount calculation
Multiply the price of each product by its quantity. For example, 2 × €10 = {qty:2} and {a:20}.
Compensation codes
You can define custom compensation codes per product or category (e.g. Group1, Group2). These codes allow Daisycon to apply different commission logic on their end. Create only as many codes as needed for the number of commission groups you want to use.
Testing your implementation
After placing the pixel or enabling an integration, always test whether the conversion is tracked correctly. Follow the steps in the conversion pixel test manual.