Behavior Tracking > What Behavior is Tracked?

What Behavior is Tracked?

OneSpot’s tracking script will log multiple metrics for users’ page views as well as interactions with our content recommendation units. This behavior is used to build personalization models, to power our Insights product, and to build reports. Below is a list of behavioral information we track using our script. For details on getting the OneSpot script installed, see The OneSpot Tag.

A page-view is triggered by a visitor loading a page with our tracking script on it. Once the tracking script loads, a page-view event is fired. Data values captured and associated with the page-view include:

  • User IDs – cookie based – (domain specific and cross-domain network IDs). These user IDs contain no personally identifiable information; in addition, no personally identifiable data is enriched or joined to these IDs.
  • Session ID – cookie based – session cookie expires at 30 minutes of user inactivity. This is used for associating engagement with “sessions” or “visits” and calculating per-session metrics.
  • Page load timings (overall page load time as well as specific time intervals like download time, DNS time, DOM-ready, DOM-interactive, etc)
  • Page URL and canonical URL of the page the user is viewing
  • Browser statistics (user-agent, device type/model, OS name/version, viewport width/height)
  • Total time on page (total amount of time the page was open before the user closed the browser or navigated away)
  • Active engaged time on page (a timer pings every 5 seconds that the user has the browser tab open and has some active engagement like scrolling, clicking or mouse movement. We use these pings to measure how much time the user was actively engaged with the content.
  • Scroll depth (in pixels and as a percentage of the vertical pixel height of the page)
  • User engaged : y/n (user spent 30s+ actively engaged on the page and scrolled > 25% of the page)
  • Referrer URL (if the user arrived on the page by clicking on a link, the referer is the page they were previously on) and category (social, search referral, internal, etc)
  • IP-address and stats (ip address, ISP, owning organization)
  • Geo-location (using Geo-IP lookup) – country, region, city, zip code
  • Any marketing/tracking parameters from the URL (such as UTM parameters around campaigns, etc)
  • Clicks on hyperlinks on the page – tracked via javascript
  • Any Custom Action Tracking events that are configured for the site

More details on the mechanics of how our script performs this tracking can be found at What Does OneSpot’s Script Do?

OnSite unit engagement is tracked using the same tracking javascript that tracks page views.
  • OnSite unit viewable % (how much of the OnSite unit was in the user’s browser viewport)
  • Which content pieces were displayed in the OnSite unit, and in what order
  • System level information – such as the timing of the call, response time, whether static recommendations were used and why, etc.
  • Which content (if any) did the user click – OnSite recommendations include a click redirect for tracking purposes.
Inbox units are delivered via email. Opens are tracked via an open pixel (hidden 1×1 image in email), and clicks are tracked via our click redirect.
  • Message open
  • Which content pieces were displayed in the unit, and in what order
  • Which content (if any) did the user click