new

Reporting

User Interface

AI Nodes now available in beta

We have been pumping out features and updates since our UI 2.0 release and the momentum continues!
See below for all the updates that have just rolled out.
AI Nodes now available in beta!
AI node feature
Our first major premium feature is now rolling out in beta.
You can create AI nodes from the funnel builder.
These offer the most advanced automatic optimisation in the industry, period. And they will only get better.
We will test these over the coming month or so before it becomes a paid premium feature, so be sure to give them a spin!
Since they are quite a complex new feature, please see our help doc here.
Some important notes:
  • If using revenue per view, it uses total revenue -- so will consider ALL event revenues
  • Right now conversion rate is just conversions. But we'll quickly add an event selector here, so you can optimise to a particular event. But we suspect most people will prefer revenue per view anyway
  • As these are in beta, their performance is not guaranteed. Please do not throw critical traffic at them.
  • Please do not programmatically create via API. They are not documented yet and have significant resource load on our system that we cannot optimise until real users test them
New dashboard available
Screenshot_7
We have updated our dashboard to make it a lot easier to view a summary of your data.
Now, you can see charges of 10 major events at once, rather than needing to switch through big clunky charts.
In the future we plan to add options to show others and pick which ones to display, as well as make the last 24 window show 15-min data points.
Additionally, quickstats are now available on the dashboard, letting you immediately drill into different funnels, traffic sources and campaigns directly from the dashboard.
PII data now available in postbacks
You can now pass phone and email data -- both raw or SHA256 hashed -- into your postbacks with the parameters pii_phone and pii_email.
If present, this data will be automatically passed on to traffic source postbacks and our custom scenario integrations (which will be the main place you use these).
No further changes are required, the data will automatically get processed and added to your event data going to Google, Facebook, TikTok etc. (have not yet implemented for Microsoft Ads).
Please note, from our investigations, it seems Google refuses PII data if click IDs are already present -- which is quite odd, but the API does what it does. We're trying to get clarification from Google on this.
Reporting improvements
Custom Events available on Raw Events page.
You can choose all 10 events alongside hits, clicks and conversions.
Conversion revenue has been added as a column in reporting, and the existing revenue column has been changed to be "total revenue" -- the sum of all event types.
P&L and ROI have also been updated to use this value.
Now your events like sales, upsells, etc. will all be present in the ROI calculations.
Funnel builder improvements
  • All funnel nodes can now be named and have the name show in the funnel builder
  • Added mobile carrier as an attribute in condition nodes
  • Conditions now select a default operator
  • Improved the operators for some conditions that were list items
  • Fixed a bug with direct link forms not resetting states properly as you clicked between nodes
  • Fixed some issues with condition nodes flagging as invalid and preventing saving
  • The node palette now shows a message when no results match your search, instead of an infinite loading animation
  • Delete page icon is now present when using "map action" mode
General UI improvements
  • Fixed URL tracking field states between tree/flat mode
  • Duplicate actions now have clearer UX, doesn't show existing asset ID when duplicating and blocks some tabs before saving
  • The default "uncategorized" options in assets is now selected properly
  • Fixed a bug with creating offer sources not closing sidebar properly
  • Fixed sidepanel animations that were a little clunky
  • Fixed some issues with URL validation in pages, allowing odd data to be saved
  • Reduced how many notifications show on screen
Upcoming changes
Postback logs in the UI are in development, and we'll add back saved views to reporting.
After that, we will need to spend some time focusing on moving to a new auth system, which we will need to better manage our upcoming premium features (like AI nodes) as well as provide the next large feature of multi-user access and management.