Tracking Page Views for HTML and PDFs Explained

This article explains how page views are tracked in general and discusses how Bitly tracking ties into this ecosystem.Tracking Page Views on both HTML pages and PDF pages can enable you to see which of your assets are gaining the most interest.  These require different workflows and utilize Bitlys for this tracking. 

Page views as reported by Kapost or Google Analytics are tracked by running javascript. Javascript is executable code that gets run every time a web page is opened.  This code as it pertains to page views reports back that some page was opened and to increment the counter of page views.  Lets take the following example:

A new webpage is launched  Javascript tracking code gets added to this page from Kapost. The first time someone opens this webpage the Javascript gets executed and reports back to Kapost there was a page view and to increment the counter for page views.  The asset in Kapost will now report back that has one page view.

This system of using javascript to track page views works great when it is possible to add javascript to a webpage.  In the case of PDF's, you can not add the javascript to the webpage.  Using Bitlys is a way around this.  

When a Bitly is clicked on it drives the web traffic to a unique webpage that has javascript on it similar to the above example, and then it redirects to the PDF's asset that is to be viewed.  In this way, a count of the page views of a PDF can be obtained even though PDFs can not be tracked directly.  The above workflow happens in a way that a user will never know they were redirected on the way to viewing the PDF.  



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request