About Web Analytics (3.5)

Jenny Jarrard — Tue, 31 Jan 2012 15:59:10 GMT

Current Revision posted to Telligent Analytics Product Documentation by Jenny Jarrard on 1/31/2012 9:59:10 AM

In Release 3.6 and 3.7, new Web Analytics were shipped.

In Release 3.5: Telligent Analytics makes use of page views to more accurately reflect true page views for actual user visits, filtering out requests from page view totals including response codes other than 200; robot/crawler visits, and requests from within Telligent Evolution itself.

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

Web Analytics is the collection, analysis, and reporting of information about Internet traffic on your Web site. Telligent Analytics 3.0 introduces all three stages of this process for use with your Telligent Evolution site.

How is data collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the End Request event of every page request, then records detailed information about each request made to the community site.

This module uses an additional user cookie for tracking unique users and returning visitors. If a user logs in, the cookie is tied directly to his/her site membership account - adding the ability to report on views by specific community members.

The Analytics module requires additional tables and stored procedures to be added to your community site. The script for adding these elements, as well as the assembly file and other configuration files, is found in the ExtendedAnaltyics folder of your Telligent Analytics 3.0 installation package. Follow the Analytics 3.0 installation instructions for more information on adding the module to your community site.

The module includes a configurable queue which collects requests. These requests are then written to the database in bulk. The ExtendedAnalytics.config file allows you to specify how often these items are written to the database. If necessary, the files can be written to a separate database. For larger communities, it is recommended the requests be frequently written out and that they be stored in a separate database.

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

These approaches are typical because a tool built on one or both of these technologies can be applied to a large customer base regardless of the server type or Web application type being run (e.g., HTML, PHP, ASP.NET, etc.).

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Because Telligent Analytics targets a specific technology and specific application, we are able to leverage technologies specific to ASP.NET and information specific to Telligent platforms that allow access to more precise information about each request. For example, because we integrate the ExtendedAnalytics module directly with the Telligent platform application, we are able to record additional information about each request by:

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

The statistics gathered by each different method of collecting Web Analytics statistics can vary greatly. We selected an HttpModule approach because the limited scope of this solution allows us greater control over each request - and ultimately results in greater accuracy.

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although, note, it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the cleanup job (see CleanupJob.sql) be installed to delete old records and free storage space.

How is the data analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on user and session information. Information about individual views, statistics on page requests, and browser and referrer information are also processed as part of this task.

The WebAnalyticsTask differentiates between browser views, RSS views, and robot or crawler views; it then stores each of these types separately in the Analytics database for reporting. The primary means of differentiating between these types is through intelligent parsing of the Http User Agent string passed with the request.

In the directory where you install the Telligent Analytics 3.0 tasks, there is a configuration file named WebAnalytics.config. This holds the current list of regular expressions used to identify common user agent strings, broken out by category. It may be necessary to update this file periodically as new user agents are introduced. Check the Telligent Web site periodically for published updates to this file.

The Web Analytics task is intended to be run frequently. Out of the box, this task is configured to run once every hour. The resulting reports in Telligent Analytics will be close to real-time (only off by at most one hour). The interval between executions is also configurable.

What reports are included?

Telligent Analytics 3.0 includes a comprehensive set of reports built around views, visitors, pages, and referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.0:

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics 3.5

Jenny Jarrard — Tue, 04 Oct 2011 20:27:42 GMT

Revision 16 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 10/4/2011 3:27:42 PM

NEW in Release 3.5: Telligent Analytics makes use of page views to more accurately reflect true page views for actual user visits, filtering out requests from page view totals including response codes other than 200; robot/crawler visits, and requests from within Telligent Evolution itself.

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Alex Crome — Sun, 28 Aug 2011 19:39:59 GMT

Revision 15 posted to Telligent Analytics Product Documentation by Alex Crome on 8/28/2011 2:39:59 PM

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Fri, 19 Mar 2010 20:01:58 GMT

Revision 14 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 3/19/2010 3:01:58 PM

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Fri, 19 Mar 2010 19:57:34 GMT

Revision 13 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 3/19/2010 2:57:34 PM

Pre-calculated roll-up data is used for page views as well as topics and sentiment.

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Mon, 14 Dec 2009 15:25:31 GMT

