All Collections
FunnelFlux features explained
FunnelFlux's On-page Javascript Tracking
Using the no-redirect feature to send traffic to your funnels without redirect links
Using the no-redirect feature to send traffic to your funnels without redirect links
Zeno avatar
Written by Zeno
Updated over a week ago

FunnelFlux allows you to send your traffic directly to your landing pages or own offers, without using any redirect link, while still tracking everything.

The regular flow looks like:

Your Visitors ---> Tracking Link Redirect ---> Your Lander ---> Your Offer

When using the no-redirect option, the flow looks like this:

Your Visitors ---> Your Lander ---> Your Offer

For this to work, you need to place a piece of Javascript code on your lander.

The upside to this is you skip redirects, which some traffic sources prefer, and you can host your landers directly on a CDN leading to much faster page loading for the user.

The downside is there is no tracker in the middle to make routing decisions based on user info, or split-test landers. If you wanted to, you could host these landers on a server and use PHP to rotate landers internally, but we'll leave you to decide that.

Note: we go into greater details on the Javascript code here, this article however is your best starting point.

How to use the no-redirect feature

The easiest way to use our javascript is with the "universal code" that is specific to a funnel. You can find this by going to the funnel editor > clicking Advanced Settings and then copying the code from the box:

Place this code in the <head> ection of any of the landing pages that you use in the funnel. You can place it just before the closing </head> tag.

This JS code does a number of things, and one of the most important parameters in it is flux_f  - which is the funnel ID (hence the JS tells FunnelFlux what funnel the user is in, and it figures out what node the user is on based on the URL visited).

Note that this universal JS code does not tell FunnelFlux a traffic source, the specific node it is on (explicitly at least), or any traffic source parameters.

All of these can however be passed in the URL for the JS to record, which we will cover in the next section.

How to send traffic to your lander

So, you now have a lander set up with the javascript tracking present. But how to send traffic from a campaign to it and get all the benefits of a normal tracking link?

Easy. Right click on a node in your funnel > send traffic here. Pick your traffic source and any other details and copy the link. It should look something like this:{campaign}&publisher={site}&ad={title}&creative={thumbnail}&angle={angle}

In this case it's a Taboola campaign and its passing data using Taboola's tokens.

Now, take the entire query string (everything after and including the ?) and append this to your lander URL instead:{campaign}&publisher={site}&ad={title}&creative={thumbnail}&angle={angle}

You can then use this in your traffic source/ads instead, thus direct linking to the lander and still passing the traffic source ID + other data. 

When you load this page, the FunnelFlux JS will detect global parameters like flux_fts , flux_fn  (node ID), flux_cost , as well as flux_f -- the funnel ID.

Note that if you do not pass flux_fts , the traffic will all register as *organic traffic* in reporting.

FYI the javascript will always prioritise URL params over anything written in the JS, so for those of you wondering, this is how you can use the same lander in multiple funnels without having to change the code (more on that soon).

Now, for your lander clickthrough links, just use the typical action links you can get from right clicking actions in the funnel editor > get action's URL.

How to use a lander in many funnels

Many of you will use the same lander in many funnels and you won't want to change the JS code or make duplicates of landers right?

FunnelFlux has this situation covered.

As I said earlier, the tracker will prioritise parameters present in the URL over the ones in the JS, which lets you override them.

So, if you are using some lander in a new, separate funnel, just be sure to send traffic to it using URL parameters that come from the specific funnel you want.

Right click a node in your new funnel > send traffic here > grab the generated link then pass the query string data to the lander, which should include the parameters flux_fts=something  and flux_fn=something , (the latter will be present only if you are linking to a node other than the default traffic node).

This will tell FunnelFlux the funnel/traffic source the click is coming from and it will honour this over what default is written in the JS.

What about if you used the same lander multiple times in a funnel? In this situation you shouldn't need to do anything as FunnelFlux should know what node a user is on, and thus where they should go when they click action links.

However if you deep link to a specific node in your funnel, you'll notice the flux_fn parameter being added to your link -- this is a node ID and tells FunnelFlux exactly what node your user is being sent to.

Be sure to include this parameter in your URL if you are linking from an ad to something other than the initial traffic node in a funnel.

There are both PROs and CON's to using the no-redirect option.


  • Your links look clean

  • You can hide your tracking domain (this can also be achieved when using CNAMEs with tracking links)

  • Your lander will load faster since you are not using any redirect


  • You have more control when you use a tracking link. For example, if you gave Facebook a direct link to your lander, then you wouldn't be able to change the flow of your funnel without editing the ad's URL (and wait for approval). On the contrary, if you gave a tracking link, then you would have full control and could change the flow in realtime, without having to go through another approval.

  • You cannot use rotators (no split test) or any conditional routing before your lander.

  • You cannot use the redirect type like 301, 307, Ultimate Meta Refresh (UMR) in your lander settings as there is no redirect happening.

Did this answer your question?