Advanced Lander Settings

This article covers advanced lander configuration options beyond basic setup. For an introduction to creating and using landers, see the onboarding guides on working with landing pages.

Redirect Types

When FunnelFlux routes a user to your lander via a redirect link, it uses one of several redirect modes. You can set this per lander in the lander configuration.

Note that redirect modes are irrelevant when using direct linking, since the user goes straight to your page and FunnelFlux's JavaScript handles the tracking.

301 Moved Permanently

A simple bounce redirect where the tracker responds with the destination URL and a 301 status code. This tells the browser (or bot) that the destination is the permanent location for this link.

This is the fastest redirect mode and should be your default for landers you control and host yourself.

One caveat: SEO bots interpret 301 as a permanent relationship between the source and destination URLs. If you have SEO considerations around backlinks or do-follow links, consider using 307 instead.

307 Temporary Redirect

Functionally identical to 301 in terms of performance. The only difference is the response code (307 instead of 301), which tells bots that the redirect is temporary and should not be treated as a permanent association.

Use 307 if you have SEO-related concerns about how crawlers interpret your redirect chains.

Ultimate Meta Refresh (UMR)

A custom redirect mode that routes the user through an intermediate page generated by FunnelFlux. This intermediate page attempts to blank the referrer information before redirecting onward using JavaScript.

The sole purpose of UMR is to obscure referrer data from the destination -- for example, hiding the URL of your landing pages from an affiliate network.

Downsides:

• Significantly slower than 301/307 because of the intermediate page hop
• Referrer blanking is not 100% reliable across all browsers and clients

Do not use UMR on landers you control and host yourself. You gain nothing from masking referrer on your own pages and only slow down the redirect. UMR is intended for offer pages where you want to prevent a third party from seeing your lander URLs.

Add Default Redirect Parameters

When configuring action links on your lander, you will see an "Add Default Redirect Parameters" toggle.

When enabled, FunnelFlux appends fallback tracking parameters (such as the VID, node ID, and funnel context) to the action link URL. These parameters serve as a last-resort fallback if the tracker has no existing session context for the visitor -- for example, if cookies are unavailable or the JavaScript was unable to inject data into the link.

Key points:

• These are fallback parameters, not overrides. If the tracker already has session context from cookies, referrer data, or JavaScript-injected values, it will always use those and ignore the defaults.
• Especially useful when a form submit redirects to an action link, since tracking context is more likely to get lost during form submissions.
• Not necessary in most standard redirect-based flows -- if your JavaScript is installed and working, it will inject the required data into action links automatically 99.9% of the time.

When to disable: If you are handling parameter passing entirely through JavaScript, have URL length concerns, or simply want cleaner URLs. There is no harm in having these parameters present, but they are rarely used in practice.

Custom Event Firing from Landers

Landers are not limited to clickthroughs. They can fire both conversions and custom events (numbered 1 through 10). This is useful for tracking actions like form opt-ins, button clicks, scroll depth milestones, or any other on-page interaction.

Via JavaScript

After including the universal JS snippet on your lander, you can fire events programmatically.

Fire a conversion:

flux.track("conversion", { rev: "1.23" })

Revenue and transaction ID are optional. If revenue is omitted, the default for the associated offer is used. All values should be passed as strings.

Fire a custom event:

flux.track("cevent", { "num": "1", "revenue": "1.23" })

The num value represents the custom event number (1 through 10). Revenue is optional. All data should be passed as strings.

Fire a custom event on page view:

If you want the event to trigger when the page loads, wrap it in a fluxView event listener to ensure it executes only after the universal snippet has finished tracking the view:

document.addEventListener('fluxView', function() {
  flux.track("cevent", { "num": "1", "revenue": "1.23" })
})

Via the Funnel Builder

You can also trigger custom events and conversions directly from the funnel builder without writing any JavaScript.

Right-click any action connection coming out of a lander node and select "Modify Action". From there, you can choose to trigger specific custom events or conversions when that clickthrough occurs.

You can assign a revenue value to the event and, if your traffic source settings have a trigger configured for that custom event number, it will send the event to the traffic source automatically.

This approach lets you send events fully server-side without requiring any JavaScript code on your pages.

Custom Event Aliases

You can name your custom events (e.g., "Lead", "Add to Cart") in the System Settings > Custom Event Aliases area. These aliases appear in reporting column headers and throughout the UI for convenience.

Via Postback URLs

Custom events can also be triggered via postback URLs:

https://YOUR-CUSTOM-DOMAIN/pb/cevent/?hit=HIT_ID&num=1&rev=OPTIONAL

Note that postback URLs require the event number -- aliases cannot be used in postback URLs.

Lander Data Passing

Data passing on landers lets you append query string parameters to the lander URL when FunnelFlux redirects a user to it. This is configured in the lander's "Configure Data Passing" tab.

How It Works

1. Set your Base Lander URL to the page URL without any query parameters you plan to configure through data passing
2. In the data passing section, define URL field names and select the values to send (using FunnelFlux tokens or custom strings)

This approach is more convenient than manually constructing long URLs -- you can select tokens from dropdowns and avoid mistakes with ? and & separators.

Available Token Types

• Internal data tokens -- values resolved by FunnelFlux such as country, city, browser, OS, funnel ID, hit ID, and traffic source ID
• Captured data tokens -- values from URL tracking fields using the {data-xxx} format, where xxx is the URL field name defined in your traffic source
• Custom strings -- plain text or complex token formats for specialized use cases

To pass a URL tracking field value, select "URL data" and type the field name. The {data-xxx} token will appear as you type:

Node-Level Overrides

Data passing configured at the lander level applies everywhere that lander is used. If you need different data passing for a specific funnel, you can override it at the node level.

Click any page node in the funnel builder and go to Additional Settings:

Here you have two options:

• Append Extra URL Parameters -- define a query string of additional data to append (use valid URL syntax)
• Receive Accumulated URL Parameters -- dumps all known URL parameters from the user's session into the page URL on redirect, including all traffic source tracking fields and any temporary values pushed into action links. Generally not recommended unless you have a very specific reason.

Node-level settings are the most specific and will override all other data passing configurations.

Organic Tracking on Landers

When FunnelFlux's JavaScript is installed on a lander and a visitor arrives without any FunnelFlux tracking parameters (no VID, no funnel context), the JS can create an organic entrance -- but only if you configure page defaults.

Why Defaults Are Needed

A single page can be used across unlimited funnels. Without context in the URL, the JavaScript cannot determine which funnel the visit belongs to. Page defaults tell the JS which funnel and node to use when no tracking context is present.

Setting Page Defaults

1. Open the funnel you want to be the default for this lander
2. Click the lander node and go to the JavaScript Tracking tab
3. Copy the optional defaults code block

Place this defaults code before the universal JS snippet on your page. It must appear before the universal snippet to be recognized.

Verifying Organic Tracking

To test, open your page URL directly in an incognito window with no tracking parameters. If working correctly:

• The visit appears in reporting as an organic entrance
• The browser address bar updates to include VID and node ID parameters
• Action links on the page have tracking data injected into them automatically, so clickthroughs work even without prior context

Use Cases

• Tracking SEO and direct traffic to your landing pages
• Monitoring organic visitors alongside paid campaign traffic
• Ensuring clickthroughs work for visitors who arrive without tracking parameters

Note that organic tracking through page defaults is more comprehensive than relying on default redirect parameters alone. With page defaults, you track the actual page view and all subsequent actions. With only default redirect parameters on action links, you would miss the initial page view entirely.

Updated on: 05/05/2026