TUNE macros & parameters
TUNE (formerly HasOffers) uses curly bracket macros {like_this}. It's one of the oldest and most widely deployed affiliate platforms, so many networks are built on top of it. You'll see go2cloud.org domains on TUNE-powered postback URLs.
👋 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 59 of 59 entries
Attribution
{adv_sub} Advertiser sub ID 1
{adv_sub2} Advertiser sub ID 2
{adv_sub3} Advertiser sub ID 3
{adv_sub4} Advertiser sub ID 4
{adv_sub5} Advertiser sub ID 5
{advertiser_id} Advertiser ID
{advertiser_ref} Advertiser reference ID
{aff_click_id} Partner click ID
Here's what I'd do
When a partner (publisher) passes their own session ID in aff_click_id=, you can return it at conversion using {aff_click_id}. This is how TUNE integrates with external trackers like Voluum — Voluum passes its click ID in aff_click_id and gets it back in the postback.
{aff_id} Partner ID
{aff_sub} Partner sub ID 1
Here's what I'd do
When a partner passes a value in aff_sub= on the tracking link, you get it back at conversion with {aff_sub}. Use this to return their click ID or any custom value they need. Equivalent to sub1 in Everflow or s2 in CAKE.
{aff_sub2} Partner sub ID 2
{aff_sub3} Partner sub ID 3
{aff_sub4} Partner sub ID 4
{aff_sub5} Partner sub ID 5
{aff_unique1} Partner unique value 1
{aff_unique2} Partner unique value 2
{aff_unique3} Partner unique value 3
{aff_unique4} Partner unique value 4
{aff_unique5} Partner unique value 5
{affiliate_id} Partner ID
{affiliate_name} Partner name
{affiliate_ref} Partner reference ID
{city} Click city
{country_code} ISO country code
{customer_id} Customer-list customer ID
{goal_id} Goal ID
{ip} Conversion IP
{offer_id} Offer ID
{offer_ref} Offer reference ID
{offer_url_id} Offer URL ID
{ran} Random number
{referer} Conversion HTTP referrer
{session_ip} Click-session IP
{session_timestamp} Session timestamp UTC
{session_timestamp_rakuten} Rakuten-formatted session timestamp
{source} Partner traffic source
{time} Current time
{transaction_id} TUNE transaction ID
Here's what I'd do
This is the non-negotiable macro for TUNE S2S tracking. Pass it in your offer URL so the advertiser can store it, then they return it in the transaction_id= parameter of your TUNE postback URL. A standard TUNE postback looks like: https://your-network.go2cloud.org/aff_lsr?offer_id=1&transaction_id={transaction_id}
{user_agent} URL-encoded click user agent
Financial
{amount} The sale amount passed by the advertiser in the conversion pixel. Used for revenue-per-sale (RPS) offers.
{currency} Offer currency
{payout} Partner payout
Here's what I'd do
Use this to pass the conversion payout to your partner. Append it to the partner conversion URL like: &value={payout}.
{revenue} Advertiser revenue
{sale_amount} Sale amount
Mobile IDs
{device_brand} Device brand
{device_model} Device model
{device_os} Device OS
{device_os_version} Device OS version
{google_aid} Google advertising ID
{google_aid_sha1} SHA1 hash of Google advertising ID
{ios_ifa} Apple IDFA
{ios_ifa_sha1} SHA1 hash of IDFA
{ios_ifv} Apple vendor ID
{unid} Unknown/catch-all device identifier
{user_id} Application-specific user ID
{windows_aid} Windows advertising ID
{windows_aid_sha1} SHA1 hash of Windows advertising ID
Utility
{eredirect} URL-encoded offer URL.
{redirect} Offer URL for click.
Data sourced from TUNE's official documentation on 2026-09-22.