Skip to main content
Deutsch Français Nederlands

Implementing Revenue Share tracking

  • Updated
Revenue Share tracking at Daisycon explained: server-side tracking model using DCI and customer reference for long-term commissions, ideal for retention-based affiliate campaigns in finance, dating, and gambling.

This article explains how Daisycon’s Revenue Share tracking works and how to implement it using server-side calls with a persistent customer reference. This model is designed for recurring commissions based on long-term customer value.

What is Revenue Share?

Revenue Share is a compensation model within affiliate marketing where the publisher is rewarded with a recurring commission, based on either a fixed amount or a percentage of the revenue they help generate. This model is especially suitable in sectors where customer value develops over time or where retention is key, such as finance, dating, or gambling.

Since Revenue Share payouts are typically spread over time, a server-side tracking solution is required to ensure long-term attribution.

Note: Learn more about technical parameters, DCI, and call setup in the article Server-side Tracking.

When should you use Revenue Share?

This model is ideal when an advertiser seeks long-term customer relationships and acknowledges the publisher’s contribution to acquiring valuable users. It allows commission payments based on customer retention, subscription renewals, or recurring transactions over time.

How is it different from standard server-side tracking?

With standard server-side tracking, a single conversion is linked to a click, but no persistent connection between customer and publisher is stored.

Revenue Share tracking focuses on recurring commissions. Since conversions may occur weeks or months later, it is essential that the publisher is still credited correctly. Therefore, in Revenue Share campaigns, Daisycon permanently links a customer reference to a publisher from the first interaction.

Note: This article is intended for users with technical experience. If you are looking for a pixel-based solution, refer to the article Implementing the conversion pixel.

How to implement Revenue Share tracking

  1. Registering customer accounts using the DCI
    • In the first server-side call (/at/), a unique customer ID and DCI are recorded. The DCI (Daisycon Click Identifier) uniquely identifies the click.
    • Example: 
      https://jdt8.net/at/?ci=[CAMPAIGN_ID]&at=[UNIQUE_CUSTOMER_REFERENCE]&dci=[DCI]&pn=[DESCRIPTION]
    • This links the customer reference (at) to the publisher based on the DCI.
  2. Tracking recurring Revenue Share transactions
    • In the second call (/rs/), only the same customer reference (at) is used. The DCI is no longer required, as the link between customer and publisher was already established in the /at/ call.
    • Example: 
      https://jdt8.net/rs/?ci=[CAMPAIGN_ID]&at=[UNIQUE_CUSTOMER_REFERENCE]&a=[TRANSACTION_AMOUNT]&cur=[CURRENCY_CODE]&pn=[DESCRIPTION]
    • This allows the system to attribute the transaction to the correct publisher, even without click data.
  3. Viewing statistics in the Daisycon dashboard
    • Revenue Share transactions are visible under "Revenue Share Statistics" in the dashboard.
    • In most cases, each transaction is logged separately as a Daisycon conversion.
    • In specific sectors, multiple transactions can be grouped and settled periodically. Please consult your Partner Manager if this applies.

Conclusion

Revenue Share tracking ensures long-term, accurate attribution of customer value in Daisycon's affiliate network. By combining the DCI at the first interaction and linking future transactions via a stable customer reference, the system maintains attribution integrity, regardless of how much time has passed since the initial click.

Related articles