Server-to-Server (S2S) tracking, also known as Direct Tracking, is an advanced method used to track conversions in affiliate marketing without relying on client-side pixels or cookies. Instead of placing a tracking pixel on the "thank you" page, S2S tracking requires that your system directly informs Daisycon about conversions, including the specific publisher that referred the transaction. This solution is ideal for cases where immediate tracking is not feasible (e.g., delayed transactions) and offers added benefits such as bypassing cookie restrictions.
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 (Direct Tracking) Works
- Click-ID Generation: Daisycon generates a unique Click ID instead of using traditional cookies.
- URL Parameterization: The Click ID is appended as a parameter in the URL, which you can store in a cookie, local storage, or database.
- Conversion Reporting: When a conversion occurs, your system makes a call to Daisycon’s postback URL, including the stored Click ID.
- Transaction Attribution: This postback enables Daisycon to attribute the conversion to the appropriate publisher.
Most often, third-party tracking platforms (e.g., Tune, Cake, Post Affiliate Pro) offer built-in solutions for handling Click IDs and postbacks. However, custom implementations are also possible if using a dedicated setup.
Reminder: Advertisers are responsible for ensuring accurate Click ID matching when using server-side tracking. If your attribution model differs from Daisycon’s (last-click/100-day window), make this clear in your campaign description.
Implementation Guide
Basic URL Structure
Add your chosen URL parameters (e.g., UTM tags) and the required Click ID parameter:
https://advertiser.com/?utm_source=daisycon&utm_medium=affiliate&clickid=%DCI%Ensure this parameter is consistent across all campaign materials, including data feeds and deep links. Daisycon support can assist in verifying your setup.
Postback URL Structure
The Daisycon postback URL should include specific parameters for conversion details. Replace /t/ with /d/ in the URL to indicate Direct Tracking and add the Click ID for proper matching:
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]Tips for switching from pixel to Server-to-Server tracking
For advertisers planning to transition from pixel-based tracking to server-to-server tracking, please review our guidelines below to ensure a seamless switch:
- Transition Period: Avoid making the switch overnight. Allow time for testing to ensure proper setup and functionality.
- Informeer Daisycon: Inform your Daisycon contact at least one month in advance (take the measurement time into account). This lead time is essential for implementing Click IDs accurately. Note: Once S2S tracking is active, pixel tracking will no longer attribute transactions, so missed Click IDs may impact attribution.
- Dual tracking for testing: We recommend running both tracking methods simultaneously for a certain period. This allows for analysis to verify that all required transactions are captured in the new S2S setup.
- Expected variances: Be aware that S2S tracking may result in slightly fewer attributed transactions, as user journeys involving multiple devices or browsers can sometimes disrupt Click ID distribution. These differences are common but vary depending on the publisher and user journey.
- Adjust compensations: Be aware of the performance of your biggest publishers, compensate by increasing their payout if their EPC drops with the change in tracking.
This process will help ensure accurate tracking and attribution continuity during your transition to S2S tracking with Daisycon.