There are two types of requests sent by our tracking code.
Article opening and metadata
To measure article reads, Content Insights waits for 10 active seconds after the page is loaded. To register an Article Read, the browser tab needs to be in focus for 10 seconds and there needs to be at least some activity on the page (e.g. mouse moves or clicks).
To count an Article Read, the tracking code sends 2 requests:
Page load request
This request is sent in the form of a GET request for the image on our servers. The address is:
and in the parameters, you can see the following metadata:
a - comma-separated list of authors b - URL of the referrer c - article title d - URL of the article e - comma-separated list of sections f - domain ID g - article’s publishing date h - comma-separated list of tags i - a number of comments as an integer j - access level k - article type pid - article ID u - session cookie identifier ul - lifetime cookie identifier t - request type identifier (0) x - request identifier
How the tracking code collects this information depends on the way the code is implemented. This can vary from case to case.
Article read request
This request is sent to the same address as Page Load request with few additional parameters:
wc - word count, number of words in the article (title included) fb_count - Facebook social actions count gp_count - GooglePlus social actions count ln_count - LinkedIn social actions count ok_count - OdnoKlassniki social actions count pn_count - Pinterest social actions count social actions count vk_count - VKontakte
Also, the "t" parameter changes its value to 1.
True attention time tracking
After the page is loaded, the code starts tracking active attention time. Active time means there is a person behind the screen whom we detect the help of tab focus and page activity (e.g. mouse movements, keyboard clicks, scrolling, etc.)
The tracking is done by sending one attention time request every 5 seconds to Content Insights’ servers via GET parameters. The address is:
The parameters that are being sent are the following:
d - URL, same as in the page load request f - domain id, same as in the page load request pid - post id, same as in the page load request b - referer u - session cookie identification, same as in the page load request ul - lifetime cookie identification, same as in the page load request at - current attention time, accumulated ar - a difference between last request and this one sp - scroll position, considering only the content ts - current timestamp seq - sequence number, the counter of requests for this page visit x - request identifier err - error number, used for internal debugging
You can easily learn more about what's being sent by following this guide.