Angelfish v2.20 Highlights
Angelfish v2.20 contains a number of improvements and fixes, many of which are minor. This article highlights the more important changes in the release.
Delete Specific Visits
This feature was prompted by the EU’s GDPR laws: each Profile lets you delete visits that match a specific IP address / username / source / browser (or other visit-level dimensions). However, it can also be used to delete traffic that you didn’t exclude with a Filter before processing, like pageviews from SharePoint service accounts, monitoring agents, or referral spam.
We really like this feature – instead of having to delete everything and reprocess, you just delete the visits you don’t want.
Avg Time on Page
The Page and Page Title reports and the Visitor ID modal (available in AGF / UGA / USR Profiles) have a new metric column: Time on Page. This column shows the average time spent on the page in MM:SS format for all pageviews.
Reports Load ~33% Faster
Thanks to some improvements, reports now load significantly more quickly than the previous version.
DB Maintenance Pre-Check
The DB Maintenance utility can require free space as much as 150% of the db file being optimized. If this space isn’t available, the DB Maintenance task will be skipped and the related processing job will have a status of “Notice.”
HTTP Security Headers
Angelfish now contains a header file where you can list of HTTP response headers to add to all Angelfish HTTP & HTTPS responses. This feature is intended to be used in high security environments.
Add Hardware Info to Support Tickets
All too frequently, one of the first questions our support team asks when troubleshooting is something like “what are the hardware specs of the Angelfish server?” When you open a support ticket from the Support tab of the About page in v2.20, the Server Status tab are appended to the ticket, which will alleviate some of the back and forth Q&A with new support tickets.
Updated Browser & Platform Detection
Angelfish now recognizes some smaller (yet growing) browsers: Vivaldi, UC Browser, Samsung Internet. Plus, detection for more popular browsers has been improved.
Use Local Time for Date Substitution
Previous versions used GMT for determining date substitution. v2.20 uses the local server time. This change primarily affects customers in Asia & Oceania who use date substitution statements in Datasources (e.g. u_exYYMM.*).
IP and Org DB Updates
Updated GeoLocation and Organization info.
The full list of improvements and fixes is available in our Help Center: