Configuration Tips for SharePoint Profiles

If you use Angelfish Software v2.4+, please use the new Help Center:


This article contains a few configuration tips for tracking SharePoint sites with Angelfish. Here's a quick list, with details below:

  • Use the USR tracking method if possible
  • Add documents to the Pageview File Types field
  • Include Pageview Query Parameters
  • Uncheck "Ignore Inflated Visits"
  • Use the SharePoint Filters
  • Use a Raw filter with Subsites


1) Use the USR tracking method if possible

The USR tracking method grabs the username from the log file and uses it to identify unique visitors. Most SharePoint Intranet sites require authentication, which means the username is available in the log file - you can verify the username is in the log by opening the file and having a look.

Public-facing SharePoint sites sometimes don't have the username in the log file, which means the USR tracking method isn't possible for these sites. The IPUA tracking method will work, but we recommend "upgrading" to one of the JavaScript-based tracking methods (AGF or UGA) as soon as possible.

Page Titles are only available in the JavaScript-based tracking methods (AGF and UGA), so you'll need to add tracking code to your master page if you want to see page titles.


2) Add documents to the Pageview File Types field

If you use one of the log-based tracking methods (USR, SID, IPUA, or IP) you must specify the file types for Angelfish to count as pageviews. We recommend adding the following file types - just add the following line into the Pageview File Types field:  (you can copy & paste)

doc docx dotx xls xlsx xltm ppt pptx pdf


As long as the username is available, this addition will show you the usernames that access a document. Try it - process data and open the reports, then find any document in the Top Pages report and segment by username (via the segment icon: Traffic - Visit Details - Username).


3) Include Pageview Query Parameters

More often than not, query parameters are meaningless from an analytics perspective and clutter the reports. Angelfish's default setting is to ignore all query parameters, but it makes sense to enable some parameters in reports for SharePoint websites.

Query parameters are configured via the "Pageview Query Parameters" field in each Profile's Settings tab. With SharePoint, we recommend using the Include option with the following parameter settings:

id mode k

You can add parameters to this list as you see fit.


4) Uncheck Ignore Inflated Visits

The Settings tab of the profile config contais a checkbox called "Ignore Inflated Visits" - this feature is intended to automatically exclude robots & crawlers that exceed a certain pageview count, which alleviates the need for you to manually add (and maintain) filters to exclude them.

Robots & crawlers aren't usually a problem for Intranet sites, with some exceptions (e.g. the Google Search Appliance). We recommend unchecking this option so you don't mistakenly exclude visits from employees with lots of pageviews.


5) Use the SharePoint Filters

Angelfish includes two predefined filters: "SharePoint: exclude websvc files" and "SharePoint: trim "0#.w|" from username". We recommend adding the "exclude websvc files" filter to all SharePoint profiles, and the "trim "0#.w|" from username" if your reports show encoded claims usernames.

The Admin Notes field in each filter contains an explanation of what each filter does.


6) Use a Raw (Include) Filter with Subsites

Raw filters are applied to both visit-level and hit-level data. The Include and Exclude filters are only applied to visit-level data.

If you use an Include filter instead of a Raw (Include) filter, your IT Reports section will show hit data for the entire site instead of just for the Subsite.  This will significantly increase processing time and the storage requirement for the profile's agfs-it.db file.

Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.