We've just released a few UI theme-related changes and some backend improvements, details below.

We have added some new table theme options in system settings > UI settings area.

You can toggle these to change to a more compact table mode, turn on the vertical borders between cells, and make ROI highlighting affect the entire row's background colour.

We have released dozens of bug fixes and tweaks related to our new UI.

Too many changes to catalog, so this will just note the most recent updates.

Our biggest request since the new UI launch was to bring back the specific URL field selector.

Now in both tree and flat reports you can click the button below:

On click it will open a menu. Here you can select any traffic source and click which fields to add.

You will see them appear in the attribute selector.

You can click the button to go back to the menu and change fields. If you change the traffic source, it will reset and remove the existing items.

Please note since tracking fields are actually numbered (i.e. c1->c20), the aliases are shown for convenience. So you should always group by traffic source first to avoid confusing overlap of different tracking fields (e.g. ad ID from one source, site ID from another, etc.)

Now when you open quick stats for any campaign or traffic source, we show an additional row with the specific tracking fields (in addition to the URL data report that is a tree of all of them).

We're happy to announce the release of our FunnelFlux Pro 2.0 UI.

On the surface it should look and feel the same (so this isn't a disruptive change) but a lot has changed under the hood to make our future development faster.

We have rebuilt the funnel builder using a completely different rendering system.

We plan to add an "extended mode" of sorts for nodes, allowing you to show bigger nodes with more info -- e.g. a longer name, the node ID, the number of pages inside, etc.

Previously we had a "Traffic Source > Tracking Fields" complex attribute, which would group by traffic source, then list all your tracking fields that you can then expand.

However, this made it impossible to group by one tracking field and then another.

We are deprecating this in favour of two new attributes:

Now, you can chain these together, allowing you to drill down into any URL parameter, then another again in a flexible tree.

So for example, if you had traffic source fields like category, network, ad type, publisher, you could now easily drill down by category > network, then quickly switch to ad type > network, then network > publisher -- all without having to reload a new report.

If you group by traffic source first (or have a filter applied to show a single source only), it will show the field IDs and their corresponding names, like in the image above.

If you do not have the traffic source filtering in place, it will show a generic listing of c1-c20 fields.

In the report builder you can now switch between two separate tables -- Tree and Flat mode.

In flat mode every attribute will be an independent column with all data loading at once. This is very useful if you're trying to export data and/or want to use the inline filters to find specific data.

In flat mode you are limited to 10 attributes max, and Journey attributes are not available (as they are inherently tree-structured data).

As with any big refactor, there will be small bugs and issues that we haven't spotted, so we'd appreciate if you can report any issues you see.

To improve the new UI we had to change journey attributes.

We don't see any API users using these so are introducing this change without a transition period.

In the new format, a journeyData attribute with nested hierarchy is returned instead.

If you don't use the API, or do but don't use journey reports, you can safely ignore this (so pretty much all of you can ignore this).

You may also notice AI nodes in the funnel builder... they will be launched soon!

That's it for now -- enjoy the UI, sorry in advance for any bugs you may discover and thank you in advance for reporting them 😅

Wow! Has been a while since our last changelog!

We have been busy getting a refactored UI ready, developing AI nodes, and finalising a large DB migration.

We're now on track to getting most of these things released shortly and with faster development as a result.

Here's a quick summary of some recent changes we have deployed:

We have rolled out a new caching system for reporting to remedy some issues users were seeing with IDs appearing instead of names, and some large asset lists not loading.

The caching used is now a lot more performant and should have minimal issues. We still plan to move our assets DB in the future to remove the need for complex caching layers entirely.

Just now we have rolled out a new conversion deduplication process that was needed after our DB migration, as it became possible for multiple conversions to happen in rapid succession.

Our new logic has a 5 minute and 3 hour deduplication window that works like this:

We have also made optimisations to the way queries from The Optimizer work, dramatically reducing the load impact this was happening on our system.

These were becoming problematic and impacting reporting speed for all users + delaying ingest at times.

You can now pass into postbacks to force firing of events to traffic sources even if they have happened before, i.e. are updates.

This combined with our new conversion deduplication means we can soon roll out conditional postback options on the Update Conversions page, i.e. the ability to choose to:

A quick update from us — not much in the way of features to announce over the last 4 weeks as we have been working on two major tasks:

This will be our first "premium" feature (i.e. that costs extra), which will use Bayesian statistics to route traffic automatically to nodes and pages based on conversion rates and revenue per view.

We plan to release a basic version in beta first (which will be free for a while), before fully releasing the feature and some extended versions that will be suitable for higher volume customers.

We have been rebuilding our frontend app - a time-consuming process that is taking 2-3 months. The main reasons for this is to make our development faster overall, to allow vastly improving the reporting performance, and generally to allow us to roll out new features faster.

At some point after many years, things can get convoluted and in need of a refresh.

We hope to finish both of these closer to the end of September.

We have made significant updates to our knowledgebase. Frankly, I think we have the best documentation in the industry 🙂

We've released quite a lot of update so this is a long one – it took us a while to get these out due to overlapping functionalities.

We have now completed the last major step in our development of custom events.

Now, you can trigger custom events in your funnel builder directly on action connections (i.e. on clickthrough).

This makes it easy for you to fire events server side to platforms like FB/Google that would otherwise require JS on pages.

For those of you doing email submits, this will be great news as you can shift to fully server-side sending of your events to the traffic source.

Additionally, we have added new options to action connections that let you set revenue overrides for the conversion/custom event, as well as transaction ID overrides.

You can now set optional overrides for traffic sources:

The incoming cost overrides will be key for those of you running platforms with high click loss that can pass cost data (e.g. pops).

Now, if you have e.g. 10% click loss, you can enable this setting -> set a value of 110% to modify incoming costs to compensate.

Outgoing revenue overrides will allow you to modify what values get sent to traffic sources. Use this to manipulate algorithms. This will not affect your data inside FunnelFlux.

Disabling of zero revenue postbacks lastly allows you to prevent postbacks to your traffic source if the payout is zero. This can be handy if you have some initial conversions at zero revenue that are later updated to a real revenue, where you want to keep them as the same conversion event, but avoid double-posting to the source.

The raw events page has been revamped and simplified. Now, you no longer have to select funnels and traffic sources. Instead, you can optionally add filters to your data, much like on the reporting page.

There's a lot more filtering available here, as well as include/exclude options, making it easier to pull specific data reports.

We are migrating all postback handling to a new service.

This has added postback logs on our backend, which we will be able to add to the UI in due time.

I'm sure a lot of users will appreciate this for debugging traffic source conversion tracking - has been a long-time coming.

We've rolled out a few small updates over the past week.

Most of our time has been spent getting events completed, which will allow you to trigger conversion and custom events via actions in the funnel builder (including with tx/revenue overrides).

Here are our recent changes.

We've rolled out a number of general updates, and are still working on finalising our custom event features.