Session Tracking

    Pass the PartnerID through your shop internally — without cookies, directly via URL parameters or your server session.

    How it works

    With session tracking, the PartnerID (and optionally the SubID) is passed as a URL parameter to your shop when a creative is clicked. Your shop stores these values in the server session or carries them as URL parameters from page to page. On the order confirmation page, you pass the stored values back to the tracking pixel.

    This method is suitable when you already have the PartnerID available internally in your order system and don't need cookie-based tracking.

    Setting up click targets

    All links under Creatives → Click Targets must contain the PartnerID as a URL parameter. Use the placeholder <% PID %>:

    Click target with PartnerID
    https://www.your-shop.com/page1?pid=<% PID %>

    Optionally, you can also pass the SubID:

    Click target with PartnerID and SubID
    https://www.your-shop.com/page1?pid=<% PID %>&subid=<% SUBID %>

    Storing the PartnerID in your shop

    Your shop must read the PartnerID from the URL parameter and retain it until the order confirmation. Two options:

    • Server session: Store the value in your web server's session (recommended)
    • URL parameter: Carry the value from page to page as a URL parameter
    PHP: Store PartnerID in session
    <?php
    // On the landing page, transfer the PartnerID from the URL to the session
    if (!empty($_GET['pid'])) {
        $_SESSION['qc_pid'] = $_GET['pid'];
    }
    if (!empty($_GET['subid'])) {
        $_SESSION['qc_subid'] = $_GET['subid'];
    }
    ?>

    Passing data to the tracking pixel

    On the order confirmation page, pass the stored PartnerID to the tracking pixel:

    Tracking pixel with session data
    https://partner.your-site.com/get_trans.cgi
      ?cpid=1
      &tid=ORDERNUMBER
      &pid=12345
      &subid=AB
      &umsatz=95.50
      &produkt=Sale
    ⚠️Warning
    The parameters pid, subid and wmid in the tracking pixel override the values read from the cookie. Only pass parameters you can actually populate with values — when in doubt, leave them out. If both cookie and session data are present, explicitly passed URL parameters take precedence.

    When to use session tracking vs. cookie tracking?

    CriterionCookie trackingSession tracking
    EffortLow (just add the pixel)Medium (session logic in the shop)
    Attribution over daysYes (cookie duration)Only within a single session
    CookielessNoYes
    Cross-deviceNoNo
    💡Tip
    For cookieless tracking across multiple sessions or server-to-server integration, we recommend ClickID / S2S Tracking instead, which automatically encodes the PartnerID in a unique ClickID.
    Still have questions?
    Our team is here to help with your integration — personally and competently.