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

https://demo.go2cloud.org/aff_lsr?transaction_id=#s2#   (docs example: the affiliate's postback URL with the CAKE Sub ID token in place of the click ID)

CAKE's click-ID macro: #s2#. Source: How to Use Conversion Pixel Tokens, How to Implement a TUNE (HasOffers) Postback URL (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

Parameter names on the receiving side

• transaction_id: Click ID the affiliate's tracker expects back (example target is a TUNE postback)
• s2: Sub ID slot on the CAKE tracking link carrying the click ID out
• payout: Filled from #price#
• t: Advertiser transaction ID in the conversion pixel, returned as #tid#

1. Click ID never put in s2

   #s2# only returns what the affiliate appended to s2= on the tracking link; if the tracking link lacks s2 the postback fires with an empty click ID.

   Fix: Append the tracker's click ID macro to s2 in the CAKE tracking link.

2. Long click IDs overflow into s3

   CAKE stores overflow of a long sub ID in the next slot, so #s2# alone returns a truncated click ID.

   Fix: Combine tokens as #s2##s3# when click IDs are long.

3. Hash signs lost or encoded

   CAKE tokens are wrapped in # characters; if the URL is saved in a tracker that URL-encodes # (as %23) the token is never substituted.

   Fix: Paste the postback with literal #token# and check CAKE's Pixel Log.

4. Using TUNE-style {macro} braces

   TUNE's macro is {transaction_id} but CAKE's equivalent is a hash token like #s2#; mixing the two styles leaves the literal text in the URL.

   Fix: Use #...# tokens in CAKE postback URLs.