Articles on: Funnel Building

Using the funnel builder

Prefer a visual guide? Watch the video below. Please note elements of our UI may have changed since the video's creation.



The funnel builder is the core visual editor in FunnelFlux.


Here, you can build and design all your funnels, controlling the logic that our servers use to process visitors.


Its best to think of a funnel as a decision-making flow chart -- because that's exactly what it is!


Funnel builder menu

You'll notice a menu on the left. Here you can:

  1. Add Nodes -- open the node palette to browse your account resources and drag & drop nodes
  2. Links -- generate redirect links (Funnel Settings > Redirect Links). You can also hover a node and use Get Link
  3. Settings -- funnel name and advanced overrides
  4. Stats -- quick stats for the current funnel. Same as the stats icon on the funnels page
  5. Heatmap -- colour-coded overlays on your nodes, showing data like visits, ROI, etc.
  6. Help


Below that are layout controls, an edge-style dropdown (Bezier by default), and Path Trace / Big Nodes toggles.



Adding nodes to a funnel

To add nodes, click Add Nodes and use the node palette:



The palette has node-type tiles at the top, then an Existing Resources section. Click between Landers, Offers, Cond., and Tags, toggle Pages vs Groups, and type to search. Click and drag > drop items onto the canvas.


There is no canvas right-click menu -- nodes are added from this palette only.


Node types

The palette has more than five node types. The core ones you'll use constantly:

  • Rotator (FYI the traffic node is a rotator)
  • External URL
  • Condition
  • Offer Group
  • Lander Group


You'll also see Tag, Act. Proxy, Webhook, Logic, AI Node, and Middleware -- those have their own articles.


Rotators

These can be used as many times as you want in a funnel to split traffic in multiple directions. You define the connections and the % weighting each connection has.


External URL

These are a simple node that send a user to a URL. These cannot have outgoing connections from them and should only be used if you want to bounce a user to some external URL where you have no control, e.g. redirecting blocked users to a special page, outgoing links to third-party sites that are not offers, etc.


Condition

These can be used to create rules for how you want to route users.


Every "route" you create is an outgoing connection that must exist from the condition.


So if you create two "routes" in the condition node, where they have certain rules in them, users would match those rules and eventually get sent down a specific route.


In the funnel builder, you need to click and drag from a condition node to connect these routes to destination nodes. Every one must have a destination, as the tracker must always be able to decide where to send someone.


Lander and Offer Groups

These are essentially the same -- they are a page group node that can have one or more pages inside of them.


If you want to split-test between multiple offers, you could add multiple offer nodes, each with one offer in them, or you could add a single offer group node and inside of its settings, you can add the many pages. It's up to you!


Inside these nodes you can set the rotation % between pages as well as various other options.


Building a funnel

After creating nodes, you need to connect them together.


Remember, this is a flow chart -- and a flow chart needs to have lines drawn between things to make sense.


With broken connections, the funnel may refuse to save, or if saved and used, it could result in errors with your links going nowhere.


To make connections, hover over the node. You will see multiple small handles appear:



Click and hold on one of the handles then drag to another node and release. This will create a connection from node A > B.


Note that connections are uni-directional -- one-way. When you drag from A to B, the connection goes from A to B but not from B to A!


That connection will have a label in it, like Action 1 above. You can click and drag to move that label around, and you should be able to see the arrow for the direction of that connection.


Once you have wired things up, you can save your funnel at any time by clicking the save button:



Note that changes to the funnel are ONLY saved when you click this button.


When you click a page node for example > and it opens the settings panel, and you save this, you are NOT committing those changes just yet.


This is important, because if the funnel was saving with each action, it would often be broken as you are mid-changes and while doing that, tracking links might break. So it only commits changes to our backend when you save the complete funnel above.


Save and Discard stay disabled until you make a real change -- editing settings, adding a connection, dropping a node, and so on. Just dragging a node around may not light them up.


When you want to send traffic to your funnel, you do so by generating links.


You can generate a link to send a user to any point of the funnel, though you'd usually use the traffic node.


Click Links in the builder menu > Redirect Links, pick a node in Select a node, choose a source, then copy the link. You can also hover a node and use Get Link:



This is a Redirect Link - a link that goes to our servers, the tracker then decides where to send the user.


Note you do not need to save these links. This is just a link generator. When you close this panel and open it again, it will have reset.


Links in FunnelFlux are dynamic and can be generated at any time -- they depend on the funnel and traffic source and do not have some unique hash or ID in them per link that needs to be saved.


In some traffic sources you will not be able to use redirect links, or it may be best to avoid them (e.g. Google Ads, Microsoft Ads, Facebook).


In that case, you can generate a Direct Link that goes straight to a page but appends URL data for our Javascript to receive.


These are on a page group's Direct Links section -- Base page URL, URL suffix, and Full Direct URL:



For a traffic source like Google Ads, you would use the "Base Page URL" as your ad URL, then put the "URL suffix" we give you in the optional suffix settings. This is a common ad configuration pattern that exists in multiple traffic sources.


On loading the ad, the result is a user would load the full direct URL, go to your page, and our Javascript would log their visit + their URL data.


Incidentally, you can get our Javascript on the corresponding tab, and should put this on all pages you control, whether you are using redirect or direct links. It has important functions that improve tracking in all cases:



Action links - for page clickthroughs

If you have any page where a clickthrough will happen, this will be what we call an "action".


You may notice in the funnel builder that the outgoing connections from page nodes have labels saying Action 1, Action 2, etc.


When users get to one of these nodes, the next step is to tell the tracker "execute action 1" or similar. A very generic instruction!


This is so the tracker, knowing the user and where they are, can decide where the user should go next.


To do this you need an action link. Get one from the Action Links section in the page settings, or hover the connection > Get Action Link:



This will bring up an action link modal:



You can see this link is very generic, i.e. it is track.mydomain.com/action/1


Here you can also toggle on default redirect parameters, but this is not needed in most cases, so you can ignore it for now.


Take these links and use them for your call to action buttons on pages, or any other links where you want FunnelFlux to track the click and control where the user will be sent.


Local vs Global Nodes

The palette no longer labels things "local" and "global", but the distinction is still there:



Dropping a node-type tile (Lander, Offer, Condition, etc.) creates a node that exists only in this funnel.


The same is true when you drag a page from Existing Resources > Pages.


Switch to Groups and you get reusable lander groups, offer groups, and conditions -- items that live outside the funnel (there is a Page Groups page and a Conditions page in the app).


When you drag and drop these, you create a node as usual, but its settings are linked to that shared item.


In this way, you can reuse these groups/conditions in multiple funnels and their configuration is shared. Change the item in one funnel (or on their respective page) and it will impact all funnels that use them.


These global resources are useful for things you want to use repeatedly -- like a condition for routing desktop and mobile, or bouncing a list of flagged ISPs, or a global list of "top X offers" that you want to adjust over time and have that change propagate to all funnels.


Imagine if you had 20 funnels all using the same list of current top-performing X offers, and if you needed to remove an offer, you had to edit each node manually in every funnel!


Deleting nodes

Hover a node and click the trash icon in its toolbar:



Note when nodes are deleted they are not actually removed from the funnel, but hidden. This is so that existing links to the nodes don't break, to prevent accidental catastrophes (e.g. you delete a node then realise a live campaign is linking to it).


Later we will add a cleanup option, which lets you clean out these old nodes.

Updated on: 15/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!