Unique Users by Events (Unique Users by URL)

This report lets you see the distinct visitors to your website, ranked by number of events.

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 pageviews events, wildcards can help filter specific document extensions or URL query string parameters.

    For example, if you would like to display unique users who viewed 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


Table Widget

The Unique Users by Events table widget contains the following columns:

User: The user name, cookie identifier, or IP address.

Views: The number of events

Visits: The number of visits.Visits are a series of SharePoint page requests from the same uniquely identified client with a time of no more than 30 minutes between each page request.

Searches: The number of SharePoint search action.

Visit Duration:  The average duration of visits.

Custom columns: This widget provides the ability to add additional user fields.


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