Encoding and encrypting token data
FunnelFlux lets you encode or encrypt token values before passing them to third parties. This helps you share data for optimization without revealing sensitive details like which traffic source you use.
Why encode token data?
It is common to pass data to affiliate networks -- funnel IDs, traffic source IDs, placement IDs, and more. Sometimes, though, you want to send values for optimization feedback without exposing the underlying source. Well-known traffic source IDs can reveal a lot of information to the recipient.
Token operators solve this problem. They transform token values before FunnelFlux inserts them into URLs during a redirect.
Available encoding functions
Add a function to any token by appending a : followed by the function name.
The available functions are:
-
rot13- a simple cipher that shifts number/letter values -
base64- converts the value to its Base64 representation -
bin2hex- converts a string of ASCII characters to hexadecimal values -
md5- hashes the value using the MD5 algorithm (one-way; not reversible)
All of the above are reversible if you know the method used, except for md5.
How to use token operators
Enter the modified token manually in your base page URL. You can also add it in the data passing section using the "Custom String" option.
Example tokens:
-
{funnel-id:rot13} -
{trafficsource-name:base64} -
{data-placement:bin2hex} -
{data-zone_id:md5}
Reversing encoded values
FunnelFlux applies these functions at redirect time. The encoded values do not appear in your FunnelFlux reporting data. To reverse them, you must do so yourself outside of FunnelFlux.
For rot13, base64, and bin2hex, reversing is straightforward if you know which function was used.
For md5, reversal is not possible because MD5 is a one-way hash. To map a hash back to its original value, create a lookup table (for example, an Excel sheet with original IDs alongside their MD5 outputs).
This lookup approach is tedious. Use MD5 hashing only when hiding the original value is critical.
Updated on: 05/05/2026
Thank you!
