Action Proxy Nodes

Action proxy nodes are passthrough nodes for action links. Here three lander sets each have 7 actions. All of them connect to one proxy [1], and the proxy sends each action to its offer [2]:

They do not contain pages, run conditions, or split traffic. Their job is to receive an action number and pass the visitor through to the matching outgoing action connection.

Why action proxy nodes exist

Action proxy nodes are mainly for keeping complex funnels readable.

Imagine a listicle page with 10 buttons, where each button sends visitors to a different offer. If you have several listicle pages that all use the same button layout, drawing every action connection from every page can get messy quickly. This is the same funnel without a proxy:

An action proxy lets each page connect to one proxy node. The proxy then fans out to the shared destinations.

The visitor experience does not change. The proxy is just a routing structure inside the funnel.

How action numbers pass through

If the visitor clicks action 3 on the page, the action proxy receives action 3.

It then follows the outgoing connection for action 3 from the proxy node. In the first screenshot, a click on action 1 on any lander set goes to Offer 1, action 2 to Offer 2, and so on.

This means your page can keep using normal action links, while the proxy centralizes where those actions go.

When to use action proxies

Use action proxy nodes when:

• many pages share the same action destinations
• a page has many buttons or links
• your funnel canvas is becoming difficult to read
• you want one place to manage repeated downstream action routing

Do not use an action proxy for normal one-step funnels. If a page has one or two simple clickthrough paths, direct connections are usually clearer.

Action proxy vs rotator

An action proxy does not choose between paths. It follows the action number that the visitor clicked.

A rotator node chooses a path based on weights.

Use a rotator when the system should choose the path. Use an action proxy when the visitor's clicked action should choose the path.

Updated on: 13/10/2026