CAKE macros & parameters
CAKE uses #hash# syntax for tokens — different from every other platform on this list. Tokens are written with a hash on each side, e.g. #s2# not {s2}. Pasting a CAKE URL into any other platform without converting the syntax will silently break tracking.
👋 Quick tip: Check the type badge before copying. A substitution macro inserts a value; an inbound parameter is the field name a platform expects when receiving a postback.
What are you setting up?
Choose a use case to keep only the fields that apply.
Showing 25 of 25 entries
Attribution
#eid# CAKE event ID.
#leadid# CAKE's unique conversion ID, auto-assigned to every conversion, event or lead.
Here's what I'd do
Use this for reconciliation between your system and CAKE. It's CAKE's own conversion ID — different from #tid# which is the advertiser's transaction ID. If you need to match a conversion in both systems, pass #leadid# back in your postback.
#reqid# CAKE's Request Session ID — the primary identifier for S2S postback tracking. Generated per click session.
Here's what I'd do
This is how CAKE's S2S tracking works. Pass #reqid# in your offer link so the advertiser stores it. When a conversion fires, the advertiser returns it in the r= parameter of your CAKE postback URL. Important: reqid is session-based not unique per click, so it can repeat on high-volume campaigns.
#tid# The transaction ID passed by the advertiser in the t= parameter of the conversion pixel.
Financial
#price# The payout or price value for the conversion.
Here's what I'd do
CAKE calls the payout 'price' — not 'payout' or 'amount'. Add it to your postback like: &amt=#price#. This is another naming quirk to watch for when translating from other platforms.
Sub IDs
#s1# Sub ID 1 — reserved by CAKE for the affiliate ID from your system.
Here's what I'd do
CAKE explicitly reserves s1 for your affiliate ID. Don't put your click ID here — use s2 instead. Mixing these up is a common mistake that causes attribution failures.
#s2# Sub ID 2 — the standard slot for a partner's click ID or session ID. CAKE recommends always using s2 for click IDs, not s1.
Here's what I'd do
This is the one you'll use most. When you pass your click ID into CAKE's tracking link using s2=, you get it back at conversion time with #s2#. A typical postback looks like: https://yourplatform.com/pb?click_id=#s2#. Watch out for the 100 character limit — if your click ID is longer, it overflows into s3 automatically.
#s3# Sub ID 3 — additional passthrough slot. Overflow from s2 spills here if s2 exceeds 100 chars.
#s4# Sub ID 4 — additional passthrough slot.
#s5# Sub ID 5 — additional passthrough slot.
Advertiser Data
#adv1# Advertiser Sub ID 1 — passed in adv1= of the conversion pixel. 500 character limit.
#adv2# Advertiser Sub ID 2. 500 character limit.
#adv3# Advertiser Sub ID 3. 500 character limit.
#adv4# Advertiser Sub ID 4. 500 character limit.
#adv5# Advertiser Sub ID 5. 500 character limit.
IDs
#affid# The affiliate ID on the CAKE network.
#campid# The campaign ID.
#cid# The creative ID associated with the click.
#oid# The offer ID.
Device
#ip# IP address at conversion time.
#sourceip# IP address at click time.
Mobile IDs
#udid# Unique Device ID for mobile tracking.
Timestamps
#sourcetime# Conversion timestamp in standard format (e.g. 2013-11-12T13:04:27).
#utcunixtime# Conversion timestamp in UNIX format (UTC).
User Data
#userid# Advertiser user identifier passed in the u= conversion/event parameter.
Data sourced from CAKE's official documentation on 2026-09-22.