Using Visitor Journey Reporting

FunnelFlux Pro has one important difference versus most conventional performance marketing trackers (like Voluum, Redtrack, Binom, etc.):

• The path the user can take has virtually no restrictions.

This has some important consequences on reporting:

• We can't show "lander + offer" as a combo grouping, because there is no requirement for users to go to a lander first, followed by one offer

In fact, there's no requirement for users to go through page types in any sequence whatsoever.

As a product owner, you might have users go to a pre-lander > a sales page lander > a checkout offer page > an upsell offer page > a thank you lander.

In this situation, you can hopefully see the "lander + offer" attribute is a bit nonsensical, hence why we don't have it.

Instead we have Journey attributes in the Report Builder, under Journey Mapping:

• Journey (full)
• Journey (pages only)
• Journey (groups and pages)
• Journey (full w/ actions)
• Journey (pages w/ actions)

These show the path a user went through as a tree. You should also notice if you try to group by a lander attribute then an offer attribute, we will automatically merge those attributes into a journey.

Here's what that might look like -- first pages only, then the full tree (rotators and groups included):

Notice the node type from the icon -- blue page icons are landers, green are offers, same as the funnel builder. Rotators use an orange split icon and show the node name (e.g. Traffic). Lander and offer groups use a page icon with a folded corner -- not a pink funnel icon.

Here I'm looking at Sample Load Test Funnel, grouped Funnel > Journey (pages only). Two starting landers -- Load Test Page 1 and Load Test Page 2 -- then the offers people reached from each.

The full journey (second image) also shows the Traffic rotator and page groups, so you can see the routing nodes, not just the pages.

We show lander and offer CTR as separate columns you can enable -- the reason for this is that if you are not grouping by lander or page type, the reporting would then show lander and offer CTR merged together, which can give odd reporting that you don't expect.

This visitor journey can go infinitely deep and lets you understand the exact sequence users go through.

Important Notes

1. If a user goes from some lander > offer, then goes back to the previous lander, we don't make another level in the tree. Instead we just make a repeat lander view on the existing level. This is to prevent infinite nesting where a user creates a tree like lander > offer > lander > offer > lander etc., which is not very helpful for analysis!
2. The tree always starts at the "entrance" a user made, which is what gives a new visit in the visit column. If you see starting points that are unexpected, its probably because some user is loading a page in your funnel where you have javascript tracking (e.g. loading a previously loaded URL, bookmark, or a tracking disconnect where they start a new journey).
3. The tree will show rotator and condition nodes, so you can understand how a user was routed. Rotators show their node names (e.g. Traffic). We will be adding them to conditions inside each route so you can even see how a user was routed (i.e. what condition route they matched).
4. Lander and offer groups are shown with a page icon (folded corner) like this:

This means that the user loaded the group's internal rotator, which then decided on which page to serve. We show this group level as it lets you understand what group node was loaded, and the overall metrics of that group rather than just individual pages (you could for example be split-testing two different groups against each other and want to see the group-level metrics).

Updated on: 15/10/2026