Where is the tracking code stored?

Our tracker code (the actual JavaScript) is served through the CDN so the closest location to the visitor will be used.

How does the Content Insights tracking code influence page loading time?

Content Insights tracking code is loaded asynchronously, meaning it does not affect normal page loading in any way, nor any third party scripts, asynchronous or not, that may be on the page. Our JS is outside of the normal queue of the page load (document, images, styles, your own scripts…) and outside the loading queue of any other third party scripts, it cannot block anything. The loading speed of the page and other third party scripts are not affected.

How to test the Content Insights code on your staging/test server first?

If your staging server is on the same domain as the main site you can use the same instructions. Otherwise, we need to register the domain of the staging server and assign new domain ID to it.
We recommend Chrome for testing, but you can use any browser in a similar way.

  • Load any article page on the site.
  • Open Chrome DevTools (F12).
  • Choose the Network tab.
  • Enter p? or a? in the search box to filter all requests on the page.

The tracker triggers two types of requests:

1. p request

First p request triggers a Pageview.
Second p request triggers after 10 seconds and it gives Article Read.

2. a request

One a request is triggered on every 5 seconds if there was any user activity on the article page (cursor move, click, scroll etc.) and it tracks Attention Time.
This means that if a user chooses another tab in a browser or just leaves to do something else, attention time will not be measured until they come back and perform another reading activity.

Click on any of fired requests and look for the Query String Parameters at the bottom of the Headers tab.
Another option is to just type _ain in the DevTools Console tab and hit Enter. You will see how the _ain object is filled.