Articles on: FAQ

Why are URL tokens showing literally?

When you use FunnelFlux tracking links, they often contain tokens that belong to the traffic source.


For example, a Facebook, Google, TikTok, or push network link may contain tokens for campaign ID, ad ID, source ID, placement, click ID, or other values.


These tokens are not replaced by FunnelFlux. They are replaced by the traffic source when a real ad is served and clicked.


For example, if you see something like this in a URL or report:

{campaign}
{external}
{{ad.id}}

then FunnelFlux received those exact strings as the incoming values.


Why this happens


There are usually two possibilities.


The first is that the link was loaded outside of a real ad click.


This can happen if you load the tracking link yourself, if an ad reviewer opens it, if a bot checks it, or if some other automated system loads the URL. In that case, the traffic source's ad serving system never had a chance to replace the tokens with real values.


The second is that the token is wrong for that traffic source.


If the traffic source does not recognize the token, it will not replace it. It will just pass the token through as normal text, and FunnelFlux will store exactly what it received.


Common causes


  • Using a token from the wrong traffic source
  • Copying token syntax from an old guide or another tracker
  • Using the wrong brace format, such as single braces where the platform expects double braces
  • Loading the link directly instead of through a real served ad
  • Bot, crawler, reviewer, or platform check traffic


How to fix it


If you only see this on occasional clicks, it is probably bot, reviewer, or test traffic.


If you see it consistently on real traffic, check the traffic source template and confirm the token syntax matches that traffic source's current documentation.


For FunnelFlux tokens, see Available dynamic tokens.

Updated on: 20/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!