These instructions are for the Google Chrome browser, but you can use them for any other web browser as well (in a similar way).

  • Load any article page on the site.
  • Open Chrome DevTools (F12)
  • Select the Network tab

Page-view and Article Read requests

To search for page load requests, use "contentinsights.com/p" or just "p?" as a search string in the Network tab.

There should be only two p-requests for each loaded article: 

  1. t=0 indicates a page-view
  2. t=1 indicates an article read, it loads 10 seconds after the first p-request

Attention Time requests

To search for attention time requests, use "contentinsights.com/a" or "a?" as a search string. 

One attention time request for a single loaded article should be fired every 5 seconds if there's any user activity on the page: mouse-click or move, scrolling up and down, selecting the text, and so on.

Click on any of the fired requests and look for the Query String Parameters at the bottom of the Headers tab.


An alternative way is to inspect the _ain javascript object which contains all the data that will be used by the tracking code to send to our servers. To do that, just type "_ain" in the Developer Tools console and hit enter.

It's correct and expected for our ingestion server to send a "204 No Content" response for every generated request.

To learn more about different types of requests, please see How does the CI’s tracking code work?