We've rolled out some improvements to our AI nodes, reporting UI, and a number of small fixes.
AI Node Updates
We now support
next best page
as the default in AI nodes. This mode will route to the next best pages within all destination nodes. This is much more powerful and easy to use, as you no longer need to make multiple nodes.
Additionally, we have removed a number of settings that overcomplicated things a bit in favour of having more intelligent handling on our side.
We have made extensive changes to the AI node logic to make them much more reliable in low data situations (i.e. you're just starting out and don't have many visits/conversions).
Being an experienced affiliate myself, I have also written many tests for how it should handle routing in the unique scenarios that come up, e.g.
- When you have very few conversions and don't want to make premature decisions, even if Bayesian/stats results suggest it
- When you have different offer payouts and need to consider how much a single conversion would impact the decision
- When you have similar RPVs but one has a lot more absolute conversion counts (i.e. confidence in your data)
Now, our AI nodes are quite conservative when there is not much data, but will flip to a much more aggressive approach when the data confidence is high enough.
We have also implemented a new API that will allow us in the future to show you the current routing percentages in the funnel builder, so you have transparency on what it's doing.
Table Performance Improvements
Some of our users have thousands of assets and this can lead to part of the UI being slow.
We have made a number of changes to greatly improve this:
- All our reporting tables have had their rendering slightly changed to make them far more performant with large lists. You may notice more "render as you go" behaviour in tables because of this, but will experience much more responsive tables. This for example is helpful on the raw events page as well when loading thousands of rows.
- We have removed pagination from all tables because of this, as it's now easier to render everything and not cut it into pages.
- We have created new UI components that are much more performant at rendering huge lists. Now all lists for assets like funnels, traffic sources, pages, are using these. In the node palette as well of the funnel builder, the lists should be more performant.
- When opening the filter menu in reporting and similar, we now lazy-load assets as needed to prevent slowdown.
Reporting Improvements
We patched issues with our "Journey" attributes that were giving weird results in some situations, which can also affect lander/offer reporting.
The data should be more reliable now in general.
We also fixed the issue with the postback logs table with the timestamps not showing in the correct format, or using the datetime range correctly.
Additionally, we made some improvements to our reporting API to make it more performant and reduce the payload size being returned (generally improving performance a little bit for all, including API users).
Other notable changes:
Added a Quora Ads tracking template and new integration for using API-based tracking for it.