Revision 12 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 12/14/2009 9:25:31 AM

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this approach differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: dynamicstyle.aspx)
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this approach differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some drawbacks of these technologies:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers.
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community/context-specific information about the page requested (i.e., Which community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Fri, 11 Dec 2009 21:21:15 GMT

Revision 11 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 12/11/2009 3:21:15 PM

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

The module includes a configurable queue in which requests are collected, then written to the database in bulk. The ExtendedAnalytics.config file allows you to specify how often these items are written to the database. If necessary, the files can be written to a separate database. For larger communities, it is recommended the requests are written out frequently and stored in a separate database.

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

These approaches are typical because a tool built on one or both of these technologies can be applied to a large customer base regardless of the type of server or Web application being run (HTML, PHP, ASP.NET, etc.).

Some of the drawbacks of these technologies include:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Because Telligent Analytics is targeting a specific technology and a specific application, we are able to leverage technologies specific to ASP.NET and information specific to Telligent platforms that allow access to more precise information about each request. For example, because we integrate the ExtendedAnalytics module directly with the Telligent platform application, we are able to record additional information about each request such as:

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community-context-specific information about the page requested (i.e., What community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the cleanup job (see CleanupJob.sql) be installed to delete old records and free storage space.

How is the data analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on user and session information. Information on individual views, statistics on page requests, and browser and referrer information are also processed as part of this task.

What reports are included?

Telligent Analytics 3.0 includes a comprehensive set of reports around views, visitors, pages, and referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.0:

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Fri, 11 Dec 2009 19:27:11 GMT

Revision 10 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 12/11/2009 1:27:11 PM

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record postbacks as unique requests
Install a SQL job to clear old requests from the database (presumably after the requests have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript who are disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single page view is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community-context-specific information about the page requested (i.e., What community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

How is the data analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on user and session information. Information on individual views, statistics on page requests, and browser and referrer information are also processed as part of this task.

What reports are included?

Views
- Page views
- RSS page views
- Most-viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Wed, 02 Dec 2009 22:03:35 GMT

Revision 9 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 12/2/2009 4:03:35 PM

This article contains the following information:

What is Web Analytics?
How is data collected?
How does this differ from other Web Analytics solutions?
How is the data stored?
How is the data analyzed?
What reports are included?

What is Web Analytics?

How is data collected?

The Analytics module requires additional tables and stored procedures to be added to your community site. The script for adding these elements, as well as the assembly file and other configuration files, are found in the ExtendedAnaltyics folder of your Telligent Analytics 3.0 installation package. Follow the Analytics 3.0 installation instructions for more information on adding the module to your community site.

Configuration options include the ability to:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Telligent Analytics data
Specify additional file extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record post-backs as unique requests
Install a SQL job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This module is unique to the Telligent Evolution/ Enterprise brand and is not compatible with other Web sites.

How does this differ from other Web Analytics solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS log parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled are not recorded via client-side JavaScript. Aside from missing Web views when a user has JavaScript disabled, this method also misses requests from RSS readers and search engine crawlers
IIS log parsing is difficult to do successfully and is often imprecise. In IIS logs, a single pageview is typically represented as several requests because the log file includes requests for every component of a page (i.e., images, style sheets, page controls, etc.).

Tying visits directly to a logged-in user
Recording real page titles along with URLs
Gathering community-context-specific information about the page requested (i.e., What community group, section, and post(s) are associated with the page?)

How is the data stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the data analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on user and session information. Information on individual views, statistics on page requests, and browser and referrer information are also processed as part of this task.

What reports are included?

Views
- Page views
- RSS page views
- Most viewed pages

Visitors
- Total visitors
- Time on site
- Depth of visit

Loyalty
- Visitor frequency
- Visitor recency
- Exit ratio

Usage
- Browser usage
- Search keywords
- Traffic sources
- Exceptions

About Web Analytics

Jenny Jarrard — Wed, 02 Dec 2009 17:03:57 GMT

Revision 8 posted to Telligent Analytics Product Documentation by Jenny Jarrard on 12/2/2009 11:03:57 AM

What is "Web Analytics"?

Web Analytics is the collection, analysis, and reporting of information about internet traffic on your website. Telligent Analytics 3.0 introduces all three stages of this process for use with your Telligent Community / Enterprise site.

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the "End Request" event of every page request, and records detailed information about each request made to the community site.

This module uses an additional user cookie for tracking unique users and returning visitors. If a user logs in, the cookie is tied directly to their site membership account, adding the ability to report on views by specific community members.

The Analytics Module requires additional tables and stored procedures to be added to your community site. The script for adding these elements, as well as the assembly file and other configuration files, are found in the ExtendedAnaltyics folder of your Telligent Analytics 3.0 install package. Follow the Analytics 3.0 installation instructions for more information on adding the module to your community site.

The Module includes a configurable Queue in which requests are collected, then written to the database in bulk. The ExtendedAnalytics.config file allows you to specify how often these items are written to the database, and if necessary the files can be written to a separate database. For larger communities, it is recommended the requests are written out frequently and stored in a separate database.

Configuration options are as follows:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Analytics data
Specify additional File extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record Postbacks as unique requests
Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS Log Parsing

These approaches are typical because a tool built on one or both of these technologies can be applied to a large customer base regardless of the type of server or web application they are running (html, php, asp.net, etc).

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers
IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

Tie visits directly to a Logged-in User
Record real Page Titles along with Urls
Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

The statistics gathered by each different method of collecting Web Analytics statistics can vary greatly. An HttpModule solution was selected for our approach because the limited scope of this solution allows us greater control over each request, and ultimately greater accuracy.

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

Requests are imported into the Analytics database through the WebAnalyticsTask. This unique task processes requests and organizes requests based on User and Session information. Information on Individual Views, statistics on Page requests, and Browser and Referrer information are also processed as part of this task.

The WebAnalyticsTask differentiates between Browser, RSS, and Robot/Crawler views, and stores each of these separately in the Analytics database for reporting. The primary means of differentiating between these types is through intelligent parsing of the Http User Agent string passed with the request.

In the directory you install the Telligent Analytics 3.0 Tasks to, there is a configuration file named "WebAnalytics.config". This holds the current list of regular expressions used to identify common user agent strings, broken out by category. It may be necessary to update this file periodically as new user agents are introduced. Check the Telligent Community site periodically for published updates to this file.

The Web Analytics Task is intended to be run frequently. Out of the box, this task is configured to run once every hour. The resulting reports in Telligent Analytics will be close to real-time (only off by at most one hour). The interval between executions is also configurable.

What Reports are Included?

Telligent Analytics 3.0 includes a comprehensive set of reports around Views, Visitors, Pages, and Referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.0:

Views
- Page Views
- RSS Page Views
- Most Viewed Pages

Visitors
- Total Visitors
- Time On Site
- Depth Of Visit

Loyalty
- Visitor Frequency
- Visitor Recency
- Exit Ratio

Usage
- Browser Usage
- Search Keywords
- Traffic Sources
- Exceptions

Glossary of Terms

HttpModule

An HttpModule is an ASP.NET feature that allows you to wire events into specific parts of the server request. The ExtendedAnalytics HttpModule subscribes to the Application_EndRequest event so that we can gather information after the page has been requested and the user authenticated.

Microsoft's Definition: An HttpModule is an assembly that implements the IHttpModule interface and handles events. ASP.NET includes a set of HttpModules that can be used by your application. For example, the SessionStateModule is provided by ASP.NET to supply session state services to an application. Custom HttpModules can be created to respond to either ASP.NET events or user events.

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

An Http Cookie is a piece of text stored on a user's computer by a web browser. Cookies are used in Telligent Analytics to record a unique user identifier and recognize returning visitors, as well as to store an identifier for the current session in order to group and connect page requests.

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

A Session is one or more page requests made by a single Visitor in succession. Telligent Analytics uses a browser cookie to track page requests that are part of the same session. An individual session lasts until a user's connection to a web page times out due to inactivity, that user leaves the web page to visit an external site, or that user closes their web browser.

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web Analytics

JanaCarter [Telligent] — Wed, 07 Oct 2009 23:29:17 GMT

Revision 7 posted to Telligent Analytics Product Documentation by JanaCarter [Telligent] on 10/7/2009 6:29:17 PM

What is "Web Analytics"?

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the "End Request" event of every page request, and records detailed information about each request made to the community site.

Configuration options are as follows:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Analytics data
Specify additional File extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record Postbacks as unique requests
Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS Log Parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers
IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

Tie visits directly to a Logged-in User
Record real Page Titles along with Urls
Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

What Reports are Included?

Views
- Page Views
- RSS Page Views
- Most Viewed Pages

Visitors
- Total Visitors
- Time On Site
- Depth Of Visit

Loyalty
- Visitor Frequency
- Visitor Recency
- Exit Ratio

Usage
- Browser Usage
- Search Keywords
- Traffic Sources
- Exceptions

Glossary of Terms

HttpModule

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web Analytics

JanaCarter [Telligent] — Wed, 07 Oct 2009 23:28:40 GMT

Revision 6 posted to Telligent Analytics Product Documentation by JanaCarter [Telligent] on 10/7/2009 6:28:40 PM

What is "Web Analytics"?

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the "End Request" event of every page request, and records detailed information about each request made to the community site.

Configuration options are as follows:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Analytics data
Specify additional File extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record Postbacks as unique requests
Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS Log Parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers
IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

Tie visits directly to a Logged-in User
Record real Page Titles along with Urls
Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

What Reports are Included?

Views
- Page Views
- RSS Page Views
- Most Viewed Pages

Visitors
- Total Visitors
- Time On Site
- Depth Of Visit

Loyalty
- Visitor Frequency
- Visitor Recency
- Exit Ratio

Usage
- Browser Usage
- Search Keywords
- Traffic Sources
- Exceptions

Glossary of Terms

HttpModule

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web analytics

JanaCarter [Telligent] — Wed, 07 Oct 2009 23:28:19 GMT

Revision 5 posted to Telligent Analytics Product Documentation by JanaCarter [Telligent] on 10/7/2009 6:28:19 PM

What is "Web Analytics"?

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the "End Request" event of every page request, and records detailed information about each request made to the community site.

Configuration options are as follows:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Analytics data
Specify additional File extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record Postbacks as unique requests
Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS Log Parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers
IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

Tie visits directly to a Logged-in User
Record real Page Titles along with Urls
Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

What Reports are Included?

Views
- Page Views
- RSS Page Views
- Most Viewed Pages

Visitors
- Total Visitors
- Time On Site
- Depth Of Visit

Loyalty
- Visitor Frequency
- Visitor Recency
- Exit Ratio

Usage
- Browser Usage
- Search Keywords
- Traffic Sources
- Exceptions

Glossary of Terms

HttpModule

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web analytics

JanaCarter [Telligent] — Wed, 07 Oct 2009 23:27:25 GMT

Revision 4 posted to Telligent Analytics Product Documentation by JanaCarter [Telligent] on 10/7/2009 6:27:25 PM

What is "Web Analytics"?

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the "End Request" event of every page request, and records detailed information about each request made to the community site.

Configuration options are as follows:

Specify how frequently requests are written to the database
Specify a separate database connection string for storage of Analytics data
Specify additional File extensions to record other than .asp, .aspx, .htm, .html
Specify specific files to ignore (example: "dynamicstyle.aspx")
Specify whether or not to record Postbacks as unique requests
Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

Client-side JavaScript
IIS Log Parsing

Some of the drawbacks of these technologies include:

Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers
IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

Tie visits directly to a Logged-in User
Record real Page Titles along with Urls
Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

What Reports are Included?

Views
- Page Views
- RSS Page Views
- Most Viewed Pages

Visitors
- Total Visitors
- Time On Site
- Depth Of Visit

Loyalty
- Visitor Frequency
- Visitor Recency
- Exit Ratio

Usage
- Browser Usage
- Search Keywords
- Traffic Sources
- Exceptions

Glossary of Terms

HttpModule

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web analytics

JanaCarter [Telligent] — Wed, 07 Oct 2009 23:15:49 GMT

Revision 3 posted to Telligent Analytics Product Documentation by JanaCarter [Telligent] on 10/7/2009 6:15:49 PM

What is “Web Analytics”?

Web Analytics is the collection, analysis, and reporting of information about internet traffic on your website. Telligent Analytics 3.0 introduces all three stages of this process for use with your Telligent Community / Enterprise site.

How is Data Collected?

Telligent Analytics 3.0 includes an additional assembly (ExtendedAnalytics.dll) that runs on your community site to collect traffic information. This assembly includes an HttpModule that subscribes to the “End Request” event of every page request, and records detailed information about each request made to the community site.

Configuration options are as follows:

· Specify how frequently requests are written to the database

· Specify a separate database connection string for storage of Analytics data

· Specify additional File extensions to record other than .asp, .aspx, .htm, .html

· Specify specific files to ignore (example: “dynamicstyle.aspx”)

· Specify whether or not to record Postbacks as unique requests

· Install a SQL Job to clear old requests from the database (presumably after they have been imported into Telligent Analytics)

This Module is unique to the Telligent Community / Enterprise brand and is not compatible with other websites.

How Does This Differ From Other Web Analytics Solutions?

The most common approaches to recording Web Analytics statistics include:

· Client-side JavaScript

· IIS Log Parsing

Some of the drawbacks of these technologies include:

· Visitors with JavaScript disabled will not be recorded via client-side JavaScript. Aside from missing web views when a user has JavaScript disabled, this method also misses requests from RSS Readers and Search Engine Crawlers

· IIS Log Parsing is difficult to do successfully and is often imprecise. In IIS Logs, a single Page View is typically represented as several requests because the log file includes requests for every component of a page (images, style sheets, page controls, etc)

· Tie visits directly to a Logged-in User

· Record real Page Titles along with Urls

· Gather community-context-specific information about the Page requested (what Community Group, Section, and Post(s) are associated with the Page?)

How is the Data Stored?

The ExtendedAnalytics module stores data in raw request format in the specified database. This is to ensure that the processing time and storage space consumed are both minimized.

Even though a minimal amount of data for each request is stored, the amount of space needed to house all page requests for an extended amount of time can be quite large (although it is unique to the amount of traffic your community receives). Allocate additional space for storing your Web Analytics data. It is also recommended that the Cleanup Job (see CleanupJob.sql) is installed to delete old records and free up space.

How is the Data Analyzed?

In the directory you install the Telligent Analytics 3.0 Tasks to, there is a configuration file named “WebAnalytics.config”. This holds the current list of regular expressions used to identify common user agent strings, broken out by category. It may be necessary to update this file periodically as new user agents are introduced. Check the Telligent Community site periodically for published updates to this file.

What Reports are Included?

Telligent Analytics 3.0 includes a comprehensive set of reports around Views, Visitors, Pages, and Referrers. Here is a list of the different sections of reports included with Telligent Analytics 3.0:

· Views

o Page Views

o RSS Page Views

o Most Viewed Pages

· Visitors

o Total Visitors

o Time On Site

o Depth Of Visit

· Loyalty

o Visitor Frequency

o Visitor Recency

o Exit Ratio

· Usage

o Browser Usage

o Search Keywords

o Traffic Sources

o Exceptions

Glossary of Terms

HttpModule

Microsoft’s Definition: An HttpModule is an assembly that implements the IHttpModule interface and handles events. ASP.NET includes a set of HttpModules that can be used by your application. For example, the SessionStateModule is provided by ASP.NET to supply session state services to an application. Custom HttpModules can be created to respond to either ASP.NET events or user events.

Http User Agent

A User Agent is the client application used to make a request to the web site. Typically this is a type of web browser, RSS reader, or search engine crawler.

Http Cookie

An Http Cookie is a piece of text stored on a user’s computer by a web browser. Cookies are used in Telligent Analytics to record a unique user identifier and recognize returning visitors, as well as to store an identifier for the current session in order to group and connect page requests.

Page View

A Page View is a request for a page file (*.aspx, *.html, etc.) not including requests for additional page components like images, style sheets, script files, and so on.

Web View

A Web View is a request for a page file coming from a Web Browser.

RSS View

An RSS View is a request for Page content coming from an RSS reader or other syndication tool.

Robot/Crawler View

A Robot/Crawler view is a Page View coming from a search engine crawler or other automated program that download web pages for indexing or otherwise gathering information about a web page.

Visitor

A Visitor is a unique user who visits the web site. Returning visitors are tracked in Telligent Analytics through a browser cookie.

Session

A Session is one or more page requests made by a single Visitor in succession. Telligent Analytics uses a browser cookie to track page requests that are part of the same session. An individual session lasts until a user’s connection to a web page times out due to inactivity, that user leaves the web page to visit an external site, or that user closes their web browser.

Referrer

A Referrer is an external web site a visitor was viewing before coming to your web site. Referrers are typically search engines or other external sites that hyperlink to pages within your web site.

Web analytics

Tim Yates — Mon, 13 Jul 2009 18:00:58 GMT

Revision 2 posted to Telligent Analytics Product Documentation by Tim Yates on 7/13/2009 1:00:58 PM

The web analytics reports in Telligent Analytics include a module that tracks all HTTP requests that come into your community and divides these requests into three types:

Web page views (which we term Page Views)
RSS page views
Robots, spiders, and other automatic traffic

These web views include any page views, include profile views, home page visits, and all application visits (forum posts, blog post reads, etc.). We measure differently than Omniture and Google Analytics, just as they measure differently from each other.

Web analytics

Anna Van Sligtenhorst — Tue, 07 Jul 2009 14:01:23 GMT

Revision 1 posted to Telligent Analytics Product Documentation by Anna Van Sligtenhorst on 7/7/2009 9:01:23 AM

The web analytics reports in Telligent Analytics include a module that tracks all HTTP requests that come into your community and divides these requests into three types:

Web page views (which we term Page Views)
RSS page views
Robots, spiders, and other automatic traffic