Using our reporting to understand your data
updated 20 days ago
Reporting is likely where most users spend the majority of their time -- trying to understand their data and figure out how to optimise.
You can also check the reporting help section for a number of other articles.
How reporting works
FunnelFlux Pro reporting is highly flexible and lets you group into a tree with very few limitations.
On the reporting page, you can choose your date/time range then add attributes in order that you'd like to group by:
You can also load one of our "quick reports" for a specific preset:
Then, click apply to load the report.
You can expand the tree as needed to drill down into the data.
After the first two levels, data will lazy-load. This is done so that data is loaded quickly in small parts, rather than trying to generate a huge single report.
The downside is that you can't export the full report to Excel/CSV directly, but we will provide a dedicated export function for this later.
Setting columns and displayed metrics
To set columns to display, click the settings icon in the footer or tap the hotkey "S":
You can browse through the different tabs to find columns you would like to display.
You can drag the table's column headers to move them into a different order.
Note that the abbreviation for each metric is displayed beside it, e.g. Cost per Visitor | CPV -- in the table, we will display "CPV" as the column name, not "Cost per Visitor". This is done to keep the columns narrow, otherwise the table can become unnecessarily wide.
Also note that in FunnelFlux, landers and offers are two separate types of pages, each having their own view and click metrics.
As such, a lander row will always show zeroes in the offer view/clicks columns and vice versa. If you have a funnel with your own offer pages in it (as opposed to a typical affiliate funnel where the end page is an offer you don't control), then you may need to look at offer view, click and CTR columns.
You can filter in two ways -- using inline filters or the restrict data option.
Inline filters can be turned on in the footer, or with the "F" hotkey:
Inline filtering works as-you-type and you can enter data in multiple columns.
The inline filtering always acts on the deepest child, so in the above example if I write "dire.." it will be filtering on the "Direct traffic (no referrer)" row, not on the parent rows. Sometimes you'd want to filter on a different row, but we have to pick one default option here for now -- and we have chosen the "deepest row" option.
For number columns, you can use operators e.g. >1000, <1000, 1000-25000.
On the other hand, the Restrict Data option allows you to filter the entire report query to include or exclude certain attribute values:
It currently only lists the options you are grouping by, but we plan to expand this later to include many global attributes -- so that, for example, you can group by funnel > traffic source, but then filter to only show data from the US.
For now, you can specifically include or exclude items from the report as above.
How journey attributes work
The "Journey" reports are unique to FunnelFlux and are necessary to display complex funnel data in a table format.
Firstly, for basic reporting, you might find the visual heatmaps in funnels either -- so be sure to check there.
Now, in FunnelFlux, unlike most trackers, there is no prescribed sequence of pages.
In many trackers there are a few specific sequences only:
- Traffic > offer
- Traffic > lander > offer
- Traffic > prelander > lander > offer
There is no such requirement in FunnelFlux. Your funnel can do any sequence, users can start anywhere. There is no requirement for a lander or offer to exist before or after anything in particular.
For example, your user might go Traffic > offer > lander > offer > lander > lander.
Because of this, we cannot provide a "Lander + offer" attribute. It is simply non-sensical. It would be like asking people on the street what their "single lunch food item + single drink item is", requiring them to have eaten the food first, then a drink, only one of each, and in that exact sequence.
Instead, we offer the Journey attributes, with a few variations that remove certain node types to make the tree simpler. Note: if you try to group lander and offer attributes together, we will automatically collapse these into Journey.
Use this journey reporting to understand the sequence users go through and the visits, revenue per view, etc. at each level.
In Journey reports, RPV (revenue per view) is probably your most valuable metric for understanding the money per visit to that node/level.
In the future, we will add some other columns like flow % (how many people got to this level versus parent) and RPV relative to parents as well, for even deeper analysis.
Breaking down by URL data (e.g. keywords)
A common question is, "how do I see keyword data".
All data like this that comes from traffic sources is passed via URL parameters, as defined in your traffic source config in FunnelFlux.
To group by these there are two methods. Firstly, you can add a specific URL field from a specific source here:
Note when you do this it will limit all further choices to that source only in the dropdown. This is because its non-sensical to group by URL parameter 1 of traffic source A, then URL parameter 2 of traffic source B. Users cannot be from two traffic sources simultaneously, so such a grouping would never work.
Alternatively, and this is usually much easier, user the Traffic Source > Tracking Fields attribute:
This groups by all sources and all their respective fields. This makes it much easier to break down multiple traffic sources and their fields together.
Lastly, you may also want to consider using quick stats to drill into the specific traffic source on its own, or the campaign analysis page.
On the campaign analysis page you can open a reporting overlay for a specific traffic source campaign and click buttons to switch between tracking field breakdowns.
This will often be much faster than manually building reports every time. Learn to leverage quickstats, they are usually... quick!