Skip to content

Media buyer tool 3 · Postback URL Tester for RedTrack

Test your RedTrack postback URL before the next conversion goes missing.

The affiliate network calls your RedTrack tracking-domain postback URL when a conversion happens, passing back the RedTrack click ID and payout. Below: RedTrack's postback format and macros as RedTrack's own docs give them, the ways a RedTrack postback usually breaks, and the tester, pre-filled with an example of the postback URL your affiliate network calls in. Edit it to match yours and run the check.

Nothing you enter leaves your browser.

RedTrack's postback format

http://rdtrck2.com/postback?clickid={sub1}&sum={sum}   (RedTrack's Affise example; CAKE example: clickid=#s2#&sum=#price#)

Set by your network, not by RedTrack: put your network's click-ID macro in the clickid= field. Source: Payout tracking (RedTrack Help), digistore24 and RedTrack (RedTrack Help), ClickBank and RedTrack (S2S postback integration) (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

RedTrack macros

MacroMeaning
{clickid}RedTrack's click-ID token for the offer URL (e.g. ?cid={clickid})

Parameter names on the receiving side

  • clickid: RedTrack click ID returned by the network
  • sum: Payout/revenue of the conversion
  • type: Conversion event type; must match the event name as entered in RedTrack

How a RedTrack postback usually breaks

  1. Network macro names differ

    RedTrack's own examples show different tokens per network (Affise clickid={sub1}&sum={sum}, CAKE clickid=#s2#&sum=#price#). Copying one network's tokens onto another sends literal text as the click ID.

    Fix: Use the token list of the specific network, and ask the RedTrack account manager for the right macro if unsure.

  2. No dynamic payout token

    If a network does not support a dynamic payout token, the payout must instead be set as a fixed value in the offer's Default conversion revenue field.

    Fix: Set Default conversion revenue on the offer, or put the network's macro in the SUM field of Postback parameters.

  3. Event type does not match

    For ClickBank, event names added to &type= must match exactly as entered in RedTrack, otherwise the event is not matched.

    Fix: Copy the conversion type name exactly from RedTrack.

  4. Click ID missing from offer URL

    The offer URL must carry the RedTrack click ID (RedTrack's guides: '?cid={clickid}' for Digistore24, 'tid={clickid}' for ClickBank affiliates), or the network has nothing to return.

    Fix: Add the RedTrack {clickid} token to the offer URL in the network's expected sub field.

Test your RedTrack postback

Pre-filled with an example: RedTrack's postback filled in for an Affise offer, exactly as RedTrack's payout-tracking page prints it. Swap in your own network's macros. Paste your own URL over it; the check runs in this page and fires nothing.

Not RedTrack's own macros: {sub1} (Affise); {sum} (Affise).

Your network's click-ID macroThe macro the network fills with the click ID you sent it. It also tells the tester which syntax the network uses.

Want me to trace one real campaign?

This tool checks the postback URL and offer link you pasted from what you typed. It can't see your ad accounts, tracker, network or live traffic. If the result shows gaps, I'll look at one real campaign for free: I trace it from ad click to payout and back, and within 48 hours I send you a written report on where money or data leaks silently, the fix for each, and the tests that prove it's fixed.

In the review I fire a test conversion end to end on one real campaign and check it lands once, with the right payout, in your tracker and in your traffic source. You get the fix for every place it doesn't.

Shilpa Goel, [email protected]

This is an engineering checklist, not a security audit, legal, compliance or investment advice.

Not affiliated with or endorsed by Meta, Google, TikTok or any network or tracker named here.