Events (Pageviews by URL)

This report shows the number of events, filtered by event name or URL address.

This report is designed for tracking custom events such as mouse clicks on specific UI elements. It is primarily used for campaign tracking, however it can also be used to filter reports by a specific URL address or all page URLs beginning with a specific URL address.



  • By default, each SharePoint page view is automatically logged and reported by CardioLog Analytics as a view event, having the URL as the event title.
  • Event filtering supports the use of wildcards. For page views events, wildcards can help filter specific document extensions or URL query string parameters.

    For example, if you would like to display page views for PDF documents only, enter %.pdf in the Website Item URL filter. The percent sign (%) wildcard character is a substitute of all possible characters.

  • Learn how to fire custom events with the CardioLog Analytics client API
  • Learn how to use goal funnels to report on campaign events.


Available Report Widgets

Meter, Chart, Table, Map


Table Widget

The Events table widget contains the following columns:

Title: The event name. URL is used for pageviews events.

Views: The number of times the event was fired.

Unique Users: The number of single visitors who fired the event, as identified by login information, or an anonymous cookie, or IP address.

Duration: In cases where the event represents a page view, duration is the average time spent by visitors on the page

Exit Rate:  In cases where the event represents a page view, exit rate is the percentage of times a specific page was the last page in a visit to the web site.


Map Widget

This report provides a world-map representation of events by country. Countries are color coded, with darker colors representing higher values. Mouse over a country to display the number of events. CardioLog Analytics uses internal and third-party data to derive visitors' geographic locations from their IP addresses.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk