Digistore24 Affiliate Tracking: Postback Setup Guide

If you promote products from Digistore24, the numbers in your ad account and the numbers in your Digistore24 dashboard rarely tell the same story on their own. Digistore24 affiliate tracking fixes that by tying every sale back to the exact click, campaign, and traffic source that produced it, so you know which ads actually make money.

The reliable way to do this is a server-to-server postback between Digistore24 and your tracker. In this guide, we'll walk through exactly how to set up Digistore24 affiliate tracking in ClickFlare, step by step, including the postback parameters that matter, how to handle upsells and refunds, and how to confirm everything works before you scale.

What Is Digistore24 Affiliate Tracking?

Digistore24 affiliate tracking is the process of recording which of your clicks turn into sales on Digistore24, and attributing each sale to the campaign and traffic source that generated it. It connects the click you paid for to the commission you earned, so your reporting reflects real profit instead of guesswork.

Digistore24 is a marketplace and payment platform where affiliates promote digital and physical products. On its own, it tells you that a sale happened, but not which Facebook ad, native placement, or email actually drove it. A dedicated tracker fills that gap by logging the click first, then matching the sale back to it when Digistore24 confirms the payment.

How Digistore24 Affiliate Tracking Works

At its core, Digistore24 affiliate tracking follows a simple handshake between two servers. Your tracker logs the click and stores a unique click ID, then hands that ID off to Digistore24. When the buyer pays, Digistore24 sends the ID back along with your commission and a transaction ID.

Here is the flow in plain terms:

• Click. Someone clicks your ad. ClickFlare records the click and generates a click ID.
• Redirect. ClickFlare sends the visitor to your Digistore24 promolink, with the click ID attached in the cid parameter.
• Purchase. The visitor buys. Digistore24 stores that cid against the order.
• Postback. Digistore24 fires a server-to-server postback to ClickFlare with the click ID, your payout, and a transaction ID.
• Match. ClickFlare matches the postback to the original click and records the conversion with revenue.

Because the conversion travels server to server, it doesn't depend on a cookie surviving in the buyer's browser. That matters a lot now that browsers block third-party cookies and buyers often purchase on a different device than the one they clicked on. If you want the full background on the mechanism, our guide on what a postback URL is breaks it down from scratch, and our postback tracking guide for affiliates covers how server-to-server tracking works end to end.

Before You Start: What You Need

A clean setup depends on getting two things in place first. Skipping either one is the most common reason tracking breaks later.

• A ClickFlare account with a custom tracking domain. Something like trk.yourdomain.com. Your postback URL is built on this domain, so if you change it later you'll have to update the postback inside Digistore24. Shared domains are often flagged or blocked, so set up your own first.
• A Digistore24 affiliate account with a promolink. You need an approved promolink for the specific product you're promoting. Some vendors require approval before they'll issue one.

How to Set Up Digistore24 Affiliate Tracking in ClickFlare

The full setup takes nine steps. Work through them in order, because each one depends on the last. For the complete reference with screenshots, see the Digistore24 integration guide in the ClickFlare docs.

1. Set Up Your Tracking Domain

Add your custom tracking domain in ClickFlare before anything else. The postback URL you'll hand to Digistore24 is built on this domain, so locking it in now saves you from redoing the postback later.

2. Set Your Conversion Timing

Go to Settings → General Settings and set Conversion registration time reporting to Postback Timestamp. This is an account-wide setting. With the default Visit Timestamp, rebills get reported on the original click date instead of the actual payment date, which skews your reporting for subscription products.

3. Create the Campaign

Go to Campaigns → New Campaign and choose Redirect tracking. Then select your traffic source and the tracking domain you set up in step one.

4. Create the Digistore24 Affiliate Network

In the offer form's Affiliate Network field, or under Affiliate Networks → + New, select the Digistore24 template. Then confirm the defaults:

• Click Id is {cid}
• Payout is {amount_affiliate}
• Transaction ID is {transaction_id}

Leave Event Type empty for now. Under Conversion tracking, choose your tracking domain and keep S2S Postback URL as the method. Set Payout currency to match the currency you'll select in Digistore24, then copy the generated postback URL and save it. You'll need it in step seven.

5. Get Your Promolink

In Digistore24, open the Marketplace, select the product, and click Promote now. Your promolink will look like this:

https://www.checkout-ds24.com/redir/[product ID]/[affiliate name]/

The optional campaign key in Digistore24 is for a fixed campaign name, not for per-click data, so don't rely on it to carry your click ID.

6. Create the Offer

In the ClickFlare offer form, select the Digistore24 affiliate network you just created. Paste your promolink into the Offer URL field and append the click ID parameter:

• Add ?cid={cf_click_id} to the end of the link. If the link already contains a ?, use &cid={cf_click_id} instead.
• Keep the curly braces. Without them, the literal text cf_click_id gets stored and matching fails.
• As an alternative, enable Append Click ID to Offer Url, but use only one method, not both.

Set the payout to Auto so ClickFlare uses the real payout value from the postback instead of a fixed number.

7. Add the S2S Postback in Digistore24

In Digistore24, go to Sales & partners → Integrations, select Add new connection, and choose S2S postback. Configure it like this:

• Name: an internal label, such as "ClickFlare."
• Products: the products you promote. Unselected products won't send postbacks.
• Order events: select only the payment event.
• Postback URL: paste the ClickFlare URL you copied in step four.
• Currency: match the Payout currency you set in ClickFlare.
• Status: Active.

8. Add a Lander (Optional)

If you run a landing page before the offer, make sure its call-to-action links to the ClickFlare click URL, not directly to the promolink. Linking straight to the promolink skips the click log and breaks attribution.

