Articles on: Getting Started

Add Landing Pages


What Is a Lander?

A lander (landing page) is a page that visitors see before being sent to an offer. It is a page you control and host -- FunnelFlux does not host pages for you. Your lander might be a pre-sell article, a product review, an opt-in form, or any other page designed to warm up traffic before the final destination.


In FunnelFlux, landers are one of your core page assets. You add them to your account, then place them into funnels as nodes. The tracker handles sending visitors to the right lander and tracking everything that happens on it.


Adding a Lander

Go to Assets > Landers and click Create New. You can also use the universal create button in the top-left of the navigation.



There are a few fields to fill in:

  • Lander name -- give it a descriptive name so you can easily identify it later, especially when you have many pages.
  • Category -- use this for organization. All landers are listed within their categories on the landers tab. Note that lander categories are independent from offer or condition categories.
  • Base lander URL -- enter the full URL where your page is hosted. Do not include query string parameters here if you plan to configure data passing separately.
  • Redirect type -- this controls how FunnelFlux redirects visitors to the page. The default is 302 (temporary redirect), which works well for most cases. Do not use the meta refresh mode for your own pages, as it is designed for masking referrer and will only slow things down with no benefit when pointing to pages you control.


In most cases you simply enter the URL and leave everything else at defaults. You do not need to configure data passing for tracking to work -- you would only pass extra parameters if your page scripts need them (for example, displaying the visitor's country in the page text).


Install the JavaScript Tracking Snippet

After creating a lander, the next step is to install the FunnelFlux JavaScript snippet on your page. This is important -- it enhances tracking, enables direct linking, and ensures action links work reliably.


To get the snippet:

  1. Edit the lander and go to the Javascript Tracking tab.
  2. Copy the entire snippet shown there.
  3. Paste it into the <head> section of your landing page's HTML.



You can also find the universal JS snippet under Settings > Tracking Codes. It is the same code for all pages.


The snippet is required for direct linking (covered below), but it also provides helper functions that improve tracking reliability in all scenarios. Always add it to your landers.


Once your lander is set up and the JS snippet is installed, you need a way to send visitors to the next step in the funnel when they click a CTA button or link. This is done with action links.


Action links use a simple, universal format:

/action/1

This tells FunnelFlux "perform action 1 from this node," which sends the visitor to whatever the first connection from that node leads to in the funnel. There is no hardcoded destination in the link itself -- FunnelFlux decides where to send the visitor based on your funnel configuration.


If your lander has multiple exit paths (for example, two different CTA buttons leading to different offers), use numbered actions:

  • /action/1 -- first connection
  • /action/2 -- second connection
  • /action/3 -- third connection, and so on


These action links are relative URLs. They work because the JS snippet sets up the correct base URL context. Simply use them as the href on your buttons and links:

<a href="/action/1">Get the Offer</a>

You can also find action links in the funnel builder by right-clicking on a connection and selecting Get Action Link.


For advanced settings like the "Add Default Redirect Parameters" toggle and other action link options, see the Advanced Lander Settings reference.


Split-Testing Landers

There are two ways to split-test landing pages in FunnelFlux:


Option 1: Multiple lander nodes. Drag multiple lander pages onto the funnel canvas, each as its own node, then use a rotator node to split traffic between them.



This approach gives you more control when you want each lander to follow a different path (for example, lander A goes to offer A, lander B goes to offer B). It is also better if you use heatmap tools, since each node has its own distinct tracking.


Option 2: One node with multiple pages. Create a single lander node and add multiple pages inside it. The node acts as a page group with its own internal rotation.



Click the lander node to open it, then add pages and configure rotation weights:



Most people prefer option 2 because it is easier to add and remove pages from rotation without restructuring the funnel. Either approach works -- choose what fits your workflow.


Direct Linking

Some traffic sources do not allow redirects. Meta (Facebook) Ads users often prefer to avoid redirects, and Google Ads and Microsoft Ads require direct links. In these cases, you send visitors directly to your landing page URL rather than through the tracker.


With direct linking, the visitor lands on your page first, and the JavaScript snippet fires to register the visit with FunnelFlux. The snippet captures all URL parameters and starts the tracking session.


To get a direct link:

  1. In the funnel builder, click the lander node.
  2. Go to the Direct Links tab.



The direct link consists of your page URL plus a URL suffix containing tracking parameters (funnel ID, traffic source, node, and any data-passing tokens). The UI splits this into sections because many ad platforms expect them separately -- for example, Google Ads has a "Final URL" field and a "Final URL Suffix" field. You can copy each part directly from the FunnelFlux interface.


For testing, copy the full direct URL which combines everything into one link.


A few things to keep in mind:

  • WordPress users -- enable the WordPress toggle in the direct links section. This removes the p parameter from the link, which otherwise conflicts with WordPress's internal post ID parameter and causes 404 errors.
  • No split-testing -- when using direct links, the tracker is not in the middle of the request, so it cannot rotate between different pages. The visitor goes directly to whatever URL is in the ad.


Conversions and Custom Events on Landers

While landers are most commonly used for clickthroughs, they are not limited to that. Landers can also fire conversions and custom events.


A common example is an opt-in lander where you want to track form submissions as a "lead" event. You can configure funnel actions to trigger custom events when a visitor clicks through from a lander, and even assign revenue values or send events to your traffic source server-side.


For details on configuring custom events on actions, see the Advanced Lander Settings reference.


Next Steps

Once you have your landers added and the JS snippet installed, you are ready to build funnels that connect traffic sources, landers, and offers together. The next articles in this series will cover adding offer sources and offers.

Updated on: 05/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!