Lander and Offer Page-Group Nodes

Page-group nodes are the main visitor-facing nodes in a FunnelFlux funnel.

They represent pages that a visitor can actually load: either landers or offers. Most other node types are routing logic that decides where the visitor should go next.

A typical funnel sends traffic to a lander group [1], and a click on the lander (Action 1) takes the visitor to an offer group [2]:

Lander groups and offer groups

There are two main page-group types:

• Lander groups contain lander pages
• Offer groups contain offer pages

You cannot mix landers and offers inside the same page group. A lander group is for landers. An offer group is for offers.

This matters because landers and offers have different roles in tracking and reporting. Landers can receive visits, clicks, conversions, and custom events, but they also show attributed downstream events from what happened after the visitor clicked through. Offers show explicit events that happen on the offer itself.

One page or many pages

A page group can contain one page or multiple pages.

If it contains one page, the node behaves like a normal single destination.

If it contains multiple pages, FunnelFlux rotates traffic between those pages using the group's rotation weights. This is the usual way to split test multiple landers at the same funnel step, or multiple offers at the same offer step.

To see the group's pages, hover over the node and click the edit button, or double-click the node. Each page has a weight, and the percentage beside it is its share of the group's traffic. Weights are relative: 100, 61 and 43 add up to 204, so the first page gets 100/204 = 49.02%.

Sorting the page list

Sort [1] changes the order of the page list:

• Manual: your own order. Drag a page by its handle on the left to move it.
• Name: alphabetical by page name.
• Category: grouped by page category.
• % weight: highest weight first.

When pages rotate by weight, the order is only there to make a long list easier to read. Changing a weight or dragging a page switches Sort back to Manual.

Map incoming action to lander number

Tick Map incoming action to lander number [2] and the group stops rotating. In an offer group, the box says "offer number". The pages become numbered 1, 2, 3 in list order, and the action the visitor clicked on the previous page decides which one they get:

• The visitor clicks action 2 on the previous page, so they go to page 2 in this group.
• A visitor who didn't arrive through an action always goes to page 1.

Weights and Sort disappear while this is ticked, because the order is now what routes traffic. Drag the pages into the order you need.

This is built for offer walls and listicles. Say a lander shows 10 products, and each product's button uses a different action number. Put the 10 offers in one offer group in the same order, tick the box, and connect the lander to that one group. Action 7 goes to offer 7, and you don't need 10 separate connections.

Local vs global page groups

Page groups can be local or global.

Local page groups exist only inside the current funnel. They are useful for one-off funnel builds where the group does not need to be reused anywhere else.

Global page groups are reusable across funnels. If you update a global page group, that update affects every funnel using it.

Use global groups when you want a shared set of pages across many funnels. Use local groups when the setup is specific to one funnel.

Page groups vs separate page nodes

Use one page group when all pages are alternative versions of the same step.

Use separate page-group nodes when those pages need different downstream paths, different funnel logic, or different reporting separation.

If you need to split traffic between separate paths, put a rotator node or condition node before those paths.

More settings

For page rotation, local/global behavior, and advanced settings, see Advanced Page Group Settings.

Updated on: 13/10/2026