Available dynamic tokens
Dynamic tokens are placeholder variables (written as {token-name}) that FunnelFlux replaces with real values at runtime. Use them to pass tracking data, user details, and device information to your pages and conversion postbacks.
You can get dynamic data from FunnelFlux to your pages in two ways:
- Through a redirect link
- Using our JavaScript
Redirect links are the simplest approach. Add {token} directly to the URL, or use the data passing section in the UI. This section provides searchable lists and filters out tokens that do not apply to the selected resource.
JavaScript can also retrieve token data. See the articles on overriding default JavaScript behaviour and other JavaScript methods and functions.
Table of Available Tokens
Below is a list of all available tokens, organized by category. Each table shows whether the token works on pages, conversions, or both.
User Identifiers
These tokens identify the individual user and their tracking session.
Name | Token | Pages | Conversions |
|---|---|---|---|
Hit ID | {hit} | ✅ | ✅ |
Visitor ID | {visitor} | ✅ | ✅ |
External ID | {external} | ✅ | ✅ |
User IP | {ip} | ✅ | ✅ |
User-Agent | {user-agent} | ✅ | ✅ |
General Tokens
These tokens expose internal FunnelFlux data such as funnel IDs, traffic source details, and referrer information.
Name | Token | Pages | Conversions |
|---|---|---|---|
Current Unix Time | {timestamp} | ✅ | ✅ |
Funnel + Traffic Source Hash | {tracking-fts} | ✅ | ⛔ |
Funnel Group ID | {group-id} | ✅ | ⛔ |
Funnel Group Name | {group-name} | ✅ | ⛔ |
Funnel ID | {funnel-id} | ✅ | ✅ |
Funnel Name | {funnel-name} | ✅ | ⛔ |
Referrer Domain | {referrer-domain} | ✅ | ✅ |
Referrer URL | {referrer} | ✅ | ✅ |
Tracking Domain | {tracking-domain} | ✅ | ⛔ |
Traffic Source ID | {trafficsource-id} | ✅ | ⛔ |
Traffic Source Name | {trafficsource-name} | ✅ | ⛔ |
Traffic Source Campaign | {campaign} | ✅ | ✅ |
Custom and URL Data
Custom strings and data passed through the URL buffer -- that is, via entrance or action links.
Name | Token | Pages | Conversions |
|---|---|---|---|
Custom String | N/A | ✅ | ⛔ |
URL Data Field | {data-name} | ✅ | ✅ |
Location and Connection (resolved from user IP)
FunnelFlux derives these values from an IP-geolocation lookup. Using them in redirect links or JavaScript may slightly increase response times because of the extra lookup step.
Name | Token | Pages | Conversions |
|---|---|---|---|
ISP Name | {isp} | ✅ | ✅ |
Connection Type | {connection-type} | ✅ | ✅ |
Continent | {continent} | ✅ | ✅ |
Country Code | {country-code} | ✅ | ✅ |
Country Name | {country-name} | ✅ | ✅ |
Region | {region} | ✅ | ✅ |
City | {city} | ✅ | ✅ |
User Latitude | {latitude} | ✅ | ✅ |
User Longitude | {longitude} | ✅ | ✅ |
User Timezone | {timezone} | ✅ | ✅ |
Browser and Device (resolved from user-agent)
FunnelFlux derives these values from device detection based on the user-agent string. As with geolocation tokens, using them may slightly increase response times.
Name | Token | Pages | Conversions |
|---|---|---|---|
Browser Name | {browser} | ✅ | ✅ |
Browser Language | {browser-language} | ✅ | ✅ |
Browser Version | {browser-version} | ✅ | ✅ |
Device Brand | {brand} | ✅ | ✅ |
Device Type | {device-type} | ✅ | ✅ |
Device Model Code | {model} | ✅ | ✅ |
Device Model Name | {model-name} | ✅ | ✅ |
Operating System | {os} | ✅ | ✅ |
Operating System Version | {os-version} | ✅ | ✅ |
Node-related Data
These tokens relate to funnel nodes -- the individual pages or steps a visitor passes through.
Name | Token | Pages | Conversions |
|---|---|---|---|
Click Action Number | {action-number} | ✅ | ⛔ |
Current Node ID | {current-node-id} | ✅ | ⛔ |
Current Node Name | {current-node-name} | ✅ | ⛔ |
Page ID | {page-id} | ✅ | ✅ |
Page Name | {page-name} | ✅ | ✅ |
Page URL | {page-url} | ⛔ | ✅ |
Referring Node ID | {referring-node-id} | ✅ | ⛔ |
Referring Node Name | {referring-node-name} | ✅ | ⛔ |
Offer Source ID | {offer-source-id} | ✅Offers Only | ⛔ |
Conversion Data
These tokens apply only to conversion events.
The {external} token (External ID) comes from the "external" tracking field. FunnelFlux captures it when a user enters from a traffic source. It appears in this table again because it plays a key role in conversion tracking.
Name | Token | Pages | Conversions |
|---|---|---|---|
Conversion Timestamp | {conversion-time} | ⛔ | ✅ |
Conversion Revenue | {payout} | ⛔ | ✅ |
Conversion Transaction ID | {txid} | ⛔ | ✅ |
External ID | {external} | ✅ | ✅ |
Entrance Timestamp | {entrance-timestamp} | ⛔ | ✅ |
Encrypting Token Data
FunnelFlux supports token modifiers that let you encrypt or hash token values before passing them. See the full guide on encoding and encrypting token data.
Updated on: 05/05/2026
Thank you!
