Advanced Info & Tips

This article contains an array of best practices, advanced admin info, and tips that we've learned over the years.  We'll add more tips to this article as we learn them!

This article is intended for current Angelfish Admins who are already familiar with admin tasks and terms.

  • You can make a copy of each Object (Profile, Datasource, etc.) via the Copy button
  • Investigate issues in the copy, then apply changes to the original
  • Use a Tag or add a string to the Object name so they can be deleted later
  • e.g. add a Tag of "copy" or prepend "TMP-" to the name

  • This is the best way to identify and eliminate bad data from the reports in a new Profile
  • The first time you process data, only process a few small logs or one large log.
  • Open the reports and look for unwanted or missing data.
  • Reports to use: Browsers, Platforms, Usernames, Organizations, IP Addresses, any of the Content reports, Top Files in IT Reports
  • When you identify something to exclude, update the relevant config settings | Filters
  • Delete all data in the Profile and process the same logs again
  • Once the reports look right, process a larger group of logs
  • Go through as many iterations of Update & Reprocess as you need to clean up your reports
  • If you notice undesirable data in the future, make a copy of the Profile - use the copy to test changes before applying them to the active Profile
  • Use the Delete Data: Specific Visits utility to remove undesirable data from an active Profile (see Deleting Data, below)

  • The Delete Data section in the Run / Data Management tab in each Profile provides three ways to remove data:
    • All Data: removes all report data AND all log tracking info from the Profile
    • Custom Range: removes report data between a specified start and end date
    • Specific Visits: removes report data that matches a Dimension pattern between a specified start and end date 
  • Use the Specific Visits option to satisfy data deletion requests

  • If you need to reprocess data after deleting a custom range, Log Tracking can be an impediment
  • The best workaround is to make a copy of the existing Datasources
  • Log Tracking info doesn't get copied when a Datasource is copied!
  • Use the copy button and edit the Location field in the copy to match the desired date range
  • Once the copies are created, process the Profile: the copied Datasources will be read
  • Once processing is complete, delete the copied Datasources.

  • Each Tracking Method provides a unique perspective in the reports
  • Create the second Profile by making a copy of the original and updating the Tracking Method
  • If the original Profile uses a JS-based Tracking Method, use a log-based method in the copy
  • The Log-based Profile will contain traffic from Visits that block JavaScript

  • Each Profile uses one Tracking Method, and you can update the Tracking Method at any time
  • You can process historical logs using one Tracking Method, then switch to another for future logs
  • Some fields only exist in JS-based Tracking Methods, like Page Title

  • Report data files are stored in a folder for each Profile: ../data/<profile-id>/
  • These files are not linked to the Profile ID, meaning you can move them around

  • It's a good idea to save your web logs: you can always reprocess data if you have the logs
  • Logs compress very well (90% or more), and Angelfish reads compressed logs. 
  • Supported formats: zip, gzip, bzip2
Creation date: 4/20/2022 6:51 PM (Angelfish Support)      Updated: 6/5/2022 9:13 AM (Angelfish Support)