We have rolled out a number of important improvements to reporting, particularly around drilling down into lander/offers, as well as a new UI for analysing specific hits and visitor sessions.
New UI - Hit Explorer
This new UI is primarily to help with critical debugging of hits and session flows.
For visitor IDs, you can see a timeline of hit events. You can click these blocks to jump between inspecting a specific hit, and can click visitor ID again to go back to the visitor ID analysis.
Additionally, we have added an "inspect" button to the raw event and postback pages, allowing you to jump to this inspector.
Improvements to Raw Events
On the raw events page, we have made the following quality of life improvements:
- Now limited to 20 columns max (up from 15)
- Timestamp, event type, hit ID are all pinned columns on the left now and are removed from column selection
- Asset names and ID are extended -- you can now get page ID, page name, offer source ID, name etc.
- You can now click an inline inspect icon to jump to the hit inspector
Improvements to Posback Logs
We have added page name, page category and offer source as columns
Have also updated to make timestamp, event, hit ID permanent pinned columns
Also added an inspector button to jump to see full details of a specific hit
Filtering Updates
We discovered a new user-agent that was responsible for a lot of bot traffic -- 'hertz', specifically associated with a TikTok ISP and Singapore-based.
We now filter it and will be removing it from historic data to clean up reporting.
Reporting Improvements
We have rolled out changes to improve the cost and conversion attribution data, especially when drilling down into lander/offer type attributes.
This will mainly affect the data you see when opening quickstats for an offer or lander, or doing drilldowns in the report builder that group by a page attribute, followed by others.
For example: Funnel > Offer > Traffic Source > Country
These are inherently complex, because it groups by viewing a specific page that is deep inside a funnel somewhere, then expands further.
In general you can't simply filter to that page, because you lose context of the overall funnel visits, the cost it truly took to get people to that page, and in the case of landers you need to consider the downstream offer conversions that attribute back up the journey.
This is one of the most complex parts of our system because of how FunnelFlux lets you make any sort of funnel, with steps in any order.
I am somewhat jealous of most other trackers that have really simple traffic > lander > offer flows only (often with the offer destinations pre-ordained in advance)... must be much easier to deal with the query logic!
Otherwise, we've also tweaked caching, so swapping between pages and quickstat reports is smoother and faster than ever before.