Landers are pages that you control, which have one or more outgoing links.

In FunnelFlux you can have up to 64 different “action links” on a lander that can each be separately routed wherever you want.

The key difference between landers and offers are:

Here is a sample lander configuration:

This is quite similar to offer configuration but simpler.

You set a name and category and a lander URL + redirect mode.

For the lander URL, if desired you can pass in parameters from FunnelFlux -- an example scenario being that you want to use a visitor’s country on your landing page by pulling it from the URL, so you can add …&country={country}... to the URL.

Note that you can later manually pass custom parameters and all traffic source data to a lander from within a funnel’s settings, thus unless a lander needs some custom data as part of its core functionality, you can instead leave the base URL here and pass in other parameters from the funnel config instead.

Once you have configured a lander you will need to edit its page code to ensure it functions and tracks correctly.

There are two potential edits you may need to make:

Let’s go through these below.

When someone is sent to a funnel and redirected to a landing page, they are now on some external page you control. 

When they click out you need to send them back to FunnelFlux so that the system can process what to do with the visitor and where to send them. Hence, all action links will be FunnelFlux tracker links.

These action links can be one of two types:

The difference between these comes down to whether you want to track organic traffic or not, i.e. traffic that gets to your lander URL directly without going via FunnelFlux first.

If you are in doubt, it is sensible to use the ones with organic routing params included, as those extra parameters will only be used if needed.

To get your universal action link, head to Links > System Links, where you can get a link like this:

On your landers you can use this link universally with action number replaced by 1, 2, 3 etc. to correspond to the outgoing actions you have in your funnel.

By using these universal link formats, your landers can be used in multiple funnels easily -- since the links do not specify anything other than the action route for FunnelFlux to take.

You can also get this link from your funnel by right click an action route. This is where you get the specific link format for tracking organic traffic

This can only be retrieved from within a funnel by right clicking an action number coming from a lander and choosing “Get Action’s URL”

Here, if you turn on the route organic traffic option, the action link will change to include parameters about the funnel and the node ID involved, e.g.

These parameters of flux_f  and flux_ffn  declare the funnel ID and the node an action is coming from, respectively.

This allows FunnelFlux to pinpoint where in a funnel a visitor is should they turn up on the lander with no previous interaction with FunnelFlux, i.e. organic traffic.

In an organic traffic scenario where a visitor does not come via a FunnelFlux link, if they were to click a universal “action=1” link, FunnelFlux will return a 404.

Consider what FunnelFlux has to do here… it has to receive an incoming visitor and figure out what funnel they are in, what position of your funnel pathway they are in, what traffic source they came from, and where to send them.

Without even knowing what funnel they are in (remember landers can be used in many funnels and even multiple times within a funnel), there is no way for FunnelFlux to make a sensible decision on where to send them next.
​

This is what these organic action links are for.
​

Note that if you do use these, they hard code a funnel and node ID into the link. 

This means that organic traffic that has not yet been tracked will always be attributed to a specific funnel and node.

However, if people come via a FunnelFlux tracker link, or if there is JS tracking on the page that declares funnel ID, or captures it from the URL, then organic funnel/node parameters in an action URL will be disregarded, as FunnelFlux already knows where the user came from -- so you are still free to use your landers in as many funnels as you want without issue, the extra parameters just set a default for traffic of "unknown origin".

This is a common trait of FunnelFlux -- there are multiple ways you can pass data like funnel/node ID, either in redirect links, URLs, embedded in JS, etc., and there is a hierarchy to which ones get used. This allows for universal usage of pages across many funnels while having backup behaviours.

To access the configuration options here you will need to be in the funnel editor. 

If you are new to FunnelFlux, you should jump ahead to the guide on creating your first funnel then return here to study this method.

When you choose to get the URL for a lander or offer node via "send traffic here" you can toggle showing the no-redirect tracking code, which is javascript that can be placed on your landing page in lieu of using a tracking link to send users there.

However, an easier way to do this is to use the Universal JS available in your funnel editor under the advanced settings area.

This JS is simpler and you can put the same code on every page in your funnel.

If you ever want to use the landers in other funnels, or need to direct link to a specific node, you can just add flux_f  or flux_fn  to your URL to tell the JS what to use instead of the default written in its code.

Rather than explain all of this here, it's best if you head on over to our guide on the no-redirect tracking and explore.