9. Save and Launch

Save the campaign, copy its URL from the Tracking tab, and verify the setup before you spend on traffic. We'll cover the exact checks in a moment.

The Digistore24 Postback URL and Its Parameters

Once everything is connected, two URLs do the heavy lifting. The offer URL carries the click ID into Digistore24, and the postback URL carries the sale back to ClickFlare.

Offer URL (set in ClickFlare):

https://www.checkout-ds24.com/redir/123456/youraffname/?cid={cf_click_id}

Postback URL (added in Digistore24, generated by ClickFlare):

https://trk.yourdomain.com/cf/cv?click_id={cid}&payout={amount_affiliate}&txid={transaction_id}

Here's what each placeholder does:

Always use {amount_affiliate} for your payout. The other amount placeholders report different figures: {amount_brutto} and {amount_netto} report gross and net order values, and {amount_vendor} reports the vendor's share as your revenue, which will badly inflate your numbers.

Why the Transaction ID Matters So Much

By default, ClickFlare keeps one conversion per click ID. Without a unique transaction ID, repeated postbacks on the same click overwrite each other, and you lose upsells and rebills.

Use {transaction_id}, which is unique per payment. Avoid {order_id}, because it's shared across the main sale, upsells, and rebills, so those get merged into one. And avoid {random}, which counts resent postbacks twice and quietly inflates conversions.

Tracking Upsells, Rebills, and Refunds

Digistore24 sends one postback per transaction, so each upsell and each rebill arrives as its own conversion. That's exactly what you want, as long as your transaction ID is set correctly.

Refunds and chargebacks are also separate transactions. If your sales connection fires on them, ClickFlare records them as new conversions rather than reversals, which overstates your performance. To keep your sales data clean, select only the payment event on your main connection.

If you want to track more than just sales:

• To track refunds, create a second S2S connection that fires only on refund events, and append &ct=refund to its postback URL. Create a matching custom conversion named refund ahead of time.
• To split sales from upsells, append &ct={order_type} to your postback URL and create custom conversions for initial_sale and upsell. The names must match exactly.

Custom conversions have to exist before the postback arrives, and the ct value must match the conversion name character for character, or the event gets dropped.

Verifying Your Digistore24 Affiliate Tracking Setup

Never trust a tracking setup until you've seen a test conversion land. Run through these four checks before putting money behind the campaign:

1. Click through the campaign and confirm the Digistore24 URL contains a real cid value, not the literal placeholder text.
2. Make a test purchase. Test orders set {is_test} to 1, which you can capture with an extra parameter if you want to separate tests from live sales.
3. Check Sales & partners → Integrations → Log in Digistore24 to see the postback call and ClickFlare's response.
4. Confirm the conversion shows on the campaign with the expected payout, and that Logs → Event Logs in ClickFlare shows a transaction ID.

Common Digistore24 Affiliate Tracking Mistakes to Avoid

Most tracking problems come down to a handful of recurring errors. Here's what to watch for and how to fix each one:

• Sales missing in ClickFlare. Check that the product is selected in the connection, the payment event is ticked, the connection is active, and cid is present in the offer URL.
• Receiving a literal {cid} value. The placeholder is misspelled. Digistore24 placeholders are lowercase.
• Receiving a literal cf_click_id value. The offer URL is missing its curly braces.
• Refunds inflating conversions. Remove refund events from your sales connection and track them separately.
• Upsells or rebills merging into one. Your transaction ID is set to {order_id}. Change it to {transaction_id}. Note that previously merged conversions won't be restored.
• Currency mismatch. The currency in the Digistore24 connection and the Payout currency in ClickFlare must match, or your payouts will be wrong.

Final Thoughts on Digistore24 Affiliate Tracking

Digistore24 affiliate tracking comes down to one reliable mechanism: a server-to-server postback that passes your click ID out with the offer URL and returns it with the sale. Get the tracking domain, the cid parameter, and the transaction ID right, match your currencies, and run a test purchase, and you'll have clean, accurate attribution across sales, upsells, rebills, and refunds.

From there, the same setup pattern applies to almost any network you work with. If you promote offers beyond Digistore24, our roundup of the best affiliate networks in 2026 walks through how to track each one. For the official Digistore24 side of things, their tracking as an affiliate documentation is a useful reference.

Frequently Asked Questions

How Does Digistore24 Track Affiliate Sales?

Digistore24 stores a click ID that you pass into the promolink, then sends a server-to-server postback to your tracker when a payment completes. The postback includes the click ID, your commission, and a transaction ID, which lets your tracker match the sale to the original click.

What Is the Postback URL for Digistore24?

The postback URL is generated by your tracker and pasted into Digistore24's S2S postback connection. In ClickFlare, it uses the {cid}, {amount_affiliate}, and {transaction_id} placeholders to return the click ID, payout, and a unique transaction ID for each sale.

Why Are My Digistore24 Conversions Not Showing in My Tracker?

The most common causes are a missing cid in the offer URL, the product not being selected in the postback connection, an inactive connection, or missing curly braces around the click ID parameter. Check the Digistore24 integration log to see whether the postback fired at all.

How Do I Track Upsells and Rebills on Digistore24?

Set your transaction ID to {transaction_id} rather than {order_id}. Because Digistore24 sends one postback per transaction, a unique transaction ID keeps each upsell and rebill as its own conversion instead of overwriting the original sale.

Can I Track Digistore24 Refunds?

Yes. Create a separate S2S connection that fires only on refund events, append &ct=refund to its postback URL, and create a matching custom conversion for refunds. Keep refund events off your main sales connection so they don't inflate your conversion count.