improved

Reporting

Tracking

September updates

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:
AI nodes
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.
Frontend app rebuilding
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.
Aside from that, there are a few small things we have done:
  • Added a toggle to reporting to allow attribution by entrance time, rather than event time. For those of you with quite delayed conversions or revshare, this will allow you to see revenue and conversions aligned with the day the visitor entered the funnel. This makes conversions, revenue, ROI, etc. by date and time more accurate in these situations.
  • We updated our default logic for processing repeat conversions (those where a conversion with the same hit/tx has already happened). Now they will overwrite as usual but will NOT send a repeat postback to the traffic source.
  • Added a handful of templates
  • Fixed some issues with the FB UI
  • Fixed an issue with tracking fields in conditions