Articles on: Tracking Setup

Token Reference

Tokens are placeholder values in URLs that get replaced with real data by the system that processes them. There are three distinct token systems you will encounter when working with FunnelFlux: FunnelFlux's own tokens, traffic source tokens, and third-party network tokens.


Each system only understands and processes its own tokens. Placing a token in the wrong system will result in the literal token text being passed instead of the resolved value.


FunnelFlux Tokens

These tokens are processed by FunnelFlux at redirect time or when building URLs. Use them within FunnelFlux's interface -- in offer data passing, lander data passing, offer source templates, and outgoing postback URLs.


Token

Description

Example Value

Where Used

{hit}

Unique hit ID for the current page view. Each node touch generates a new hit ID.

h_abc123def

Offer/lander data passing, postback URLs

{visitor}

Visitor session ID (VID). Identifies the visitor's current session.

v_8f3a2b1c

Data passing, postback URLs

{funnel-id}

ID of the current funnel being traversed.

fun_XYZ789

Offer/lander data passing, postback URLs

{trafficsource-id}

ID of the traffic source that originated the visit.

ts_ABC456

Postback URLs, data passing

{campaign}

Value captured in the reserved "campaign" tracking field.

camp_spring_sale

Data passing, postback URLs

{external}

Value captured in the reserved "external" tracking field. Typically used for the traffic source click ID.

click_789xyz

Postback URLs to traffic sources

{data-FIELDNAME}

Value captured in any named custom tracking field. Replace FIELDNAME with the name you assigned to the field.

{data-zone} resolves to zone_456

Data passing, postback URLs

{payout}

Conversion revenue amount.

29.99

Outgoing postback URLs to traffic sources

{txid}

Transaction ID associated with a conversion.

order_456

Postback URLs

{country}

Detected country of the visitor.

US

Data passing, postback URLs

{device}

Detected device type of the visitor.

mobile

Data passing, postback URLs

{browser}

Detected browser of the visitor.

chrome

Data passing, postback URLs

{os}

Detected operating system of the visitor.

android

Data passing, postback URLs

{current-node-id}

ID of the current funnel node being processed.

node_12345

Data passing


Notes on FunnelFlux Tokens

  • The {campaign} and {external} fields are reserved. Every traffic source has these two fields available automatically.
  • Custom tracking fields (up to 20 per traffic source) are accessed via {data-FIELDNAME}. For example, if you named a field "zone", you access its value with {data-zone}.
  • All URL parameters from the incoming click are temporarily stored in the visitor session, even if they are not configured as tracking fields. You can access any of them via {data-PARAMETERNAME} for data passing purposes, but only configured tracking fields appear in reporting.


Traffic Source Token Examples

Traffic source tokens are defined and processed by the advertising platform. When a user clicks an ad, the platform replaces these tokens with actual values before the browser loads the URL. FunnelFlux never sees the token syntax -- it only receives the resolved values.


Use these tokens in the tracking field placeholder values when configuring a traffic source in FunnelFlux.


Platform

Campaign Name

Campaign/Ad ID

Additional Tokens

Facebook

{{campaign.name}}

{{ad.id}}

{{adset.name}}, {{adset.id}}, {{ad.name}}, {{placement}}, {{site_source_name}}

Google Ads

{campaignid}

{creative}

{keyword}, {matchtype}, {network}, {device}, {adgroupid}, {placement}

TikTok

__CAMPAIGN_NAME__

__CID__

__AID__, __AID_NAME__, __PLACEMENT__, __CID_NAME__

Zeropark

{campaign_name}

{campaign_id}

{target}, {keyword}, {source}, {visitor_type}, {geo}

Generic push/pop

[campaign]

[campaign_id]

[clickid], [zone], [country], [device], [os]


Every advertising platform documents its own available tokens. Always refer to the platform's documentation for the full and current list.


Third-Party Network Token Examples

Third-party tokens are defined and processed by affiliate networks, CPA networks, and other external platforms. They are used when configuring a postback URL within the network's interface -- NOT within FunnelFlux.


FunnelFlux displays these tokens in the offer source configuration UI for reference convenience, so you know what format to use when setting up postbacks in the network's interface.


Network/Platform

Sub ID Tokens

Revenue Token

Transaction ID Token

Cake / HasOffers

#s1#, #s2#, #s3#, #s4#, #s5#

#price#

#tid#

Everflow

{sub1}, {sub2}, {sub3}, {sub4}, {sub5}

{payout}

{transaction_id}

Generic (varies)

{click_id}, {sub_id}, {aff_sub}

%%REVENUE%%, {payout}

{txid}, [[subid]]


How These Are Used in Practice

When you pass FunnelFlux's hit ID to a network as a sub parameter (e.g., sub1={hit}), the network stores that value. When a conversion occurs, the network fires its postback URL and replaces its own tokens with the stored values:

https://track.example.com/pb/?hit=#s1#&rev=#price#&tx=#tid#

The network replaces #s1# with the hit ID it received, #price# with the conversion amount, and #tid# with its transaction ID.


Quick Reference: Which Tokens Where

Token System

Where Configured

Who Processes

Example

Traffic source tokens

In the FunnelFlux tracking link, as tracking field placeholder values

The traffic source platform, at click time

[clickid], {{campaign.name}}, {campaignid}

FunnelFlux tokens

In FunnelFlux's interface -- offer data passing, lander data passing, postback URLs, offer source templates

FunnelFlux, at redirect time or URL build time

{hit}, {visitor}, {campaign}, {payout}

Third-party tokens

In the network's interface, when configuring the postback URL to FunnelFlux

The third-party network, when firing the postback

#s1#, {sub1}, %%REVENUE%%


Key Rule

Each system only processes its own tokens. If you place a FunnelFlux token like {hit} in a Facebook ad URL, Facebook will pass the literal text "{hit}" because it does not recognize that token. Similarly, placing a traffic source token like [clickid] in FunnelFlux's data passing configuration will result in the literal text "[clickid]" being sent to the offer page.

Updated on: 05/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!