Tracking Pixel

    The tracking pixel is the core of the shop integration. It is placed on your order confirmation page and reports every transaction to QUALITYCLICK.

    JavaScript pixel vs. image pixel

    You can choose between two variants:

    • JavaScript pixel (recommended): Already includes the conversion tracking code and allows partners to deploy their own pixels
    • Image pixel: Simple 1×1 pixel image, works without JavaScript

    You can find the code under System → Tracking Codes after selecting the partner program.

    JavaScript pixel
    <script type="text/JavaScript"
      src="https://partner.your-site.com/get_trans.cgi
        ?cpid=1
        &tid=ORDERNUMBER
        &produkt=PRODUCTNAME
        &umsatz=NET_REVENUE
        &kunde=CUSTOMERNAME
        &js=1">
    </script>
    Image pixel
    <img src="https://partner.your-site.com/get_trans.cgi
        ?cpid=1
        &tid=ORDERNUMBER
        &umsatz=NET_REVENUE"
      height="1" width="1" border="0" />
    ⚠️Warning
    Replace the uppercase placeholders with variables from your shop system. Revenue must always be passed as a net amount (excluding VAT and shipping costs). The order number (tid) must be unique for each transaction.

    Parameter reference

    All parameters are optional. tid and cpid are recommended.

    ParameterDescriptionExampleMax lengthStatus
    tidTransaction ID (order number)ORD-2026-001255Recommended
    cpidCampaign ID15Required
    pidPartner ID (overrides cookie)3520Optional
    umsatzNet revenue95.50Recommended
    provisionFixed commission19.85Optional
    provCommission factor in % (0-300)503Optional
    produktCommission productflowersale255Optional
    kundeCustomer (free field)Smith63Optional
    freitextFree textKFW255Optional
    subidSub-ID (overrides cookie)Avb212255Optional
    wmidCreative ID (overrides cookie)120Optional
    lieferdatumFormat: YYYY-MM-DD2026-08-1010Optional
    bestelldatumFormat: YYYY-MM-DD2026-08-1010Optional
    FF_1 to FF_nCustom fieldsValueOptional
    jsJavaScript mode11Recommended
    ⚠️Warning
    Revenue (parameter umsatz) must be specified in the program currency without thousands separators. Both period and comma are allowed as decimal separators. Examples: 2134.23 or 4353,75 — but not 2.134,23.
    ⚠️Warning
    The parameters pid, subid and wmid override the values read from the cookie. Omit any parameters that you cannot populate with actual values.

    Custom fields

    Custom fields allow you to pass additional variables that are stored with the transaction.

    Create custom fields: System → Tracking Codes → Manage custom fields → Add new custom field

    Each custom field is accessible as FF_1, FF_2 up to FF_n in the order they were created:

    Custom fields in the pixel
    https://partner.your-site.com/get_trans.cgi
      ?cpid=1&tid=ORDERNUMBER&umsatz=95.50
      &FF_1=127.0.0.1
      &FF_2=customer@email.com
      &FF_3=John Doe
    ⚠️Warning
    The order and number of custom fields should be planned carefully in advance — they cannot be changed or deleted afterwards. Custom fields are not accessible via the SOAP interface.

    Tracking code assistant

    Under System → Tracking Codes, the tracking code assistant helps you generate the syntax for your programming language. Specify which language your shop system uses and how the parameters are named there.

    Conversion tracking

    If you use the combined JavaScript pixel, conversion tracking is already integrated. Otherwise, add the conversion tracking code (get_conv.cgi) separately on the order confirmation page:

    Conversion tracking (optional, separate)
    <iframe src="https://partner.your-site.com/get_conv.cgi
        ?cpid=1
        &tid=ORDERNUMBER
        &produkt=PRODUCTNAME
        &umsatz=100.00"
      height="2" width="3">
    </iframe>

    Details on setting up conversion tracking for partners can be found under Conversion Tracking.

    Still have questions?
    Our team is here to help with your integration — personally and competently.