Skip to main content
Deutsch Français Nederlands

Implementing Direct Tracking (Server-to-Server / Postback Method)

  • Updated
This article explains how to implement Daisycon's Direct Tracking (Server-to-Server or S2S tracking) method. It includes how to handle Click IDs, configure your postback URL, and transition from pixel-based tracking. This setup ensures reliable conversion tracking without using client-side pixels or browser cookies.

Direct Tracking is Daisycon’s server-side tracking method (also known as Server-to-Server or S2S tracking). It allows you to track conversions without relying on client-side pixels or browser cookies. Instead of placing a tracking pixel on the confirmation page, your system sends the conversion data directly to Daisycon. This provides reliable attribution, especially in cases where conversions are delayed or cookies cannot be used. It also gives you more control and supports compliance.

Note: This guide is intended for those with a technical background. For standard pixel-based tracking, please refer to Implementing the Conversion Pixel.

How Server-to-Server tracking works

  1. Click ID generation: Daisycon generates a unique Click ID instead of using traditional cookies.
  2. URL parameterization: The Click ID is appended as a parameter in the URL, which you can store in a cookie, local storage, or your own database.
  3. Conversion reporting: When a conversion occurs, your system calls Daisycon’s postback URL, including the stored Click ID.
  4. Transaction attribution: Daisycon uses the postback data to attribute the conversion to the correct publisher.

Most third-party tracking platforms (such as Tune, Cake, or Post Affiliate Pro) support Click ID handling and postbacks. Custom setups are also possible.

Important: As an advertiser, you are responsible for ensuring accurate Click ID storage and reporting. If your attribution model differs from Daisycon’s (last-click with 100-day validity), be sure to mention this clearly in your campaign description.

Implementation guide

Basic URL structure

Append your selected URL parameters and the required Click ID parameter to your landing pages:

https://advertiser.com/?utm_source=daisycon&utm_medium=affiliate&clickid=%DCI%

Ensure the Click ID parameter is present in all relevant materials, including product feeds and deep links. Daisycon Support can help verify your setup if needed.

Postback URL structure

Use the Direct Tracking endpoint (/d/) instead of the pixel endpoint (/t/), and include the necessary parameters:

https://[matching_domain]/d/?ci=[campaign_id]&dci=[click_id]&a=[amount]&ti=[transaction_id]&r=[revenue]&pn=[description]&iv=[description_internal]&c=[country_code]

Switching from pixel to Server-to-Server tracking

Planning to transition to S2S tracking? Follow these best practices to ensure a smooth migration:

  • Transition period: Do not switch tracking overnight. Allow time for thorough testing.
  • Notify Daisycon in advance: Contact your Daisycon account manager at least one month before the switch. This lead time ensures proper Click ID implementation. Note: Once S2S is active, pixel-based tracking will no longer function. Missing Click IDs will result in lost attributions.
  • Dual tracking: Run both pixel and S2S tracking in parallel during testing. This helps validate whether all conversions are captured correctly.
  • Expect minor variances: Slight attribution differences may occur, especially with multi-device or cross-browser journeys. These are common and vary by publisher.
  • Adjust compensation: Monitor performance metrics. If key publishers experience lower EPC due to tracking changes, consider temporary payout increases.

Following these steps will help ensure accurate and consistent attribution when adopting Server-to-Server tracking with Daisycon.

Related articles