We were very busy in the last couple of weeks as we have renewed great parts of our reporting engine. We have now released the biggest update this year. Not all features are at the point where we want them to be, but this will follow in the next releases.
Report caching
Maybe you have noticed this already. Our reporting engine got a massive speed boost. Reports that took minutes to generate are now displayed almost instantly. The reason why some reports used to take a while to load, is that we always load raw data and we do not fill any gaps with some data. We work with every single data record we receive in our reporting engine. And that can be quite a huge amount of data.
By using the new caching mechanism, an existing report is loaded almost instantly. When you create a new report, the first report execution may still take a while. But once it is generated, it will load from the cache for future reports. Also the API profits from this update in the same way as if you would run the report from our UI.
Trigger selector
fusedeck now stores for every event, which selector triggered the event. This feature allows the set up of more general tracking events. For example: An event tracks all clicks with one event on all elements. The reports now shows which element exactly received the click. This is especially useful for the overlay report as the report shows the exact element that was clicked, independant of how the selector was defined.
Tracking URL export
Our campaign-tracking-system already allows a systematic set up based on unique identifiers. To make the set up of campaigns easier and faster, all tracking URLs can now be exported to an excel file. The excel file can be filtered to find the right tracking link for each publisher.
Report search
You can now find reports a lot faster. The search function returns only those reports matching to your search query.
CIDR flagging
This new feature allows you to flag or block complete CIDR areas. Do you want to know how many users are using the VPN function within iCloud Plus? No problem, simply set up the respective CIDR block to be flagged and you can filter that traffic via a data stream in the reports.
