Advanced Page Group Settings

Page group nodes are the primary building blocks of funnels in FunnelFlux. Each page group acts as a single funnel step that can contain one or more pages of the same type, with built-in rotation to distribute traffic across them. This document covers the full range of page group configuration options -- rotation mechanics, local vs global scope, hit tracking behavior, multi-page setup, and when to use a page group versus multiple separate nodes.

Rotation Mechanics

When a page group contains multiple pages, FunnelFlux distributes incoming traffic across them using a weight-based rotation system.

How weights work

Each page within a group is assigned a numeric weight. Traffic is distributed proportionally based on each page's weight relative to the total weight of all active pages in the group.

Example: A page group with three pages weighted 50, 30, and 20 would distribute traffic as follows:

Equal weights produce an equal split. If all three pages had a weight of 1 (or any identical value), each would receive approximately 33% of traffic.

A/B testing with weights

Weights are the primary mechanism for split testing within a funnel step. Common patterns include:

• Equal split: Set all pages to the same weight (e.g., 1/1 or 50/50) for a clean A/B test.
• Champion/challenger: Give the proven page a high weight and the test variant a low weight (e.g., 80/20 or 90/10) to test a new page without risking most of your traffic.
• Gradual rollout: Start a new page at a low weight, then increase it over time as confidence grows.

Adjusting weights takes effect after the funnel is saved. There is no need to create new tracking links -- existing links continue to work with the updated distribution.

Local vs Global Page Groups

Page groups exist in two scopes: local and global. The scope determines where the group's configuration lives and how changes propagate.

Local page groups

A local page group is created directly within a funnel. Its configuration (which pages it contains, their weights, any other settings) exists only inside that funnel.

How to create:

• Right-click the funnel canvas and add a new lander or offer group node
• Drag and drop a "Local Lander Group" or "Local Offer Group" from the node palette
• Drag an individual lander or offer from your resource list onto the canvas (this creates a local group containing that single page)

Characteristics:

• Configuration is isolated to the funnel where the group was created
• Changes to the group do not affect any other funnel
• Best for one-off tests or funnel-specific page combinations

Global page groups

A global page group is created on the Page Groups page in the FunnelFlux UI and can be used across multiple funnels. Its configuration is shared -- any change made to the group (whether from the Page Groups page or from within any funnel's builder) propagates to every funnel that uses it.

How to create:

1. Navigate to the Page Groups section in the app
2. Create a new lander or offer group and configure its pages and weights
3. In the funnel builder, drag the global group from the node palette under "Global Lander Groups" or "Global Offer Groups"

Global groups are marked with a (G) tag on the node in the funnel builder:

Characteristics:

• Configuration is linked across all funnels that use the group
• Updating rotation weights, adding or removing pages, or pausing pages affects every funnel where the group is used
• Can be edited from the Page Groups page or from within any funnel that contains the group

When to use each

The key decision factor is reuse. If you will use the same page configuration in more than one funnel, or if you expect to update the configuration over time and want those changes applied everywhere, use a global group. For everything else, local groups are simpler and avoid unintended side effects.

Hit Tracking in Page Groups

Understanding how FunnelFlux records hits for page groups is important for interpreting reporting data correctly.

The page group does not create an independent hit

When a visitor reaches a page group node, FunnelFlux selects one of the pages inside the group (based on rotation weights) and serves it to the visitor. The hit is assigned to the individual page the visitor actually sees, not to the page group as an abstract entity.

This means:

• Reporting shows individual page performance. You will see hit counts, conversion rates, and other metrics broken down by each page within the group -- not a single aggregate "page group" metric.
• Each page touch generates one hit. If a visitor is served Page A from a group, one hit is recorded for Page A. If a different visitor is served Page B, one hit is recorded for Page B.
• The page group itself has no separate hit entry. There is no additional "group-level" hit created on top of the individual page hit. One visitor arriving at a page group node equals one hit attributed to the selected page.

This behavior means you can directly compare performance across pages in a group by looking at each page's individual metrics in reporting.

Multi-Page Node Configuration

A single page group node can contain any number of pages. This section covers the practical mechanics of configuring a multi-page node.

Adding pages to a group

Select a page group node in the funnel builder and open its settings panel. From here you can add pages to the group:

You can add pages that already exist in your account, matching the group type. Lander groups can contain landers. Offer groups can contain offers. Each page added to the group becomes part of the rotation.

Setting rotation weights per page

Each page in the group has its own weight setting. Adjust these weights to control what proportion of traffic each page receives. Weights are relative -- only the ratio between them matters, not the absolute values (weights of 1/1/1 produce the same distribution as 100/100/100).

Pausing individual pages

You can pause individual pages within a group without removing them. A paused page receives no traffic but remains in the group configuration. This is useful for:

• Temporarily stopping traffic to a page that needs updates
• Keeping a page in the group for quick reactivation later
• Running a test with a subset of pages without losing the full group configuration

When a page is paused, its weight is effectively removed from the rotation calculation. The remaining active pages continue to distribute traffic among themselves proportionally.

Lander Groups vs Offer Groups

Page groups are separated by page type. FunnelFlux has lander groups and offer groups:

• Lander groups hold landers that serve as pre-sell, bridge, or content pages
• Offer groups hold offer pages that represent offer destinations

You cannot mix landers and offers inside the same page group node. A lander group cannot contain offers, and an offer group cannot contain landers.

This matters because lander and offer nodes behave differently in funnel structure and reporting. Keep landers in lander groups and offers in offer groups, then connect the groups in the funnel flow.

Page Group vs Multiple Separate Nodes

There are two ways to present multiple pages at a given funnel step, and they produce fundamentally different funnel structures.

Multiple pages in one page group

Adding multiple pages to a single page group node means:

• All pages share the same position in the funnel
• Traffic is rotated within that single step -- one visitor sees one page
• All pages share the same outgoing connections (action 1, action 2, etc.)
• From a funnel structure perspective, this is a single step with internal variation

This is the standard approach for A/B testing within a funnel step.

Multiple separate nodes

Creating separate page group nodes (each containing one page) and connecting them independently means:

• Each node is a distinct position in the funnel
• Each node can have its own unique downstream connections
• To split traffic between them, you need an upstream rotator node or condition node to distribute visitors across the separate paths
• From a funnel structure perspective, these are separate paths through the funnel

Choosing between them

Rule of thumb: If all pages at a given step should lead to the same next step(s), use a single page group with rotation. If different pages need to lead to different destinations, use separate nodes with an upstream rotator or condition to split traffic.

Updated on: 05/05/2026